Routes connect workflow queues. They can be inbound or outbound or both. You can also route to a queue contained in the
same process or to a queue in a different process.
Sequential routes - A sequential route is a clearly defined route with little variation. One action must be completed before the workflow item is routed to the next queue. Manual routes are used when there is more than one queue an item might be routed to next. Sequential routes require the user to select the destination queue from the available routes list.
Sequential Auto routes - A sequential auto route is a clearly defined route with no variation. One action must be completed before the workflow item is routed to the next queue. Automatic routes require no additional user interaction after the Route button is clicked. There is only one queue the item can route to next, so it is automatically sent to that queue.
Parallel routes - A parallel route allows multiple actions to take place at the same time. Multiple processing of the same document can occur and be brought together at a specified queue. When all processes are completed, the next action is initiated. With a parallel route, a workflow item is routed to more than one queue at the same time and when all actions on the item (sibling) are complete, the sibling items are routed forward and rejoined in ajoin queue. Items you route into a queue in parallel cannot be routed to another parallel route because they are already split.
Conditional routes - A conditional route is a route that is determined by rules that occur dynamically in the process. The next queue in the process is determined by information received by the workflow process. For example, in an approval process where an invoice over $5,000 must go to the Finance Director, the process automatically routes invoices greater than that amount to the Finance Director.
Parallel Conditional routes - A parallel conditional route is a route that allows multiple actions to take place at the same time and also allows you to place conditions on the route.
Load Balance routes - A load balance route processes high volumes of items, such as ten thousand or more items per day, and allows you to route items using distribution. The distribution option you select determines how Perceptive Content routes your items. You can choose to route using a high volume loadâ€”balancing algorithm that distributes approximately the same number of items among the destination queues. As an example, when you define four destination queues and there are 20,000 items, this distribution option routes approximately 25 percent of items to each queue. Alternatively, you can choose to route items to the destination queue with the fewest number of items. This option means that the faster a user processes items, the more items they receive.