2020.1

Table Of Contents
located at the end of the secondary branch is used for the main branch. If the 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 PReS Workflow to use identical copies of the
local variables for the main and secondary branches. When this option is not selected, the
local variables that reach the output task located at the end of the secondary branch are
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.
Miscellaneous Tab
The Miscellaneous tab is common to all tasks.
Check the option Use as step description to display the text next to the icon of the plugin in
the Process area.
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 run-time. 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 run-time.
File Count
File Count tasks check if a target folder contains a specified number of files. They can be used
as Condition task or as Input task.
When used as Input task, the task triggers the process to run only when the condition is true. As
long as the condition is false, it does nothing (except log any errors).
Page 474