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.

• If the job file comes to a branch in the process, OL Connect Workflow makes a copy of the job file and gives the new file a new job file name.
• 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 OL Connect 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-character string).

When choosing naming schemes for output files, consider the following:

• 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.
• 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), data selections (see 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 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 OL Connect Workflow). 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.

Note: You can change the name of a previously named file using a Rename action task (see Rename).