Restricting When a Lifecycle Process Can Start¶
Info
New in Atfinity 17.
By default, the button to start a lifecycle process shows for every instance of the ontology the process is built on. Adding a condition to the process narrows that down to only the instances that match it.
Adding a condition¶
Turning on 'Does this process have a condition?' reveals a 'Condition' field. The condition is a RuLa expression, and self, the instance the button would be shown for, is the only reference it can contain.
The button to start the process shows only while the condition evaluates to true. It is hidden whenever the condition evaluates to false, or cannot be evaluated at all, in every interface where the button would otherwise appear.
Once 'Does this process have a condition?' is turned on, the 'Condition' field cannot be left empty, and the expression must reference self. Either mistake is a configuration error that blocks Put Live, see Why does Put Live fail?.
Example¶
A bank has two lifecycle processes built on the same Client ontology, a review for individual clients and a review for corporate clients.
The individual clients' review uses:
The corporate clients' review uses:
Each client then sees only the review process that matches their client type.