2018.1

During processing, ink is always applied to the document first and then the logic is applied for
releasing patterns. This means that even if a document is closed by a field set as Final that was
checked first, ink present in other fields will still be applied to the document.
From version 7.5 and onwards, ICR is done on the ink, if the "Perform ICR Recognition" option
is checked.
Error handling
If the Capture Fields Processor generates a critical error during the processing of any document
in the PGC file, all of its actions will be reverted. If your PGC file contains multiple documents,
even those documents that were processed before will revert. It is strongly suggested to backup
your PGC file before using this task and to create an error handling process to capture these
errors.
Logical errors do not cause this task to exit. For example, if a List Item Capture Field is set to
only accept a single option but contains ink in more than one option, or if a Capture Field that
does not accept re-writing receives more ink, the task will still complete. The inks that are
relevant to logical errors are still added to the PDF document, but they are added on a separate
"error" layer.
Output
This task outputs the PGC file it received along with Metadata that contains the documents that
have been updated by this task. The Metadata can be used to do post-processing of the file
using Capture Conditions, or directly through other Metadata tools. The structure of the output
Metadata added by Capture is the following:
l
Document Level
l
CapCloseDate: Date at which the document was closed by Capture Field
Generator. Blank if the document is still open.
l
CapDocID: The database ID of the document. This field is useful especially if using
the Capture API since the ID corresponds to the itembyID function.
l
CapDocName: The name of the document as specified in the Capture Field
Generator.
l
CapOpenDate: The date at which the document was created by the Capture Field
Generator.
Page 404