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:

  • Via the Set Job Info and Variable action task. See Set Job Infos and Variables.
  • Via a Script task. See the chapter Using Scripts.

    • Note: 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.

    Job infos are limited in quantity and are slowly being deprecated when transferring data to your documents and processes. You should probably consider using Metadata, or local variables (see Local variables).

    Tip: Since version 2022.1, information can be passed from a process to a subprocess by setting the value of runtime parameters in the Go Sub task. Job Infos are no longer needed for this.

Using Job Infos in a Connect template

Workflow variables can be passed to an OL Connect template, data mapping configuration, or Job Creation Preset by setting the value of runtime parameters in the All In One, Create Preview PDF, Create Email Content, Create Job, Create Print Content, or Create Web Content task.

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.

Tip: You can also access global and local variables from your document using the ExpandString() function. For more information, please see the PlanetPress Design User Guide.