Installation guide

Zetadocs for NAV Installation Guide
This edition 5
th
December 2012 © Copyright Equisys plc 2012 All trademarks acknowledged All rights
reserved
Page 70
12. Enabling Barcode Support
Zetadocs supports the addition of barcodes to reports printed from NAV using a barcode font to print
unique information about an NAV object. This places a barcode into the report output, which can be used in
a number of manners. For example, with documents like invoices or sign off sheets which are distributed
from NAV before being signed or filled in and returned. In these cases when the document is added back
into the system document queue via scanning or email etc, it is captured back into the system and OCR’d.
This process detects the barcode and decodes the information contained within it. It is then used to link the
returned document to the original document in the archive. This enables users to track documents through
a variety of business processes.
Barcode Formats
Zetadocs for NAV supports Code 128 format barcodes only, however the OCR software has the capacity to
read and process those listed below. We recommend a minimum of Font-size 32 and a scanner resolution
dpi of 300 or greater. It should also be noted that some barcode formats only support upper case letters,
such as Code 39, if using such a barcode format please ensure you only use supported characters in your
barcodes.
Numeric-only barcodes
 EAN-13 (European Article Numbering, an international retail product code)
 EAN-8 (compressed version of EAN code for use on small products)
 UPC-A (Universal Product Code seen on almost all retail products in the USA and Canada)
 UPC-E (compressed version of UPC code for use on small products)
 Code 11 (used primarily for labelling telecommunications equipment)
 Interleaved 2 of 5 (compact numeric code, widely used in industry, air cargo, other applications)
 Industrial 2 of 5 (older code not in common use)
 Standard 2 of 5 (older code not in common use)
 Codabar (older code often used in library systems, sometimes in blood banks)
 Plessey (older code commonly used for retail shelf marking)
 MSI (variation of the Plessey code commonly used in USA)
 PostNet (used by U.S. Postal Service for automated mail sorting)
Alphanumeric barcodes
 Code 39 (de facto standard for Government, Manufacturing, BarCode Industry, Education, and
Business applications, in use world-wide)
 Code 93 (compact code similar to Code 39)
 Code 128 (very capable code, excellent density, high reliability; in very wide use world-wide)
 LOGMARS (same as Code 39, this is the U.S. Government specification)
Barcode Options
 The Zetadocs server searches for barcode information when processing graphics and PDF image
files. Any barcodes which are included in the file are saved alongside the document, and can be
used by custom processing functions to identify the document and automate its processing.
 A typical usage is to encode the NAV document number directly – eg adding the shipping note
number as a barcode. However for more complex requirements a separate ID could be stored
instead – eg storing a lookup key into a custom table within NAV which is used to store custom
information about the document. Barcode information is passed transparently to the custom code
when processing for maximum flexibility.
 Zetadocs for NAV is supplied with a standard barcode font. When used with this font, the barcode
recognition supports the following features:
o Encoding of variable length data strings, including letters A-Z (from ANSI standard Western
European character set), digits 0-9, plus a selection of punctuation characters.
o Barcode including text (user readable) version for manual checking or processing.
o Protection against misreading, using automatically generated checksum data.
o Support for documents scanned upside down.
o Most other common barcode formats can also be supported. Please contact Equisys for
further details if there is a requirement to use a specific barcode format.
o Barcode processing requires the OCR add-on module.