![]() ![]() |
|
Help for Process Engine Reference | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
About routingTo specify how work will progress from one step to the next, you define routes between the steps in a workflow definition. With the exception of the last step on the map, every step has one or more routes leading from it. You define every route as being either "always true" at runtime or having a condition that is either true or false at runtime. A condition is based on one or a combination of the following:
In general, when there is only one route leading from one step to the next, you specify the route as being always true. When the participant completes the step, the work progresses to the next step. Alternatively, you can define a condition for the only route from a step; in this case, the workflow will stop when the participant completes the step if the condition does not evaluate to true. At runtime, whether a route evaluates to true or false is the primary factor in determining whether the route is taken. When there are multiple routes from a step, and more than one of those routes evaluates to true, how the step is defined to handle this occurrence is another factor in determining whether a route is taken. The options for handling multiple routes are:
|
![]() |
|
![]() |
|