2021.2

Note
l While the initial Job Infos are created by the input task, they can be overwritten by
the Set Job Info and Variables Action task, by a Script, or by any secondary input
task in the process. Whenever you use a job info in your process, make sure it
contains the value that you want, and not one that has been overwritten by another
task.
l Job infos are limited in quantity and are slowly being deprecated when transferring
data to your documents. You should probably consider using "Metadata" on
page75, or local variables (see "Local variables" on page723).
Using Job Infos in a Connect template
Workflow variables can be passed to a Connect template via a data mapping configuration.
Data mapping configurations are created with the DataMapper module (inside Connect
Designer). They contain a data model and instructions on how to extract data from a job file and
are used by the All in One task and the Execute Data Mapping task.
Job Infos are passed to the task so the trick is to transfer the value of the Job Info to a field in the
data model. To do that, simply add a property-based field to the Data Model and select a Job
Info from the list of properties; see Adding a property-based field.
Note that Job Infos don't change whilst the task executes. Consequently, the value of the field
that contains the Job Info will be the same in each of the records in the resulting record set.
Using Job Infos in a PlanetPress Design document
Job Infos are transmitted, unless otherwise configured, directly to any PlanetPress Design
document used within a process and can be directly accessed by that document, so they can
be used to transfer complementary information to a document that is not contained within the
data file.
Job Infos sent to the document are global to that document, meaning the values do not change
between data files. This means that if your data file contains multiple data pages for different
clients, your Job Infos cannot be used to send information to the document.
Page 717