2022.2

debug PlanetPress Workflow configurations (see "Debugging your PlanetPress Workflow process" on
page89).
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 (associated 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, PlanetPress Workflow makes a copy of the job file
and gives 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 PlanetPress Workflow, 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 variable %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 %u (unique 13-char-
acter 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 as 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 (see "About variables" on page238), data selections (see "Data selections" on the
facing page) 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 gen-
erated 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 Workflow). A three page job to be called Invoice, for example, will
Page 48