Partial Batch Export
The Partial Batch Export feature offers an alternate approach to exception processing, whereby a batch with documents or pages in error is not automatically routed to Quality Control for repair. Instead, a batch with errors is processed through the modules in the order originally defined for the batch class. Once the batch reaches the Export module, the error-free documents and pages are exported. The exception documents and pages are routed back to Quality Control for repair and then processed through the batch class workflow, starting with the first module after Scan. This approach is helpful if you do not want to delay batch processing for error-free documents or pages that exist in the same batch with exception items.
How Partial Batch Export Works
Select Partial Batch Export in the Administration module on the Batch Class Properties - Advanced tab. On the Advanced tab, you select the processing module at which Partial Batch Export should first go into effect. Starting with the specified module, rejected documents and pages are forwarded along with error-free items to the next module. The feature remains in effect for any modules in the workflow that follow the specified module.
For example, you might have Scan, Recognition Server, Validation, Verification, and Export set up as the processing modules for a batch class. Beginning with the Validation module, you specify that batches in error be advanced to the next module.
As a result, Partial Batch Export is not enabled for the batch if errors occur in the Scan or Recognition Server modules. If a bad document is detected in these modules, the batch is sent to Quality Control for repair. If a bad document is detected after the batch reaches the Validation module, the batch in error is forwarded through the workflow in the module order designated on the Batch Class Properties - Queues tab. After reaching the Export module, the error-free items are exported and the bad document is routed back to Quality Control for repair. The repaired item is then processed through the batch class workflow, starting with the first module after Scan.