7.5

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
l CapTemplateName:Name of the PlanetPress document used to generate the document.
l Page Level:
l CaptureField:Information on each capture field on the page. Repeated for each capture field that is present.
There is currently no method of obtaining the information from a PGC except through a successful processing of this
task, or via the use of the PlanetPress Capture API within a Script (see Using Scripts)
Properties
Capture Fields Processor action task properties are as follows:
l PGCName: This value will be added to the output metadata, as well as the Capture Database, to link the PGCto the
document it updates.
l Pattern sequence group
l Type:Specify from where the Pattern Sequence should be taken.
l None:Do not use a Pattern Sequence.
l Pen Information:Use the Pattern Sequence assigned to the pen in the PlanetPress Capture Database.
l Custom:Overwrite the pen's information and specify a Pattern Sequence manually or use a data selec-
tion.
l Custom Pattern Sequence:If you choose Custom in the Type drop-down, enter a manual Pattern
Sequence or a data selection that contains the Pattern Sequence to be used.
l ICRSettings group
l Perform ICRRecognition:Triggers the PlanetPress Capture ICRengine. For more information, see Plan-
etPress Capture ICR.
l Engine Language:Define the language the ICRengine will use for text recognition. This has a major effect
on the way text is recognized, as different languages use different databases to recognize letters, numbers and
characters. For example, accented letters are not correctly recognized in the English ICRdatabase.
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 Cap-
ture PGCsplitter before this task, however the PGCSplitter remains useful when using self-replicating processes to
accelerate PGCprocessing.