7.1

l Use alternate XSLT engine group: Select this option to enable the box and the buttons included in this group.
l Path and parameters for the alternate engine: Enter your XSLT engine’s absolute path (use quotes for non
DOS 8.3 compliant paths) followed by its required operators and parameters (you must know exactly which operators
and parameters your XSLT engine requires and in which order they must appear in the command prompt used to
launch the 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 cor-
responding parameters are automatically added at the current cursor position. These variables will be replaced by the
correct information at runtime.
l XSLT file: Click to add the {XSLTFILE} variable to the command prompt displayed in the box above.
l Data file: Click to add the {DATAFILE} variable to the command prompt displayed in the box above.
l Output file(s): 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 on "Task Properties Dialog" (page 51).
Generic Splitter Action Task Properties
In previous versions of PlanetPress Suite Workflow Tools, only this splitter was available. Although it is still available for back-
ward compatibility reasons, we strongly suggest that you create new splitter action tasks using the new splitters listed below.
To add tremendous leap in performance to your existing processes, we even suggest replacing existing generic splitter action
tasks with specific splitter action tasks.
l "In-Stream Splitter Action Task Properties" (page 136)
l "Emulated Data Splitter Action Task Properties" (page 134)
l "XML Splitter Action Task Properties" (page 138)
l "PDF Splitter Action Task Properties" (page 136)
l "Database Splitter Action Task Properties" (page 133)
Generic Splitter action task properties are as follows:
General Tab
l Split data file on: Use this box to choose the item on which top split the file. The options available depend on
whether or not the Use emulation box is checked (see below).
l Use emulation: Check to emulate the data before splitting the file. This lets you split the file on a word, a word
change, a page number, a database field value or a database field change. When this option is not checked, you can
only split the file on a form feed, a specific number of lines, or a chain of characters. See below for detailed information
on any of these splitting methods.
l A word :If you choose “A word” in the Split data file on list box (the Use emulation option must be selected), the fol-
lowing boxes are displayed.
l Word: Enter the string of characters to search for as the splitting criteria. In this variable property box, you may enter
static characters, variables, job information elements or any combination of these.
l Get: Click to get a static string of characters from the sample data file. If you use this button, the coordinates of the
data you will select will be added to the Word is between lines and Word is between columns groups below.
l Word is between lines group
l From and To: Enter a vertical search region defined as starting from a given line and ending at a given line. If
you enter 1 in the From box and 1 in the To box, the Generic Splitter will search for the string of characters
entered above only in the first line of every page. If you enter 1 in the From box and 10 in the To box, the
Generic Splitter will search in the ten first lines of every page. Note that the actual search region is a com-
bination of the vertical and horizontal search regions.
©2010 Objectif Lune Inc - 139 -