7.0

Table Of Contents
Data can also be changed using the PlanetPress Suite Workflow Tools. You can use an Action task to perform
search and replace operations on the data, to change the data emulation, or the data character set.
When data is pulled in via an input task it is stored in an internal data file, called a job file, that is handed
down from task to task. Data can originate from a variety of sources and come in a variety of formats. For
example input sources might be UNIX systems dispatching print jobs or various types of databases which are
queried. Examples of formats are plain ASCII files, CSV files, and database files through any ODBC compatible
data source.
Note that null characters present in the data may not be displayed properly when using the PlanetPress Suite
Workflow Tools Configuration program, and that they may also be printed differently by different printers. To
ensure consistency, you should consider filtering out such characters.
You add data selections to tasks using the same Data Selector and emulation types as in PlanetPress Design
(with the exception of User Defined emulations, which are not available in the PlanetPress Suite Workflow
Tools). A scaled-down version of the Data Selector, called the File Viewer, can also be used when you don’t
need an emulation.
You can also change the emulation during the course of the process by adding a Change Emulation action
task. You might do this, for example, if you are retrieving data files from multiple sources in a single
PlanetPress Suite process. For example a print job sent from a UNIX system may require Line printer
emulation, while a Comma Separated Value file retrieved via FTP may require CSV emulation.
About Binary Data
PlanetPress Suite Workflow Tools are designed to process text files (files that contain bytes of value 4, 8 to
13, 32 to 126 and 128 to 255). Results are not guaranteed when tasks are used to process binary files.
Data and Emulation in PlanetPress Design and PlanetPress Suite Workflow Tools
Emulations are like filters that can be used to read the data. When you create a document in PlanetPress
Design, you choose a sample data file and specify the emulation to use for the chosen data. The emulation
setting you choose will typically always be associated with that document. If you choose a CSV (comma
separated values) file and specify the corresponding emulation, for instance, commas encountered in the data
will typically be considered as value separators.
Every PlanetPress Design document is associated with an emulation that allows it to read the data correctly
and thus to perform the merging process successfully. When a PlanetPress Design document created for data
formatted using the line printer emulation receives data files formatted using the CSV emulation, for instance,
the results are less than perfect. So whatever processing takes place in the PlanetPress Suite Workflow Tools,
the data always remains in its original format.
Change Emulation Tasks
Why would you want to add a Change Emulation action task in a PlanetPress Suite process? You may need to
do this, for instance, if your process includes a secondary input task.
When you choose a sample data file and an emulation in your PlanetPress Suite Workflow Tool Configuration
program, you are in fact doing two related but very different things:
You are loading data that will be used as test data to help you create your process in your PlanetPress
Suite Workflow Tool Configuration program.
You are telling the tasks in your PlanetPress Suite process how the data included in the files they will
receive is structured.
So if you add a secondary input task that pulls in data that is not structured like the data pulled in by the
initial input task, you must add a Change Emulation action task to tell the tasks that follow it how the new
data is structured.
Understanding PlanetPress Suite Workflow Tools - Key Concepts
Objectif Lune Inc. © 2009 23