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
l ICRSettings group
l Perform ICRRecognition:Triggers the PlanetPress Capture ICRengine. For more information,
see PlanetPress Capture ICR.
l Engine Language:Define the language the ICRengine 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 ICRdatabase.
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 PGCthat 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 PGCby document:Check to treat each document as a separate PGCfile. This removes the
need to use a Capture PGCsplitter before this task, however the PGCSplitter remains useful when
using self-replicating processes to accelerate PGCprocessing.
l Add pattern information to the metadata:Adds advanced information in the Metadata for post-
processing:
l At the Document node, timestamp information such as ink start/end time
l At the Page node, information about each Capture Field such as its name, dimensions, style,
index, mask, timestamp and content status.
Technical
When the "ignore out of bounds ink data"option is checked, this option modifies the way that the On
Error tab reacts. When a single split is processed and generates an error, only that split triggers the
On Error tab. The other splits continue processing as usual. If another split generates an error, it also
triggers the On Error tab.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l Basic Functional Capture Workflow
l Capture Web Manager Workflow
On Error Tab
The On Error Tab is common to all tasks. Details can be found on " Task Properties Dialog" on page 587.