Document integrity problem management
You can manage document integrity problems by routing a batch to a job that fixes the problems.
The Document Integrity ruleset demonstrates how to handle document
integrity problems. The Batch Route To Fixup function
is started only if CheckAllIntegrity returns a value
of False.
A document integrity problem can be pages in the wrong order,
or a missing required page. If CheckAllIntegrity identifies
a document integrity issue, the application sends the batch to a Fixup job.
An operator then fixes the problem and returns the batch to the main
workflow. Moving a batch out of the current workflow in this way is
known as branching.
Status = 1, which
indicates a problem. You cannot complete the Fixup job unless the Status on
all pages is 0, which indicates that there is no
problem. You can configure your application to use two separate task
profiles so that Datacap branches
to FixUp before recognition if there are document integrity problems.
For details about using two task profiles, see the topic Creating the CreateDocs task. The Batch Route To Fixup function uses these rrunner actions
to branch to the Fixup job.
| Library | Action | Description |
|---|---|---|
| rrunner | Task_NumberOfSplits | Specifies the number of jobs to which the batch is sent to before the branch returns to the main workflow (almost always 1). |
| rrunner | Task_RaiseCondition | Specifies the group index (almost always 0)
and the index of the condition to raise, where 0 is
the first condition. The index is including on a list on the Datacap Web Client, Administrator tab, Workflow page. To view the Workflow page, start the Datacap Web Client, log on to the TravelDocs application, click the Administrator tab, and click Workflow. |
Before Datacap can
branch to the FixUp job, you must configure the settings on the Document
Integrity Failed condition. See the topic Configuring branching.