In the every Docupace site's User Access Domain of every Docupace site, there is 's a field called 'New Processor' field for each record. This field can be enabled by setting it to 'Yes' or disabled by setting it to 'No'. The 'New Processor' flag impacts It allows you to flag work items processed by a specific user and pull them in for review. Usually, this flag is used when a new employee joins the team. The New Processor flag affects all request categories or workflows, regardless of the rules related to their quality control (QC) N-th rates that each category or workflow may haverate rules. If the 'New Processor' flag is set to 'Yes
', all items are will be processed by a that user or Back-Office user through post-processing queues and are before being sent to QC for review. On the other hand, if the 'New Processor' flag is set to 'No
', the regular N-th sample rate applies, and those items are routed to QC accordingly.
Note: This functionality only applies to out-of-the-box QC nodes and not to any custom QC Meta Tasks in a client might be placing on a Pre-Review node.
How to Set a New Processor
Rw ui steps macro | |||
---|---|---|---|
Go Navigate to Administration and search for User Access (300) Domain.
Open the required Workflow.
In the Details section, set the flag to |
Process of Using New Processor Flag
The This attribute serves the business purpose for this attribute is to supervise of overseeing new Back-Office employees processing as they process Work Items.
Note: QC is related to the user assigned to process the Work Item, not the user who created the Work Item.
It works the following way:
Rw ui steps macro | |||||
---|---|---|---|---|---|
The Back-Office user gets is flagged under in the user access as system with the status "New Processor = yes
The system checks if the transition is set to the assigned processor (Figure 3) . If yes, the system and processes the Work Item in the background.
The system assigns the QC Meta Task activity Activity as a default queue for all Work Items where the QC decision is
If the workflow requirements call for specify the use of another Meta Task to be used as for QC, for example, such as Pre-Review5 or Preview 6 Preview6, the configuration analyst will need to perform several steps.
Note: For all Meta Tasks - if other Meta Task conditions are on the same queue, standard “AND” and “OR” rules apply (Figure 5):
|
...