Processes in atfinity are guided by rules.
A rule tells the application what actions it should take, when a specific condition is met.
Each rule can trigger multiple actions, from ensuring defined instances are present in a case to issuing a warning, from sending out an email to performing a background check.
When naming a rule, pick a name that says what the rule is for.
  • 'Two account holders required for joint account'
  • 'Applicant for entity account must be of low risk class'
  • 'World-Check required for non-EU account holder'
Currently, you can attach one or more of the following actions to a rule:
Raise an issue to alert a user to something that requires attention. Issues are marked with a red icon. The process cannot function properly until issues are fixed.
Display a warning. Warnings are marked with a grey icon, because they're less severe than issues. Ignoring warnings will not stop the system from working.
Add a comment to a case, which will have no other implication than to simply inform a user of something.
atfinity will check that the instances you specify in this action are actually present in the case. If they are not, atfinity will create them.
Selected roles will be required and available in a case for users to assign them to instances.
Have atfinity assign a designated value to a specified information field.
An email will be sent, according to a template and/or input values you specify in this action.
This action triggers communication with the external World-Check database, to search for any hits a person might have there.
Create an IDnow link, and have it emailed to a specified address.


The condition under which you want a rule to trigger the action(s) you attach to it, are written in RuLa - atfinity's rule language.
Here's an example of a condition:
cr is ContractualRelationship
cr.type_of_account = joint
When a contractual relationship in a case has a joint account, this condition is met. That means the action(s) you attach to the rule this condition belongs to, will be executed. For example, the action Ensure Instances could be triggered to automatically ensure two account holders for this case.
Had the case been about a contractual relationship with an individual account, the condition is false. No actions will be triggered.

Adding to a process

Only when rules are added to a process are they being used. atfinity evaluates these rules to determine the flow of a case through a process, depending on the specific characteristics present in the case.