Routing entities based on a condition such as the value of a variable or attribute. If a routing decision is based on a condition of the entity such as customer type, use an attribute. If it is based on a condition external to the entity such as the total number of entities processed, or the time of day, use a variable.
1. Create an attribute or variable to which the possible conditions may be assigned.
2. Create the desired routings and for each select Conditional in the Type field.
3. Enter the condition in the Condition field of the properties dialog for each routing connection.
Example: Paid invoices are routed to filing. Invoices that are current are routed to the receivables desk, and those that are 30 days past due are routed to the collections desk.
TO DO: Create an attribute called a_Status which may be assigned three descriptors ( Paid , Current , and Past_Due ). Connect the activities, select Conditional type and enter the condition on the General tab of the properties sheet as shown above.
- The order you draw conditional routes is significant. For example, if the condition on the route drawn first is always true (Condition field is left blank), the other routes will never be tested because a true condition was found on the first route.