2020.2

Process logic tasks
A process is like a flowchart. The data files captured by the Input tasks become job files (see
"Job file" on page50) 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 Workflow 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" on the facing page is effectively a doubling of your job file (see "Job file" on
page50). 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135.
A "Loop" on page472 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.
The "Send to Process" on page476 and "Go Sub" on page471 tasks 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.
Note
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 NOT modify metadata in any way. Furthermore,
Page 464