Conditional Routing Overview

Conditional routing lets designers create application workflows that automatically route an item to a particular state based on visually designed rules that evaluate item data. They are used in decisions to determine which outgoing transition is executed. (For information about rules, see About Rules.)

One or more incoming transitions lead from one or more source states to a decision, and two or more outgoing transitions lead from the decision to their respective target states. The rules are evaluated in the order you specify in the Rules Tab of the Decision Property Editor. If a rule evaluates to "true," the associated transition is taken.

The last transition in the Property Editor list must be mapped to an "Otherwise" rule. This transition is taken if the last rule evaluates to "true" or if no rule evaluates to "true."

Note: For step-by-step instructions for using conditional routing, see Conditional Routing Tutorial. For examples of how conditional routing can be used, see Use Cases: Conditional Routing. For ways to implement conditional routing most effectively, see Best Practices: Conditional Routing.

Key Benefits

Conditional routing is an intuitive way to route items based on certain conditions. You no longer need to use actions and AppScripts to accomplish this.
The decision in the workflow editor lets you see the routing options at a glance.
A rules editor lets you build rule expressions graphically.
The Property Editor for the decision displays the rule associated with each outgoing transition, and optionally shows detailed information about the rule and its associated transition. You can open the rules editor from this Property Editor to add and edit rules.
Application variables make it easy to create and maintain rules.

Conditional Routing Overview

Key Benefits

Related Topics