8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
All the variables in PReS Workflow are considered strings, even if the information itself can be a number.
There are no other types of variables (such as arrays, floating point numerical values or Boolean) in PReS
Workflow.
Job Info Variables
Job Infos have two main uses. First, they contain information on any job file that comes out of the initial input
task or any secondary input tasks. The number of job infos as well as their definition can be seen in the
Other tab of any input task. Secondly, they are transmitted, unless otherwise configured, directly to any
PReS Connect document used within your process and can be directly accessed by that document, so they
can be used to transfer complementary information to your document that is not contained within your data
file.
Note
You can also access global and local variables from your document using the ExpandString()
function. For more information, please see the PReS Connect User Guide.
There are only 9 Job Infos available numbered from 1 to 9. They can be accessed directly anywhere that
accepts variable properties by using the number of the variable preceded by a percent sign (For example,
%2 or %9).
You can set the value of a job info within your process in two ways:
l Use the Set Job Info and Variable action task. See "Set Job Infos and Variables" on page 262.
l You can use Scripts. See the chapter "Using Scripts" on page 75.
Considerations on Job Infos:
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 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.