7.4

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).
Actual Data and Sample Data
The actual data is the dynamic data captured by PlanetPress Suite Workflow Tools at runtime. The sample data file is a static
sampling of the runtime data.
In the PlanetPress Suite Workflow Tools Configuration program, you use sample data files to create and edit PlanetPress Suite
Workflow Tools configurations.
Job File Names and Output File Names
When an input task sends a new data file down a process, it gives it an internal file name referred to as the job file name (asso-
ciated with the %f variable). The new job file typically keeps the same name until the end of the process.
l If the job file comes to a branch in the process, the PlanetPress Suite Workflow Tools make a copy of the job file and
give the new file a new job file name.
l If the job file is processed by a splitter action task, the task typically creates a number of new files which are all given
new job file names.
Since these files are generated and managed by the PlanetPress Suite Workflow Tools, you should not actually pay too much
attention to their names.
Many output tasks, on the other hand, let you determine exactly how you want the files they generate to be named. In the
case of Send to Folder output tasks, for example, output files are saved under their job file names by default (using the var-
iable %f), but you may use a static (MyOutput.txt, for example) or variable name (%O_Invoices, for instance) of your
choosing.
Variables such as %o (original file name) bring up the issue of file overwriting. If the process receives two source files with the
same name, the second output file may overwrite the first one. This may be what you want, but otherwise you may consider
using another variable, such as in %u (unique 13-character string).
When choosing naming schemes for output files, consider the following:
l For the benefit of users who must identify files, be it in a folder or on a printer queue, consider using names that are as
meaningful and precise as possible.
l Some devices or applications may use file name extensions to know what to do with incoming files.
Since variable properties can be entered in the boxes where you specify the folder and file names, you can use variables, data
selections and static text. You could, for example, use the following: ClientID_@(1,1,1,1,14,KeepCase,Trim)_StatMonth_
%m.
One last consideration regarding output file names has to do with standard JPEG and TIFF files generated by PlanetPress
Image. When an output job contains multiple pages, multiple JPEG or TIFF files are generated (one image per file), each one
identified by a sequence number appended to its name (this is managed by your PlanetPress Suite Workflow Tool). A three
page job to be called Invoice, for example, will generate three JPEGs or TIFFs called Invoice0, Invoice1 and Invoice2. Note
that this does not apply to multiple TIFFs, which can include multiple images in a single file.
Finally, note that you can change the name of a previously named file using a Rename action task (see Rename).
Data in PlanetPress Suite Workflow Tools