Routes¶

Routes define the connections between Actions and Tasks, establishing the workflow's path.

Multiple routes can branch from a single action, creating parallel workflow paths. If no valid route is found, the workflow terminates.

Route Properties¶

Instructions: Overrides the next task's instructions. Useful for dynamically updating instructions based on the action taken (e.g., changing instructions after a "Reject" action).

Validation Rule: Determines the route's validity. The rule can be a Decision Table or a scripting expression. A route is considered valid if no validation rule is defined.

Sample Validation Rules¶

The following examples demonstrate route validation using decision tables and expressions.

Route Validation with Decision Table¶

This decision table validates the route if the "Department" field is "Sales" or "Accounting". Other values invalidate the route.

Route Validation with Expression (FEEL)¶

Using FEEL:

1

Department in ("Sales", "Accounting")

Route Validation with Expression (JavaScript)¶

Using JavaScript:

1

$Xml.Equals('Department', 'Sales') || $Xml.Equals('Department', 'Accounting');