2018.1

Job Info variables
Job Infos contain information on any job file that comes out of the initial input task or any
secondary input tasks. There are only 9 Job Infos available numbered from 1 to 9. They can be
accessed directly anywhere where variable properties are accepted, by using the number of the
variable preceded by a percent sign, for example, %2 or %9.
Not all available Job Infos will actually be used by input tasks. The number of Job Infos as well
as their definition can be seen in the Other tab of any input task.
The value of a Job Info can also be set:
l Via the Set Job Info and Variable action task. See "Set Job Infos and Variables" on
page310.
l Via a Script task. See the chapter "Using Scripts" on page123.
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67, or local variables (see "Local variables" on page518).
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.
Page 512