8.7

Note
Null characters present in the data may not be displayed properly when using PReS
Workflow Configuration program, and that they may also be printed differently by different
printers. To ensure consistency, you should consider filtering out such characters.
Data File and Job File
Whichever source it may come from, a serial port, an e-mail message, or an LPR request, for
instance, and whatever its format, data entering a PReS Workflow process via an input task is
always referred to as a data file. Job file is a more general term, that can refer to data files as
well as other types of files traveling through a process. Image files, for example, can be passed
from task to task in order to be downloaded to a printer. So files traveling within a process are
mostly referred to as job files.
By default, job file names are generated using the %f variable. You may change the wayPReS
Workflow names job files by using any combination of static characters, variables and Job info
variables. You could for instance enter Process_%w_Job_%f in the File name box to add the
process name in the name generated by the PReS Workflow Tools.
A single job file can be the source of multiple job files. This is the case, for example, when a
process includes multiple branches, as each branch is given a duplicate copy of the job file.
This is also the case when a job file is split into multiple smaller files by a Splitter action task,
for instance (See Data Splitters).
It is important to note that job files may be used as a helpful debugging resource (See
"Debugging and Error Handling" on page55).
Actual Data and Sample Data
The actual data is the dynamic data captured by PReS Workflow at run-time. The sample data
file is a static sampling of the run-time data.
In the PReS Workflow Configuration program, you use sample data files to create and edit
PReS Workflow configurations.
Page 24