Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Designer
  Search  |  Index
Process Reference  
Process Designer
Getting Started
Workflow Properties
Steps
Routes
  Create route
  Specify route properties
  Associate a response
  Specify routing expression
  Delete a step or route
Validate & Launch
   

About routing

To 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:

  • Participant responses. For example, if the participant had to respond by choosing either "red," "green," or "blue," you might define three routes leading from the step—one route for the red response, one for the green response, and one for the blue response.
  • An expression that references one or more fields in the workflow. For example, for a data field called LoanAmount, you might define one route to take if LoanAmount is greater than or equal to 100,000.00 and another route to take if LoanAmount is less than or equal to 99,999.99.

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:

  • Take the first route that evaluates to true. You can specify the order in which the routes are evaluated. The result of this choice is that work continues down a single path, regardless of how many true routes exist.
  • Take all routes that evaluate to true. The result of this choice is that work continues down multiple paths-specifically, all true routes. In this situation, you must also define a collector step that brings the work back into a single path at the end of all the true routes.

For step-by-step procedures, choose the appropriate topic:

How do I ...?

See:

Define routes between steps

Create a route between steps

Indicate that a route is "always true"
or has a condition

Specify route properties

Specify possible responses for a step

Specify responses

Indicate that taking a route is based on a response

Assign a response to a route

Specify a conditional expression for a route

Specify a routing expression

Indicate whether work following a step follows one path only
or multiple true paths

Specify outgoing routing

Designate a step as a collector step

Specify incoming routing

Ensure that the workflow map is valid

Create a valid workflow map