Folders and documents that require special handling can be routed to a specific module, allowing the rest of the documents in a batch to continue being processed. Parent batches can be separated into smaller child batches, and these child batches can be routed to the necessary modules based on their document requirements. This means that the parent batch may follow a different queue order than its child batches.

A document or folder can be flagged for routing with or without user intervention. You can provide a button on the validation form for a user to consciously flag a document or folder for routing. Alternatively, you can use these and other actions, such as rejecting a document during processing to flag a document for routing without the user being aware of what is happening.

Document Routing occurs after the Batch_Close event. At this time, the batch is checked for flagged documents and folders. If any flagged documents and folders are found, they are filtered out of the parent batch and one or more child batches are created. Each batch is then routed to the specified module for further processing.

You can configure the script to determine what module a batch is routed to, as well as specify the name of the child batches. This gives you significant control over how a batch behaves during processing.

For information about testing scripts, see Testing Runtime Script Events.

Example: Document Routing with Child Batches

An order form that includes payment information is processed by a Validation user. On rare occasions, problems with payment details require a second Validation step so an expert can solve the problem. If every order form is processed by both steps, even when the second step is not necessary, it is a waste of time.

Document Routing can be configured so all documents by-pass the second Validation step unless there is a problem with the payment details.

The following image shows how after the first Validation step, the batch is split into two child batches. Each batch then follows its own path to completion. The first goes directly to Verification, while the second goes to the second validation step first. It then follows on and is processed in Verification.