Routing Scenario

The routing scenario feature allows users to predefine document workflow in detail. For example, in the image below, DocBoss knows to assign a specific set of reviewers based on the file's return source (customer) and whether or not the st...

This article explains how to add or edit routing scenarios. For an overview of routing scenario functions, see this article first. Topics Add routing scenarios Edit routing scenarios Add/edit routing scenarios for all new pro...

After creating routing scenarios , users can apply them to doc codes or cards. Apply routing scenarios to doc codes (individual) If a routing scenario is available to use on a project already, select it from the Routing Scenario drop...

If using stage lists with multiple stages, it is possible to assign a different routing scenario to each stage the documents pass through. First, ensure the correct Stage List is selected for the doc code (or card). If needed, save to apply t...

Every time a new workflow stage begins, a card is set to NULL status (exceptions exist, but are not typical). Users may want to assign the card to a specific user, responsible to upload that card. This is done using routing scenarios . All ...

Default/forced routing can be defined for any stage. You can define an assignment for all cards which come back either as COMPLETE, or INCOMPLETE. 1. Review when stage is NOT COMPLETE If users set values for “Review when stage is n...