How to create a Process
alt: split things up even more, Process Header with short chapters; Object Model Header; Workflow Header.
Here you will learn how to create a Process in Atfinity.

The Basics

In the Configuration menu, choose 'Processes'. Then click 'Create Process' to start.
In the screen that pops up, enter the basic characteristics of the new process.
The name of the process in English, as it will appear in the list of cases. If needed, provide the name in other supported languages through Translations.
Example: 'Onboarding'.
Creation: the process results in the creation of an instance of an outcome ontology.
Lifecycle: the process modifies an existing instance of an outcome ontology.
Outcome ontology
Choose the ontology this process applies to.
Each case created with this process will follow the steps defined in the workflow you select here.
Click 'Confirm'. The process is now listed in the Processes overview screen.

Set Parameters

The next step is setting the parameters that determine how, if at all, the process shows up in the Case Manager.
To begin, in the Processes overview screen, click on the process you just created.
In the screen that follows, under the tab ‘General’ you are able to set the parameters:
The options that haven't been set in the previous step are:
Created automatically from the process name you provided. In Atfinity, the process will be identified with the key.
If you disable a process, no new cases can be created for it. Existing cases can still be completed.
Allow instance creation
Yes: this is the default setting, which enables a user to add or remove other instances, besides the primary outcome instance which is always part of the case. E.g. the user could add additional persons to a contract.
Button Text
The name on the button that starts the process. The default setting uses the process name you chose. Buttons for creation processes appear at the top left corner of the cases overview. Lifecycle process buttons show up in the detail view of an instance.
Name Formula
Every case has a case name which is displayed in the case overview.
Here you can define a formula in RuLa that calculates a name based on information provided in the case. When left empty, Atfinity will generate a case name based on the outcome instance and its ID.
Color Tag
Here you can select a color tag. In the Process overview screen, you will then see this tag next to your process. This helps you to easily find a specific process.
Start from Dashboard
Yes: the process can be started by clicking its button on the Dashboard.

Add Documents, Proofs and Rules

Next, add documents, proofs and rules to the process.
Having documents, proofs, and process rules present in the system is only a first step. However, their presence alone doesn't have any effect. To make them work, each document, proof, and process rule has to be attached to a process. Only then will they define how the process behaves, what questions are asked in a case, which documents are required, and when issues are raised.
The tab ‘Documents’ shows all the documents that are present in the system. If a document should be part of a process it needs to be selected from the list with the blue check mark.
Move to the 'Proofs' and 'Rules' tab, and add these elements to the process in a similar way as you do for documents.

Set Access Rights

In the ‘Access Rights’ tab you have the option to select the access rights of the different user Roles.
All Atfinity users have user roles assigned to them. Depending on the access rights you give a user role in your process, the user might only get read-only access to cases created with this process.
Access rights options are Read/Write, Read Only and No Access.
A user can start cases, read and write information.
Read Only
With Read Only access, users cannot start new cases. However, they are able to see (but not edit) cases which have been created with this process.
No Access
Users can neither start new cases nor see cases that have been created with this process.

Manage Notifications

Go to the 'Notifications' tab to define whether users should be notified when a case transitions from one state to another (e.g. from ‘Draft’ to ‘Compliance’).
The users that can be informed are the case initiator (the one who started a new case), the case owner (which, if unchanged, is the same as the initiator) or other users, according to a list of email addresses. Additionally it can be chosen whether users should be notified after every case transition or only the final transition. The latter is the transition to a final successful or failed state, e.g. 'Approve' or 'Declined', which closes the case.