8.6

updating the wrong document. When out of bounds ink is found, the document will be set
in the "Error"status. (see note below)
l Split PGCby document:Check to treat each document as a separate PGCfile. This
removes the need to use a Capture PGCsplitter before this task, however the
PGCSplitter remains useful when using self-replicating processes to accelerate
PGCprocessing.
l Add pattern information to the metadata:Adds advanced information in the Metadata
for post-processing:
l At the Document node, timestamp information such as ink start/end time
l At the Page node, information about each Capture Field such as its name,
dimensions, style, index, mask, timestamp and content status.
Technical
When the "ignore out of bounds ink data"option is checked, this option modifies the way
that the On Error tab reacts. When a single split is processed and generates an error,
only that split triggers the On Error tab. The other splits continue processing as usual. If
another split generates an error, it also triggers the On Error tab.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l Basic Functional Capture Workflow
l Capture Web Manager Workflow
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page723.
By default, any action task, branch, splitter or condition that generates an error will simply be
ignored, and the task just under it (not within a branch)will be given control of the job file
without any modification. Any initial input task that generates an error will stop the process from
running as a whole, and output tasks will not generate output. The On Error tab can be used to
overwrite the default behaviors.
Page 456