2022.2

But when opened with PlanetPress Design or a PlanetPress Workflow using the ASCII emulation, the
data in the generated file would look exactly like the data in the original. The same would hold true for
the Channel Skip emulation.
Note the following details about emulations and their options:
l
With most emulations, if a file is split on a form feed, the form feed will not be appended to the out-
put file.
l
With the ASCII emulation, tabs within the input data file are replaced by spaces (the number of
spaces is determined within the configuration of the emulation).
l
With the ASCII emulation, if the Remove HP PCL Escapes option is selected, the data coming
out of the splitter will have no escape sequences.
l
The Goto column option of Channel Skip emulation is not supported.
Database Splitter
The Database Splitter is used to split database files into multiple data files that are passed to sub-
sequent tasks in the process.
Input
Database data (see "Database emulation" on page59).
Processing
The file is separated into multiple chunks according to the rules set in the task's properties.
Output
Multiple data files, sent one after the other to the rest of the tasks in the process. Metadata, job infos
and user variables are not modified by this task.
Task properties
General Tab
l
Split group: Use this group to indicate how you want the file to be split.
l
Field value change: Select if you want the file to be split based on changes in the values of a
selected database field (the value in the ClientID field changes, for example).
l
Field value condition: Select if you want the file to be split based on a condition set for the val-
ues of a selected database field (the value in the Order field equals 1, for example).
l
Field count: Select if you want the file to be split whenever a given number of pages or data
pages has been reached.
Page 408