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
Processing
The PlanetPress Capture Fields Processor action task receives and processes the information sent by the
Anoto digital pen and updates all the documents in the PlanetPress Capture Database using the information
from the pen. Any ink in the pen is added as an EPS(image)layer on the PDFinside the Capture Database.
If a specific document needs to be closed to release its pattern, this task does so.
During processing, ink is always applied to the document first and then the logic is applied for releasing
patterns. This means that even if a document is closed by a field set asFinal that was checked first, ink
present in other fields will still be applied to the document.
From version 7.5 and onwards, ICRis done on the ink, if the "Perform ICRRecognition"option is checked.
Error Handling
If the Capture Fields Processor generates a critical error during the processing of any document in the
PGCfile, all of its actions will be reverted. If your PGCfile contains multiple documents, even those
documents that were processed before will revert. It is strongly suggested to backup your PGCfile 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
PDFdocument, but they are added on a separate "error"layer.
Output
This task outputs the PGCfile 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 IDof the document. This field is useful especially if using the Capture
API since the IDcorresponds to the itembyIDfunction.
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.