2022.1

The Capture-Fields generator action task is used to generate Capture patterns in your job,
which will then be printed for use with an Anoto Digital Pen. It also interacts with the Capture
database and does some operations.
Warning
PlanetPress Capture Fields cannot simply be inserted into an existing document as-is
and expected to work properly, efficiently or consistently. In order to design a document
with Capture Fields, you must review and understand the Critical PlanetPress Capture
Implementation Restrictions.
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 document. 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 creates 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 database 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 beginning.
Page 703