8.6

Table Of Contents
Technical
Branches, Loops and other process logic tasks do not generally modify the job file,
though some may change system variables. The only exception is the Run Script action,
which can be a condition that also modifies the data.
Warning
Branches, loops and conditions do NOTmodify 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.
ALoop 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
page385.
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391 and "Go Sub" on page383.
Branch
ABranch 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.
Page 375