When configuring Atfinity, rules, documents, proofs, etc. are created. A process is the place where all these elements can be combined in order for them to interact with each other. It is a roadmap which defines the elements that play a role during the creation or modification of an instance.
Also connected to that roadmap is a workflow which defines the directions the road can take.
This combination of documents, rules and proofs together with a workflow is what we call the process. It makes Atfinity ask the relevant questions in the right order and finally leads, as mentioned above, to the creation or modification of an instance of an outcome ontology.
Here are two examples of processes (and their types):
Client Onboarding (creation) – The point of this process is the creation of a new contract. This contract might include a person the bank already knows, however the contract itself is new and has not existed like this before. That's why it is a creation process.
KYC (lifecycle) – Here, more information of an existing client should be collected or existing information updated. So in the end of the process, there won't be a new instance of the outcome ontology but instead the same instance will be updated. It is therefore called a lifecycle process.