8.4
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.4.1
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
must review and understand the Critical PlanetPress Capture Implementation Restrictions.
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.
Processing
The Capture Fields Generator action task uses an existing PlanetPress Connect document containing
Capture fields and assigns a unique Capture pattern to each printed page. The task then locks each pattern
that it used so it cannot be reassigned to any other document.
The whole job is then converted into a PDFfile which is stored, without the patterns, in the Capture
Database. This PDFfile is later used by the "Capture Fields Processor" on page 369 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 PDFis always generated in
the database.