Configure a Sequential Routing Plan

The configuration of a sequential Routing run always includes selection of a predecessor Routing plan, that is, the one to be completed before the current one starts. Any Routing plan, regardless of its schedule, can be selected as predecessor. However, any Routing plan can have only one successor, therefore, whenever a sequence has already been created, the predecessor Routing plan of such sequence can no longer be selected for other sequences. Its name is disabled in the list.

This screenshot shows the settings for a sequential routing plan:

Sequential Routing plans can be used as predecessors creating longer sequences, if the business needs so require. Other routing plan settings depend on the company specifics and are not influenced by the sequential nature of the Routing plan.

Note: Routing plan sequences can only be created within one routing profile. Sequences of Routing plans between different Routing profiles are not supported. The Routing plan summary shown in the Routing plan header contains its schedule – Sequentially after [predecessor_Routing_plan_name].

A Routing plan belonging to a sequence cannot be deleted unless detached from the sequence. On an attempt to delete such Routing plan, the action is rejected with the [Routing_plan_name] is already in use and cannot be deleted error message. To detach a Routing plan, change the schedule from sequentially to any other, starting from the last plan in the sequence. This restriction applies to all plans in a sequence regardless of their position. The system prevents creation of Routing plan chains forming closed loops in which the first plan is to be started after the completion of the last one. If the first Routing plan in the sequence is changed to the sequential schedule to start after the completion of the last plan in the same sequence, the modification is rejected with the Routing plan {plan_name} cannot be processed error message.