7.1

secondary branch includes a secondary input task or a Change Emulation action task, then the last emulation selected
in the secondary branch will be the one used for the main branch.
l Backup local variables: Select if you want PlanetPress Suite Workflow Tools to use identical copies of the local var-
iables for the main and secondary branches. When this option is not selected, the local variables that reaches the out-
put 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.
In case of the failure of a Branch task (the branch itself, not the other tasks contained within), by default the process will
ignore the branch and simply go down the main trunk. You can overwrite this in the On Error tab.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on "Task Properties Dialog" (page 51).
Comment Properties
Comments can be used to clarify your process either for yourself or others, to explain branches and scripts, or add information
for anyone editing the configuration in the future.
Comments do not open, modify or otherwise process the job file in any way, and are simply ignored at runtime. They do not
have an "On Error"tab because of this, since they cannot generate an error in any situation.
Comments have a single property in the General tab, which is the box where you enter the comment itself. This box does
not process variables (it is not a "variable property"), since that would be of no use at runtime.
Conditions
A process is like a flowchart. The data files captured by the input tasks become job files (see "Data File and Job File" (page
89)) that travel down the process. Many processes include multiple branches and conditions.
In the Process area, conditional branches appear with their associated condition, allowing you to understand the logic of the
whole process at a glance.
l When PlanetPress Suite Workflow Tools arrives at a branch, it duplicates the job file so as to send a copy down each
branch.
l When PlanetPress Suite Workflow Tools 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.
You can add five types of conditions to your PlanetPress Suite Workflow Tools processes:
l The name of the job file:see "File Name Condition Properties" (page 128).
l The size of the job file:see "File Size Condition Properties" (page 129).
l The state of a printer or other SNMP compliant device:see "SNMP Condition Properties" (page 129).
l The comparison between two pieces of text:see "Text Condition Properties" (page 130).
l The current time:see "Time of Day Condition" (page 132).
l An advanced scripted condition using a Run Script Condition. See the "Run Script Action Task Properties" (page 122).
File Name Condition Properties
File Name conditions test the original name of the job file traveling down the process branch, or in other words, the name of
the file received by the last input task appearing above the condition.
File Name Condition properties are as follows:
General tab
©2010 Objectif Lune Inc - 128 -