8.6

l Fail if document doesn't contain at least one capture field:If the static or dynamic
document that tries to pass through this task does not contain any capture fields, an error
will be generated.
l Simulate pattern area on final document:When retrieving the document from the
database with the Get Capture Document, each Capture Field is simulated using a grey
box. This box is not a pattern and cannot be used with the Anoto Digital Pen, however
this option can be used to keep the same overall design of your document.
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 in the" Task Properties Dialog"
on page723.
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.
l Send to Process: Check this option to send the job file to an error management process.
l
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.
l Action:In the initial input tasks, this group is disabled and defaults to Stop Process. In
all other tasks where the On Error tab is present, the following options are available:
l Default:By default, the task is ignored as if it did not exist and the error is logged
before continuing the branch or process; the job file is passed on to the next task in
the process. When an error occurs in a loop (or in a plugin that acts like a loop), the
loop may log the error, terminate the current iteration and proceed with the next
iteration.
Page 451