2018.2

Table Of Contents
l "OL Connect tasks" on page502 can add information, such as record IDs, a record set ID
or a print job ID, to the Metadata. They put it under 'User defined information' on the Job,
Group or Document level.
l The "Barcode Scan" on page306 task can add information to the existing Metadata, and
creates it if there is none.
l The "Capture Fields Generator" on page452, "Capture Fields Processor" on page455,
"Get Capture Document" on page466 and "Find Capture Documents" on page462 tasks
generate their own Metadata.
l The "Lookup in Microsof Excel® Documents" on page416 enhances Metadata fields
with information from an Excel spreadsheet, but does not otherwise change its structure.
How Metadata affects the output
By default the data file is not affected when the Metadata are modified. There are however a
few situations in which Metadata will or may affect the output.
l When you print a PDF with a Windows Print Queue, the Metadata is inspected to
determine whether pages should print or not (see "Print using a Windows driver" on
page555 and ).
l The "Create PDF" on page317 task also takes the Metadata into account.
l In Connect, output is normally created from records in the Connect database, but options
in some "OL Connect tasks" on page502 make it possible to influence the output via the
Metadata.
l The "Execute Data Mapping" on page530 task and "Retrieve Items" on page541
task can output records in the Metadata.
l The "Create Print Content" on page523 and "Create Email Content" on page508
tasks have the option to update the records in the Connect database from the
Metadata.
Output issues caused by Metadata, and how to avoid them
A Branch, Loop (the "PDF Splitter" on page383, for instance, or the Loop task) and Condition
don't reset the Metadata. This can cause confusing issues if they are used in combination with
a task that takes the Metadata into account.
To avoid such issues, either regenerate your Metadata inside the (condition) branch or loop as
early as possible (see "Create Metadata" on page470), or use the "Metadata File
Management" on page476 to delete the active Metadata file and let the data file be taken into
account instead of the Metadata.
Page 81