Page Comparison

Routes are the links between Actions and Tasks to build relation within process that build relations within the process diagram.Image Removed

...

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

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

Instructions
If specified replaces , replace the next task instructions with entered instructionthe provided instructions. 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 approve the approved task.

Validation Rule
Validation The validation rule specifies the route is valid as the next task in processesthe process. Rule content can be a Decision Table or a scripting expression. Route The route is assumed as valid if not any 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 are invalidates invalidate the route.Image Removed

...

Route Validation with an Expression

Validation The 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;

Image Removed

...

Department in ("Sales", "Accounting")

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

Image Removed

...

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