7.4

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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Comment
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.
File Name Condition
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
l File name mask: Enter one filename mask or multiple masks separated by a semicolon (;). See Masks. The con-
dition will be tested True only in the case of an exact match, so consider using wildcard characters.
l Invert condition result: Select to toggle the result of the condition (true becomes false and vice versa).
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.