.png%3Falt%3Dmedia%26token%3D8174d25a-bbf3-43b6-9e21-3b022d5cd5ec)
.png%3Falt%3Dmedia%26token%3D8174d25a-bbf3-43b6-9e21-3b022d5cd5ec)
5. Create a Process
So far we have created ontologies, roles, information, documents and rules. Now we need to bring it all together. This bundling is what is called a process. It defines which elements are allowed to interact with each other.
To create a process we need to give it a key as usual.
Furthermore, we have to select whether the process is a Creation process, which leads to the creation of a new instance of an outcome ontology, or a Lifecycle process, which modifies already existing instances. With our process, we want to create new account opening contracts, so we select 'Creation'.
The outcome ontology of the process defines what kind of instance will be created at the end of the process. As mentioned before, we want to have a contract in the end. Therefore, we select 'Contract' as the outcome ontology.
The workflow defines the states of the process and how one moves through them. Every workflow usually starts with a draft state and ends with either an approved or declined state. Let's select the 'simple_workflow' which is the most basic workflow with exactly these three states.
Let's also make sure that our process can be started from the Dashboard and give the process a name. We want our process to be called 'Account Opening'.
The process we have just created is still an empty shell. Adding the documents (or more importantly the information on them) which are essential will form the process. The essential document in our scenario is the individual account opening form we have created in an earlier step. Let's go ahead and add it to the process.
The same goes for rules. We define how a process should be steered by choosing the rules that should be part of it. Therefore, we should add our rule that ensures one person with role account holder to the process. Without doing so, the rule would not do anything and just sit idle.
Last modified 1yr ago