8.4

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.
Properties
Backup Tab
l Backup job file: Select if you want PReS Workflow to use identical copies of the job file for the main
and secondary branches. When this option is not selected, the file generated by the output task
located at the end of the secondary branch is used as the job file for the main branch. Note that if the
secondary branch ends with a Delete output task, the main branch will not receive any job file. If the
secondary branch includes a splitter task, the main branch will receive the last part of the job file (as
split by the splitter task). If the secondary branch ends with a PReS Fax or PReS Image output task,
the main branch will receive a PostScript file.
l Backup job information: Select if you want PReS Workflow to use identical copies of the job file
information for the main and secondary branches. When this option is not selected, the job file
information that reaches the output 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.
l Backup emulation: Select if you want PReS Workflow to use the emulation selected when the job file
reaches the secondary branch for the main branch as well. When this option is not selected, the
emulation selected when the job file reaches the output task 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 reaches the output 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" on page 584.