8.5

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.
l CapPatternSequence:The value of the pattern sequence assigned to the document.
l CapPGCName:The name of each PGCfile that was used to update this document (will repeat
for each PGCfile)
l CapStatus:Current status of the document:
l 0:Open
l 1:Closed by an optional field
l 2:Closed by a mandatory field
l 3:Closed by a final field