2021.1

l
Fail if new ink is found on non-rewritable fields: Check to trigger the On Error tab if
and when a field set as Disable Rewriting receives ink in a new session.
l
Ignore out of bounds ink data: Check to continue processing even if receiving a PGC
that causes ink to be outside of any Capture Field to appear. This may happen if
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.
Note
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.
Miscellaneous Tab
The Miscellaneous tab is common to all tasks.
Check the option Use as step description to display the text next to the icon of the plugin in
the Process area.
Capture PGC Splitter
The Capture PGC Splitter task can be used to separate each document into its own PGC file
so they can be processed separately. The splitter then sends each document PGC to the next
action, which should be the Capture Fields Processor task. Note that using the Capture PGC
Page 548