8.8

l Custom:Use the title in the input field as set by the user. The field is variable so the
title can be set on a per-document basis using data or metadata selections.
l Output Format group
l Continue process with optimized postscript(no metadata):The job file coming
out of the task will be a PostScript file that can be sent to any postscript printer or
saved locally.
l Continue process with PDF(with new metadata):The job file coming out of the
task will be a PDFwith accompanying metadata for that PDF(previous metadata is
lost).
l Override document pattern sequence:Check to override the pattern sequence as
entered in your PlanetPress Design document properties. Once checked, enter a new
pattern sequence in the Pattern Sequence box.
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777.
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.
Page 484