8.5

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 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.
Properties
General tab
l
File name mask: Enter one file name mask or multiple masks separated by a semicolon (;). See
Masks. The condition 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 in the" Task Properties Dialog" on page666.
By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and
the task just under it (not within a branch)will be given control of the job file without any modification. Any
initial input task that generates an error will stop the process from running as a whole, and output tasks will
not generate output. The On Error tab can be used to overwrite the default behaviors.