2022.2

This task is put into effect in the following use cases and example processes:
l
Basic Functional Capture Workflow
l
Capture Web Manager Workflow
Input
The Capture Field Generator action task expects to receive a regular data file that corresponds to the
Capture-Ready document that uses it, along with Metadata generated using the same data file and doc-
ument. This means that this task must be preceded by at least the Create Metadata task.
This metadata must also be correctly separated at the documents level, either in the Capture-Ready
document's properties or through the Metadata Level Creation task.
You may also use a Metadata Sequencer task in order to split the job into multiple parts. This both cre-
ates multiple smaller outputs, as well as multiple smaller PDFs in the Capture database. While it is not
recommended to separate each document on its own as it removes all optimization and makes the data-
base much larger, you may split into document batches such as 250, 1000 or 2500 documents.
If using the Metadata Sequencer it is generally recommended to place the Sequencer and the Capture
Fields Generator tasks within a branch and, within the Capture Field Generator's On Error properties
tab, to set it to stop the branch if any errors occur. This is to ensure that if such an error occurs most of
your document sequences will get generated and you will not have to start the job over from the begin-
ning.
Processing
The Capture Fields Generator action task uses an existing PlanetPress Design document containing
Capture fields and assigns a unique Capture pattern to each printed page. The task then locks each pat-
tern that it used so it cannot be reassigned to any other document.
The whole job is then converted into a PDF file which is stored, without the patterns, in the Capture
Database. This PDF file is later used by the "Capture-Fields processor" on page624 to be merged with
ink from the pen. At the same time the output is generated, either as a PDF (including the patterns) or
an Optimized PostScript Stream file. This means that regardless of the output, a PDF is always gen-
erated in the database.
Note: If any error occurs during processing, such as running out of patterns while generating the
job, every action made by this task will be rolled back as if they hadn't happened.
Output
The Capture fields Generator action task will output either a PDF and Metadata, or an Optimized
PostScript Stream file without Metadata.
Page 622