Barcodes

About Barcodes

A barcode is a machine-readable representation of data that can be included on documents for identification or automation needs (such as for imaging systems). Expere EZ Config Packages and Packets provides the ability to set barcode-related properties and define variable parameters within a barcode pattern. This barcode pattern may include document identifiers or static text used to provide a consistent and standard label on documents generated by the system within a single transaction.
Note: A barcode must contain a Barcode Pattern. The package will fail to generate if the barcode does not include a barcode pattern.

The properties for barcodes can be defined for each package. Within that package, the barcode properties applies to all documents in all packets.

How it Works

When processing Expere Document Services requests using a package defined within Expere EZ Config Packages and Packets, the barcode properties are included for all documents in the packets defined for the package. The request processing includes resolving the barcode pattern variables by replacing the variables with data values used for the final barcode label rendered on the documents.

The Barcode Card

The barcode card is used to contain information pertaining to barcodes for the package. If a barcode exists, its properties display within the card. If no barcode exists, use the +Add Barcode field within the card to begin creating a barcode.

Note: If the barcode value is too long to display within the card, it appears with an ellipses (…) character. Hover over the barcode value to display the entire pattern text.

Barcode Setup

  1. Click Add Barcode in the Barcode card to open the Barcode Setup popup window.
  2. Select which type of barcode to use. Available options include:
    • Barcode Inter 25. Also referred to as 2 of 5.
    • Barcode 39. Also referred to as 3 of 9 or 3.9. Code 39 uses 43 characters, including uppercase letters (A through Z), numeric digits (0 through 9), and a number of special characters (-, ., $, /, +, %, and space).
      Note: When considering the barcode pattern syntax, note some barcode patterns support limited character sets. For example, "3of9" (also: "39") supports a subset of special characters specified above, which does not include some special characters (i.e. underscore ('_') ).
      • Code 39 Extended - Code 39 Extended is an extended version of Code 39 that supports the ASCII character set. So with Code 39 Extended you can also code the 26 lower letters (a-z) and the special characters you have on your keyboard.
    • Barcode 2D. This option produces a barcode based on the PDF 417 definition.
    • Barcode 128. Barcode 128 is used for alphanumeric or numeric-only barcodes and uses all 128 ASCII characters.
    • BarcodeQR. BarcodeQR (quick response) is a type of 2D matrix barcode. The QR barcode is approximately .5 x .5 inches in size when generated on documents. Depending on the barcode alignment, the central scanning point is equidistant from the surrounding document margins regardless of the barcode size.
    Note: The amount of data that a barcode can hold varies between the symblogies. 1D barcode symbologies, such as Code 39 or Code 128 will hold much less data than 2D barcode symbology. When selecting the barcode type, be aware of the components you intend to include within the pattern to determine if the amount of data will require a 1D or 2D symbology. Refer to Barcode Details: Defining the Barcode Pattern for additional details.
  3. Designate a justification setting for the barcode within the documents: Left, Center, or Right.
  4. Then, specify whether to use the barcode on a cover page and also whether to use the barcode on the first page only, if desired. (Printing barcodes on the cover page applies to documents that do not have sufficient space to include the barcode on the document directly.) If the First Page Only option is not selected, the generated barcode displays on all pages of the document (for those documents that support barcodes).
  5. Specify a barcode pattern. The pattern can include the following elements:Refer to Barcode Details: Defining the Barcode Pattern for additional details on working with barcode patterns.
    Note: The barcode pattern field is scrollable to help make the contents more easily viewed. Carriage returns may be used for readability; carriage returns are not honored when Expere processing resolves the barcode data.
  6. Click Add.
Note: Only one barcode per package is allowed.
Note: If any barcode property is defined and a packet exists, the system assumes barcodes are intended. Validate all options are defined as necessary, particularly the barcode pattern. Failing to enter a pattern will cause errors when processing an Expere Document Service request.

Editing or Removing a Barcode

To edit a barcode:
  1. Click Edit Barcode.
  2. On the Barcode Setup window, edit the barcode properties you wish to change.
  3. Click Add.
To remove a barcode:
  1. Click Edit Barcode.
  2. On the Barcode Setup window, click Remove Barcode.
  3. Click Add.

Additional Notes

  • Expere EZ Config Barcodes use Expere’s Ancillary Output logic for rendering the barcode. If both the Knowledge Base Content is authored to include transactional barcode elements (typically in the tagline) with corresponding transaction data, and an Expere EZ Config Package (with a barcode defined) is used for document generation, Expere processing will honor the Expere EZ Config barcode. If both an Expere EZConfig barcode is defined and the Expere Document Service request includes barcode ancillary output options, the request ancillary output barcode specifications will be honored.
  • Documents assigned to a package that are not associated with a packet will still generate (provided the document passes autoselection rules) and are assigned to a separate packet named "Default" during processing. Documents not assigned to any packet in Expere EZ Config (assigned to "Default" packet) will not generate an Expere EZ Config Barcode. Transactional barcodes authored in Knowledge Base Content will generate for documents in the "Default" packet, provided the elements were included in the Transaction Data.
  • Barcodes are applied only to those documents assigned to a packet(s). Barcodes are resolved per each document within the packet.