For every Docupace site in In the User Access Domain , for of every recordDocupace site, there is a field called ‘New Processor’. It 'New Processor' for each record. This field can be enabled (set to ‘Yes') or disabled (set to 'No’). TheNew Processor Flag affects all request categories (workflows). Each request category or workflow may have different by setting it to 'Yes' or disabled by setting it to 'No'. The 'New Processor' flag impacts all request categories or workflows, regardless of the rules related to quality control (QC) N-th rates . Regardless of the request that each category or workflow , may have. If the 'New Processor flag ensures ' flag is set to 'Yes', all items are processed by a user or Back Office through post-processing queues and go are sent to QC for review. If ‘New Processor’ On the other hand, if the 'New Processor' flag is set to ‘No’ then 'No', the regular N-th sample rate applies, and those route items are routed to QC accordingly.
Note: This functionality only applies to out-of-the-box QC nodes and not to any QC Meta Tasks a client might be placing on a Pre-Review node.
...
| Rw ui steps macro | |||||
|---|---|---|---|---|---|
Back Office user gets flagged under user access as New Processor = yes.
The system checks if the transition is set to the assigned processor (Figure 3). If yes, the system processes the Work Item in the background.
The system assigns the QC Meta Task activity as a default queue for all Work Items where the QC decision is
If the workflow requirements call for another Meta Task to be used as QC, for example, Pre-Review5 or Preview 6, the configuration analyst will need to add the Meta Task to the Request Category, rename it to QC, and add a Meta Task Condition that meets the criteria for QC (N-th rate or New Processor flag)
For all Meta Tasks - if other Meta Task conditions are on the same queue, normal standard “AND” and “OR” rules apply (Figure 5):
 |
...