Routes

Routes are the links between Actions and Tasks that build relations within the process diagram.

You can draw multiple routes, from a single action to multiple tasks to split workflow in more than one branch. If no route is found, or all of the routes are invalid, the workflow is automatically terminated.

For a route, you can configure the following properties from the context menu:

Instructions
If specified, replace the next task instructions with the provided instructions. This property is useful if you want to override the default task instruction. For example, a "Reject" action may change the next task instructions with the approved task.

Validation Rule
The validation rule specifies the route is valid as the next task in the process. Rule content can be a Decision Table or a scripting expression. The route is assumed as valid if no condition is defined.

Sample Validation Rule

Route Validation with a Decision Table

Following a decision table specifies the route is valid if the form field "Department" is set to a "Sales" or an "Accounting" value. All of the other values invalidate the route.

Route Validation with an Expression

The validation rule can also be written as an expression. Expression language specifies how the content will be interpreted.

If FEEL expression is preferred expression can be specified as;

Department in ("Sales", "Accounting")

The same expression can also be written as a javascript expression, as follows:

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



Copyright © 2010 - 2023 Emakin. All rights reserved.