7.4

l Barcode_1_Value: Metadata field representing the value of the first barcode on the page.Note that thisfield (Bar-
code_1_Value) contains the same value as the first occurrence of BarcodeValue.
l BarcodeBase64_1_Value: Metadata fieldcontaining the value of the first barcode, encoded in Base64.
l Barcode_1_Type: Metadata fieldcontaining the type of the first barcode (ex. EAN13, UPCA …).
l Barcode_1_Orientation: Metadata fieldcontaining the orientation of the first barcode.
l Barcode_1_Top: Metadata fieldproviding the distance (in pixels)from the top of the page to the top of the first bar-
code.
l Barcode_1_Bottom: Metadata fieldproviding the distance (in pixels) from the top of the page to the bottom of the
first barcode.
l Barcode_1_Left: Metadata fieldproviding the distance (in pixels) from the left of the page to the left side part of the
first barcode.
l Barcode_1_Right: Metadata fieldproviding the distance (in pixels) from the left of the page to the right side part of
the first barcode.
Accessing Barcode Value From a Workflow Tool
One method is to use a VBScriptwith the Open Script task, using the Watch.ExpandString command with a metadata com-
mand as its input parameter, in between double quotes. For example, the following script line gives the value of the first Bar-
codeValue metadata field of the first datapage:
watch.expandstring("GetMeta(BarcodeValue[0],0,Job.Group[0].Document[0].Datapage[0])")
Another method is to use a Set Job Info and Variables task to copy a metadata field into a Workflow variable.
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.