8.8

saved).
l Script running from:Choose if the script should be run from the editor text box, or from
an external script file.
l Script filename and path:Either enter the full path of the XLSTScript, or click the
Browse button to navigate to the file. This option is only available if you choose external
script file in the Script running from option.
Warning
With the Run Script action, the OnErrortab is accessible by right-clicking on the action
in your process and clicking Advanced Properties.
The On Error tab will be triggered if your script has an execution error (such as syntax
error, etc) as well as when raising an error from within your script.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page777.
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.
l Send to Process: Check this option to send the job file to an error management process.
l
Error Process drop-down:Enabled only when the Send to Process option is checked.
Lists any process of which the initial input task is the Input Error Bin task.
l Action:In the initial input tasks, this group is disabled and defaults to Stop Process. In
all other tasks where the On Error tab is present, the following options are available:
l Default:By default, the task is ignored as if it did not exist and the error is logged
before continuing the branch or process; the job file is passed on to the next task in
the process. When an error occurs in a loop (or in a plugin that acts like a loop), the
loop may log the error, terminate the current iteration and proceed with the next
iteration.
Page 339