7.6

l Condition:The condition or value the document needs to meet. The condition is variable dependent on
the chosen filter. It can be a drop-down of values, an alphanumerical or numerical value.
l Add button:Click to add a condition row to the grid.
l Remove button:Click to remove the currently selected condition from the grid. To select a row, simply click
on any of its 3 components.
l Condition Operator:Select either "All items are met"to force all conditions to be true for a document to be
included, or "At least one item is met"to include documents where a minimum of 1 condition is true.
l Create Advanced Data File:Click to retrieve additional information about each document in the result list. These
information include each field, the presence of ink on each of them, time stamps, etc.
The Advanced Data File option will generate a high number of queries into the Capture Database, and will be slower
than a regular data file by orders of magnitude. Do not use this option unless you are aware of the loss of per-
formance and actually need to access each field's properties individually!
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.
Get Capture Document
The Get Capture Document action task is used after the Capture Field Processor to retrieve all documents that have been
updated.
Input
A data file in PGCor PDFformat that is accompanied by valid Metadata. This metadata must contain Capture information and
is generally available after a Capture Fields Processor or Find Capture Documents task. However, it is also possible to directly
retrieve the required information from a specific Document ID. When a specific ID is used, the data file and metadata are com-
pletely ignored by this task's condition rules, and the database information is used instead.
Processing
One PDF, corresponding to the information present either in the metadata or specified in the task, is extracted from the Cap-
ture database.
When retrieving documents from the database, the PDFfrom which the document is obtained will remain in the database until
each document contained in it is retrieved from it. For example, if a 10-page PDFcontains 5 documents, the 10 pages remain
in that PDFuntil all 5 documents have received ink, been closed and retrieved from the database. This may mean space issues
if too many PDFfiles remain in your database.
Performance-wise, when this plugin retrieves a document from a 10,000 page PDF in the database, it will take more
time then if it retrieved it from a 100 page PDF.