7.0

Table Of Contents
Related topics:
In-Stream Splitter Action Task Properties (Page 178)
Emulated Data Splitter Action Task Properties (Page 182)
XML Splitter Action Task Properties (Page 184)
Database Splitter Action Task Properties (Page 186)
In-Stream Splitter Action Task Properties (Page 178)
Add Document Action Properties (Page 192)
Change Emulation Action Task Properties (Page 195)
Create VDX Action Task Properties (Page 198)
Digital Imaging Action Task Properties (Page 201)
Digital Signature Action Task Properties (Page 205)
Download to Printer Action Task Properties (Page 207)
External Program Action Task Properties (Page 208)
Load External File Action Task Properties
Loop Action Task Properties
Open XSLT Action Task Properties (Page 210)
Database Action Task Properties (Page 161)
PrintForm Action Task Properties (Page 164)
PrintShop Mail Action Task Properties (Page 165)
Rename Action Task Property (Page 166)
Run Script Action Task Properties (Page 167)
Search and Replace Action Task Properties
Advanced Search and Replace Action Task Properties (Page 159)
Send Images to Printer Action Task Properties (Page 169)
Send to Folder Action Task Properties (Page 170)
Standard Filter Action Task Properties (Page 172)
Set Job Infos and Variables Action Task Properties (Page 171)
Translator Action Task Properties (Page 173)
Windows Print Converter Action Task Properties (Page 174)
10.1.26 Change Emulation Action Task Properties
Change Emulation action tasks are used to tell the tasks that follow them to use a different emulation to
format the data they receive. So these tasks do not perform any operation as such on the data, but rather
they modify the way subsequent tasks process the data they receive.
Change Emulation action tasks are typically used when a secondary input task brings new data that is not
structured like the initial data into the process. By default, every task included in a process uses the emulation
associated with the sample data file to structure the data before it processes it. Any task that must use a
different emulation must be preceded by a Change Emulation action task. All the tasks that follow on the
same branch will use the emulation chosen in the Change Emulation task.
New input brought into a process via a PlanetPress Database action task (see Database Action Task Properties
(Page 161)) does not require to be followed by a Change Emulation action task, even if the structure of the
new data is not the same as that of the sample data.
Change Emulation action task properties are as follows:
General tab
Add/remove characters: Enter the number of characters to add to, or remove from, the head of the data
stream, or use the spin buttons to increment or decrement the value. Positive values add characters; negative
values remove characters. This is useful when one or more characters of input data precede the start of the
first data page. Note that certain control characters can be problematic. For example, the NUL character
(hexadecimal 00) cannot be removed from the head of the data stream, and a backspace (hexadecimal 08)
can cause unpredictable behavior. The Hex Viewer can be useful in helping determine the control characters
that appear at the head of the data stream. Note that you cannot add characters in either a CSV or user-
Action Tasks - Detailed Directions
Objectif Lune Inc. © 2009 195