Versions Compared

Old Version 27

changes.mady.by.user Mercedes Rothwell

Saved on

compared with

New Version Current

changes.mady.by.user Gints Vaskums

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In every Docupace site's User Access Domain, there's a New Processor field for each record. Enable it withYes or disable it with NoIt 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 their quality control (QC) N-th rate 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 places on a Pre-Review node.

How to Set a New Processor

Rw ui steps macro
Rw step

Navigate to Administration and search for User Access (300) Domain.

Rw step

Open the required Workflow.

Rw step

In the Details section, set the flag to Yes for the New Processor.

Process of Using New Processor Flag

...

Rw ui steps macro
Rw step

The Back-Office user is flagged in the user access system with the status "New Processor = yes Yes."

Rw step

The system checks if the transition is set to the assigned processor (Figure 3) and processes the Work Item in the background. 

Rw step

The system assigns the QC Meta Task Activity as a default queue for all Work Items where the QC decision is true. Based on QC calculation, if an item is marked for QC, it will be sent to the QC Meta Task. Criterion is:

  • the N-th sample rate on the Request Category (Figure 4) or

  • the User Access record for the user is set as a New Processor (Figure 3).

Rw step

If the workflow requirements specify the use of another Meta Task for QC, such as Pre-Review5 or Preview6, the configuration analyst will need to perform several steps.

  • First, they will need to add the specified Meta Task to the Request Category.

  • Then, they will need to rename it to QC.

  • Finally, they will need to add a Meta Task Condition that aligns with the criteria for QC, which could include conditions such as the N-th rate or the New Processor flag.

Rw step

Note: For all Meta Tasks - if other Meta Task conditions are on the same queue, standard “AND” and “OR” rules apply (Figure 5):

  • all AND conditions must be true

  • only one OR condition must be true.

05. And Or Conditions.png