8.4

Another method is to use a Set Job Infos and Variables task to copy a metadata field into a Workflow
variable.
Limitations
l
Some barcodes created with PlanetPress 5 could not be read by the Barcode Scan task, so please
use PlanetPress 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 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.
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