7.1

Process Logic Tasks
Process Logic tasks include conditions, branches and loops. They can be used to control the flow of the data within your proc-
ess either consistently or depending on certain information obtained from multiple sources.
Conditions are used to create a path in your process that will either execute one branch or continue down the main trunk.
The result can depend on data within your job file, external data, variables or even the result of an external script. Acondition
will never result in both branches being executed, and any tasks or outputs in the ignored branch will also be ignored. See
"Conditions" (page 128).
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 Properties"
(page 127).
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 Action Task Properties" (page 142).
ASplitter separates your data into multiple chunks that are used as individual, smaller job files. Asplitter is similar to a loop
in the sense that it will cause anything after it to repeat a certain number of times, however in this case it is the data itself that
determines the number of loops. See "Splitters" (page 132).
The Send to Process action and GoSub 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 Task Properties" (page 142) and
"GoSub Action Task Properties" (page 142).
Branch Properties
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
©2010 Objectif Lune Inc - 127 -