The Exceptions workflow offers users a suite of functionality geared specifically for tackling exceptions found within a reconciliation. This includes a modified interface with unique buckets that track the status of exceptions within the review lifecycle, as well as workflow tools to assist the review process itself. This feature is not enabled on process creation, but is typically switched on after the initial build phase has been completed.
With the Exceptions workflow enabled, Duco considers all partially matched and unmatched items from a run as exceptions requiring investigation. Our Exceptions workflow ensures that breaks are owned throughout a review lifecycle, and that this ownership is transparent. The diagram below illustrates the different paths that exceptions can follow within the review lifecycle.
When creating a process, the Settings Overview shows an option to select Exceptions workflow.
The Exceptions workflow preferences can be set after the process has been configured (at a minimum Data Inputs and Matched Fields will have to have been selected). If the process has not already been configured, you receive the following screen when selecting Exceptions workflow:
To enable the Exceptions workflow you must first select a Default group. This will be the user group with responsibility for advancing exceptions through the review lifecycle, and performing actions on any new exceptions, such as applying comments or labels. Other users with access to the process, but not in the default group, will have rights to assign exceptions, apply labels and make comments. They will not, however, be able to progress exceptions through the review lifecycle.
Only one Default group can be selected per process, although more groups can be granted with access in the Permissions section. It will then be possible to assign exceptions to users from those groups as well.
This will then allow you to check the Exceptions workflow enabled checkbox.