Capture Fields Processor

The Capture fields Processor Action Task is used to update the Capture Database using information received from an incoming PGC file, which generally originates from a communication by the Anoto penDirector.

Input

This task requires a PGC file that has been obtained from an Anoto Digital Pen that was used to write on documents generated from the same PlanetPress Production installation.

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 PDF inside 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 as Final that was checked first, ink present in other fields will still be applied to the document.

From version 7.5 and onwards, ICR is done on the ink, if the "Perform ICR Recognition" option is checked.

Error Handling

If the Capture Fields Processor generates a critical error during the processing of any document in the PGC file, all of its actions will be reverted. If your PGC file contains multiple documents, even those documents that were processed before will revert. It is strongly suggested to backup your PGC file 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 PDF document, but they are added on a separate "error" layer.

Output

This task outputs the PGC file 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:

Document Level
- CapCloseDate: Date at which the document was closed by Capture Field Generator. Blank if the document is still open.
- CapDocID: The database ID of the document. This field is useful especially if using the Capture API since the ID corresponds to the itembyID function.
- CapDocName: The name of the document as specified in the Capture Field Generator.
- CapOpenDate: The date at which the document was created by the Capture Field Generator.
- CapPatternSequence: The value of the pattern sequence assigned to the document.
- CapPGCName: The name of each PGC file that was used to update this document (will repeat for each PGC file)
- CapStatus: Current status of the document:
  - 0: Open
  - 1: Closed by an optional field
  - 2: Closed by a mandatory field
  - 3: Closed by a final field
- CapTemplateName: Name of the PlanetPress document used to generate the document.
Page Level:
- CaptureField: Information on each capture field on the page. Repeated for each capture field that is present.

There is currently no method of obtaining the information from a PGC except through a successful processing of this task, or via the use of the PlanetPress Capture API within a Script (see Using Scripts)

Properties

Capture Fields Processor action task properties are as follows:

PGC Name: This value will be added to the output metadata, as well as the Capture Database, to link the PGC to the document it updates.
Pattern sequence group
- Type: Specify from where the Pattern Sequence should be taken.
  - None: Do not use a Pattern Sequence.
  - Pen Information: Use the Pattern Sequence assigned to the pen in the PlanetPress Capture Database.
  - Custom: Overwrite the pen's information and specify a Pattern Sequence manually or use a data selection.
- Custom Pattern Sequence: If you choose Custom in the Type drop-down, enter a manual Pattern Sequence or a data selection that contains the Pattern Sequence to be used.
ICR Settings group
- Perform ICR Recognition: Triggers the PlanetPress Capture ICR engine. For more information, see PlanetPress Capture ICR.
- Engine Language: Define the language the ICR engine 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 ICR database.
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.
Ignore out of bounds ink data: Check to continue processing even if receiving a PGC that 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)
Split PGC by document: Check to treat each document as a separate PGC file. This removes the need to use a Capture PGC splitter before this task, however the PGC Splitter remains useful when using self-replicating processes to accelerate PGC processing.
Add pattern information to the metadata: Adds advanced information in the Metadata for post-processing:
- At the Document node, timestamp information such as ink start/end time
- At the Page node, information about each Capture Field such as its name, dimensions, style, index, mask, timestamp and content status.

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:

On Error Tab

By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and the task just under it (not within a branch) will be given control of the job file without any modification. Any initial input task that generates an error will stop the process from running as a whole, and output tasks will not generate output. The On Error tab can be used to overwrite the default behaviors.

Send to Process: Check this option to send the job file to an error management process.
Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available:
- Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process.
- Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
- Stop Process: The process is stopped and no more processing is done. No further output is produced.
Log Message: Check this option to enable logging a custom error message in the PlanetPress Suite Workflow Tools' log file.
Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PlanetPress Suite Workflow Tools' log file. You can use any variables available in PlanetPress Workflow to customize the message.
Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content.
ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PlanetPress Suite Workflow Tools' log file.
Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID.
Reset to defaults: Resets all options in this tab to their default values.

If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.

Common Errors

Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc.

Comments Tab

The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in The Task Comments Pane.