8.7

engine). Note that you should not enter fixed values for the following parameters: the
XSLT stylesheet parameter, the source XML data file parameter or the output file
parameter. When you click the buttons below, the corresponding parameters are
automatically added at the current cursor position. These variables will be replaced by the
correct information at run-time.
l
XSLT file button: Click to add the {XSLTFILE} variable to the command prompt displayed
in the box above.
l
Data file button: Click to add the {DATAFILE} variable to the command prompt displayed
in the box above.
l
Output file(s) button: Click to add the {OUTPUTFILE} variable to the command prompt
displayed in the box above.
l
Browse button: Click this button and browse to select the XSLT engine you want the XML
splitter to use.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page731.
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 386