Rule events can be added to a process model in one of two ways. They can either be added to the process flow as a process node, or they can be used within an activity to trigger an exception flow.
At any time in a process model when there are certain conditions that need to be met before the process flow proceeds, an intermediate rule event should be used. Once an intermediate rule event is activated, it remains active until the rule evaluates to true.
To configure a Rule Event:
With an expression, you can use a Rule Event to monitor global constants and process variables. Each time a global constant or process variable is changed, the rule is reevaluated.
Best Practice: As a best practice, we recommend using conditions rather than expressions whenever possible because conditions consume fewer processing resources and less memory than expressions.
To build a Rule Event condition:
In the second list box, select the operator you wish to use for the condition. The following options are available:
|Select||To perform this operation…|
|<>||not equal to|
|<=||less than or equal to|
|>=||greater than or equal to|
To create an expression:
Expressions that are created as a rule must evaluate to true or false. Creating an expression that does not evaluate to true or false causes the expression to be automatically set to false.
You cannot use a record data type in this event. This means you cannot reference a process variable of type record data type, use a record field reference, or use a record type constructor; otherwise, an error will occur.