2018.2

Design document, 'User defined information' (sometimes created by regular tasks) and in some
cases page properties and page counts.
Some of the Action and Output tasks produce, alter, or use the Metadata. In addition to that,
PlanetPress Workflow provides a whole series of plugins to create and edit Metadata during a
Workflow process (see "Metadata Tasks" on page462). The things that you have to know in
order to use the Metadata tasks effectively are set out in another topic: Working with Metadata.
Note
Applications or plugins created in PlanetPress Suite 6 and using Metadata will need to
be updated for use in version 2018.2. No backward compatibility mode is available.
Warning
When a user-defined emulation (created in PlanetPress Design) is used with Metadata,
results and behavior are unknown and unsupported. For instance, refreshing the
Metadata file may cause the document to crash and/or corrupt. For this reason, it is
strongly advised to create backup copies of your documents beforehand.
Metadata structure
The hierarchical structure of the Metadata is composed of a number of basic levels for adding
information to a job. These levels are, from top to bottom:
l
Job: A file that contains one or more groups.
l
Group: A logical and ordered group of documents (ex: all invoices for a specific customer
number; all documents going to the same address, etc.).
l
Document: A group of one or more ordered data pages intended to the same recipient
from the same source (ex: invoice).
l
Data page: One atomic unit of content that produces zero, one or more pages.
l
Page: One side of a physical paper sheet.
When Metadata is produced for a given job, a hierarchical (i.e. tree-like) structure is created,
composed of the above elements in the following order: Job > Group(s) > Document(s) >
Datapage(s) > Page(s). For example:
Page 70