8.7

l
Barcode_1_Orientation: Metadata field containing the orientation of the first barcode.
l
Barcode_1_Top: Metadata field providing the distance (in pixels)from the top of the
page to the top of the first barcode.
l
Barcode_1_Bottom: Metadata field providing the distance (in pixels) from the top of the
page to the bottom of the first barcode.
l
Barcode_1_Left: Metadata field providing the distance (in pixels) from the left of the page
to the left side part of the first barcode.
l
Barcode_1_Right: Metadata field providing 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 command as its input parameter, in between double quotes. For
example, the following script line gives the value of the first BarcodeValue 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 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.
Page 282