7.3

Process Logic Tasks
A process is like a flowchart. The data files captured by the input tasks become job files (see "Data File and Job File" (page
101)) that travel down the process. Many processes include multiple process logic tasks.
In the Process area, conditional branches appear with their associated condition, allowing you to understand the logic of the
whole process at a glance. When PlanetPress Suite Workflow Tools comes to a condition, it tests the condition and sends the
job file down one of the two branches based on the test result. So every time a job file travels down the process, it is either
routed down the True or False branch.
A Branch is effectively a doubling of your job file. As your job file goes down the process, when it encounters a branch it will
go in that branch, process all tasks up to the output, and return to the main trunk to continue processes. You can have
branches within branches, and all branches must have an output. For more information on branches, see "Branch" (page 153).
ALoop is a task that will cause anything after it to repeat a certain number of times. You can indicate a static number of loops
or dynamically determine the number via a variable or information from your job file, and store the iteration of the loop in a
job info. See "Loop" (page 155).
The Send to Process action and Go Sub Action are used to send the job file to another process or subprocess and, in the
case of the GoSub, to get information back from the subprocess. See "Send to Process" (page 157) and "Go Sub" (page 155).
Branch
By default, when you add a branch to a process, PlanetPress Suite Workflow Tools uses identical copies of the job file and job
file information for the both the main and secondary branches. You can change these settings as required once the branch has
been added.
Branch properties are as follows:
Backup Tab
l Backup job file: Select if you want PlanetPress Suite Workflow Tools to use identical copies of the job file for the
main and secondary branches. When this option is not selected, the file generated by the output task located at the end
of the secondary branch is used as the job file for the main branch. Note that if the secondary branch ends with a Delete
output task, the main branch will not receive any job file. If the secondary branch includes a Splitter action task, the
main branch will receive the last part of the job file (as split by the Splitter task). If the secondary branch ends with a
PlanetPress Fax or PlanetPress Image output task, the main branch will receive a PostScript file.
l Backup job information: Select if you want PlanetPress Suite Workflow Tools to use identical copies of the job file
information for the main and secondary branches. When this option is not selected, the job file information that reaches
the output task located at the end of the secondary branch is used for the main branch. Any modification performed on
the secondary branch thus has an impact on the main branch.
l Backup emulation: Select if you want PlanetPress Suite Workflow Tools to use the emulation selected when the job
file reaches the secondary branch for the main branch as well. When this option is not selected, the emulation selected
when the job file reaches the output task located at the end of the secondary branch is used for the main branch. If the
secondary branch includes a secondary input task or a Change Emulation action task, then the last emulation selected
in the secondary branch will be the one used for the main branch.
l Backup local variables: Select if you want PlanetPress Suite Workflow Tools to use identical copies of the local var-
iables for the main and secondary branches. When this option is not selected, the local variables that reaches the out-
put task located at the end of the secondary branch is used for the main branch. Any modification performed on the
secondary branch thus has an impact on the main branch.
©2010 Objectif Lune Inc - 153 -