8.5

Warning
Branches, loops and conditions do NOTmodify metadata in any way. Furthermore, even if a branch
does a backup of jobinfos and the data file, it does not back up the metadata. Keep this in mind when
designing a process.
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" below.
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" on page362.
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" on page368 and "Go Sub" on page360.
Branch
ABranch duplicates your job file along with accompanying information. Branches do not execute in parallel
- the branch is executed, and then the trunk (or the following branch)continues.
Properties
Backup Tab
l
Backup job file: Select if you want PlanetPress Workflow 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 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.