2018.2

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 NOT modify metadata in any way. Furthermore, even if a
branch does a backup of Job Info variables 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 (see "Job file" on page46). As your job file
goes down the process, when a branch is encountered, a copy of the job file will go in that
branch. In the branch, all tasks up to the Output task will be performed, before returning to the
main trunk to continue processes. You can have branches within branches, and all branches
must have an Output task. For more information on branches, see " About branches and
conditions" on page124 and "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 variable. See
"Loop" on page388.
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392 and "Go Sub" on page387.
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.
For more information about branching see " About branches and conditions" on page124.
Page 383