Routes

Routes represent the order in which operations on the process diagram are executed. Two operations can be connected using a route to represent a sequential flow. Routes begin at one operation and end at the operation that is to be executed next. Arrowheads indicate the order of progression.

Routes can also begin and end at activity elements, events, and gateways.

Multiple routes can originate at a single operation. However, within in a branch, only one route can be followed, and a decision needs to be made to determine how to proceed:

Each route is evaluated to determine whether it is valid.
The first route that is found to be valid is followed.
The order in which the routes are evaluated is configured at design time.
Tip: If you need operations to execute in multiple branches simultaneously, use a gateway. (See Gateways.)

Conditions are logical expressions that can be associated to routes and are evaluated at run time to determine whether a route is valid. Conditions typically compare values against data that is gathered at run time so that decisions are made based on the context of the process instance. Routes can have multiple conditions. Routes that have conditions appear as dashed lines, and routes that do not have conditions are solid lines.

Note: Routes that do not have conditions are always valid.

For example, a company's internal process for requesting purchases is automated using LiveCycle ES. To start the process, a user fills and submits a form using Workspace ES. The user's manager opens the form in Workspace ES and selects an option to either decline or approve the purchase. The decision determines the next operation in the process, which is to either return the form to the originator (the purchase is declined) or to send the form to the accrual department (the purchase is approved).

On the process diagram, the decision is represented by two routes that originate at the same operation. One route has a condition associated with it that evaluates whether the manager denied the purchase. If the condition is true (the request was denied), the route is followed. If the condition is false, the other route is evaluated.

When no valid routes are found after an operation is complete, the process is complete. Therefore, when multiple routes originate at an operation, typically one of the routes is not given a condition and is evaluated last. This route is followed by default if the other routes are evaluated and found to be invalid. This design ensures that the process continues to progress after the operation is complete.

Each route has a name that you can customize to provide meaning. Typically, the name provides insight into the condition that is associated with the route. Route names can also be exposed as form submission options for Workspace ES users. (See Using route names as submit options.)

Routes

See also