Routes are the links between Actions and Tasks to build relation within process which build relations within the process diagram.
You can draw multiple routes, from a single action to the multiple tasks to split workflow in more than a one branchesbranch. If no route is found, or all of the routes are invalid, workflow is automatically terminatesterminated.
For a route you can configure the following properties from the context menu:
Instructions
If specified, replaces the next task instructions with entered the provided instruction. This property is useful when if you want to override the default task instruction. For example an a "Reject" action may change the next task instructions with the approve task.
Validation Rule
Validation rule specifies the route is valid as a next task in processesthe process. Rule content can be a Decision Table or a scripting expression. Route is assumed as valid if not any condition is defined.
...
Route Validation with a Decision Table
Following a decision table specifies the route is valid if form field "Department" is set to a "Sales" or an "Accounting" value. All of the other values are invalidates invalidate the route.
Route Validation with an Expression
Validation rule can also be written as an expression. Expression language specifies how the how content is will be interpreted.
If FEEL expression is preferred expression can be specified as;
Same expression can also can be written as a javascript expression, as following;:
