7.4

l After:If the first stroke found in the Capture Field was made later than the specified date and
time, the condition becomes true.
l In the last:If the first stroke found in the Capture Field was made within the specified number
of Hour(s), Day(s) or Week(s) counting backwards from the moment the PGCis received, the con-
dition becomes true.
l End timestamp: Triggered when the last stroke finishes in the field. (see Start Timestamp for detailed
options)
l Pen Id: Triggered by the ID(serial number)of the pen. A box provides a way to specify which Pen
IDwill trigger this condition to be true.
l Field List Value: Triggered only on Field List Capture Fields. Abox provides a way to specify which
value will trigger this condition to be true.
l Content Status:Triggered when the field is in a specific status. ADrop-down provides a way to select
which status will trigger this condition to be true.
l Complete:The field contains ink and no error was detected.
l Empty:No ink was found in the field.
l Error:A logical error was detected in the field. This can happen, for example, if a field was re-
written when it should not, a List Field set to only accept one option contains ink in both options,
etc.
l
button:Add a new field and action line.
l
button: Remove the currently selected line.
l The condition is true when: Specifies how to react when more than one Capture Field based condition is present
l All items are met: The task will return true if ALLthe combined conditions are true.
l At least one item is met: The task will return true if ANY of the combined conditions is true.
l Condition Scope:Determines whether the conditions need to be true for all the pages of the document, or any one of
them.
l In the document (occurence):The task will return true if the condition set it true for any page of the doc-
ument.
l On each pages:The task will return true only if the condition set is true for all of the pages of the document.
l Invert condition:Inverts the result of the task.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l Capture Post Processing 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.
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 cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.