7.5

Table Of Contents
Limitations
l Some barcodes created with PlanetPress Suite 5 could not be read by the Barcode Scan task, so please use PlanetPress
Suite version 6 or 7 to create barcoded documents.
l When using a secondary input, a known issue of the Workflow Tool can cause some unexpected behavior, like having
the same metadata file reused instead of a new one being created for each data file captured. To work around this
issue, simply add a Rename Action taskto set a unique file name (Ex. %u) to each new file before the Barcode Scan
task, after each secondary input.
Change Emulation
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 ini-
tial 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 Emu-
lation action task. All the tasks that follow on the same branch will use the emulation chosen in the Change Emulation task.
Input
Any data file.
Processing
The emulation for the following tasks is changed to the selected emulation.
Output
The original data file, metadata and job infos are not modified. Only the emulation is changed.
General Tab
l The options of this task are basically the same as the Data Selector in PlanetPress Design. Please refer to the Plan-
etPress Design User Guide for information on how to use the Data Selector.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l Capture Web Manager Workflow
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors