Common Issues - Bar Code Process - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential

Bar Code Process

Platform
OnBase
Product
Bar Code Process
Release
Foundation 23.1
License
Premier
Standard
Essential

Bar codes printed bi-tonally can be read without issue, but bar codes printed in color or grayscale are not always read correctly.

Bar Code Processing may have trouble reading bar codes that are printed in color or grayscale due to the compression of the image.

It is considered a best practice to always use bi-tonal bar code images with Bar Code Processing.

OnBase has difficulties attempting to read bar codes printed on a colored background.

Bar codes should be printed bi-tonally (i.e., black printing on a white background).

If a bar code must be printed on a colored background, then the scan queue being used to scan the documents should be configured to use a color dropout image process to remove the background color from the image document.

For more information on color dropout image processing, see the Document Imaging module reference guide or help files.

I am unable to perform Bar Code Processing at the time of scanning on a workstation registered for Desktop Document Imaging.

Bar Code Processing at the time of scanning must be performed on a scanning workstation registered with a Production Document Imaging license. Scanning workstations registered with a Desktop Document Imaging license are unable to perform Bar Code Processing at the time of scanning.

Bar Code Processing at the time of scanning can also be performed on a Disconnected Scanning workstation.

Batches are bypassing the Awaiting Bar Code Processing batch status queue after being scanned/swept and are being sent directly to the Awaiting Index batch status queue.

If batches are bypassing the Awaiting Bar Code Processing batch status queue and your scan queue is configured correctly, ensure that there are no System Document Types assigned to the scan queue. System Document Types will cause the batch to skip the Awaiting Bar Code Recognition batch status queue.

The Indexing Status window confirms that bar codes are being processed and that the correct values are being read, but no Keyword Values are being assigned to the documents or Keyword Values are being intermittently assigned to the documents.

As documents undergo bar code processing, the Indexing Status window displays the starting positions and values of all bar codes read on each document. These values are only assigned to a document's configured Keyword Types if the actual starting positions of the corresponding bar codes fall within the X-to- Delta X and Y-to- Delta Y ranges configured for the specified Keyword Types in the Bar Code Field Definition dialog box. When a processed bar code value is assigned to the configured Keyword Type for a document, the Indexing Status window displays a message in the following format:

Bar code: Keyword type: <configured Keyword Type name> - Value: <processed bar code value>

Once you have ensured that your configured ranges for the starting positions of your documents' bar codes are suitable, also ensure that the values represented by the bar codes are valid for the Keyword Types they are being assigned to (i.e., a value containing non-numeric alphanumeric characters is not being assigned to a numeric Keyword Type).

If a value represented by a bar code is invalid for a particular Keyword Type, that Keyword Value will be left blank.

I am having trouble recognizing values from self-configured bar code sheets.

When using Kofax hardware or software used to read bar code values, Kofax sporadically has an issue reading the %SELFCONFIG% string that identifies a self-configured bar code sheet.

To resolve this issue, generate self-configured bar code sheets using the string OBSELFCONFIG instead of %SELFCONFIG%.

After moving from Kofax to the Hyland Bar Code Recognition software, my OnBase solution is no longer identifying values from some bar codes at the time of scanning.

This issue is due to the fact that Kofax and the Hyland Bar Code Recognition software process images differently and are determining the location of the bar code at slightly different coordinates.

To resolve this issue, you must change the Bar Code Process to modify the area of document that is searched for each bar code. The simplest solution is to modify the Delta X and Y values for each bar code that composes the Bar Code Process to increase the area of the document that the Hyland Bar Code Recognition software will search when looking for the bar code.

My batch bar code process produces inconsistent results. Sometimes it works correctly, sometimes it assigns the wrong Keyword Values to documents, and other times it does not index documents at all.

If you indexing documents using separate bar code sheets are sweeping or scanning batches from disk, be aware of the file names used by the documents and the bar code sheets to ensure that the documents are swept/scanned from disk in the proper order.

By default, OnBase sweeps/scans from disk the file with the shortest file name into the system first, and then proceeds alphabetically/numerically.

For example: if the folder being swept/scanned from disk contains files named 1.tif, 2.tif, and 10.tif, the document with the shortest file name is scanned from disk first (1.tif), followed by the files that are displayed next alphabetically or numerically (2.tif and then 10.tif).

Note:

Your solution may be configured to scan files in a different order. For more information, contact your solution provider.

If you are not cognizant of your file names, documents may be indexed incorrectly (i.e., the wrong bar code sheet may be imported before a document) or they may not be indexed at all (i.e., the document is imported before the bar code sheet so no indexing values are applied).

I have documents (e.g., OLE documents, HTML documents) containing bar codes that I would like to convert to images and process via the Bar Code Recognition Server. I would like to retain the original documents as a rendition of the new image documents. When the new image documents undergo batch bar code processing, some of them share Keyword Values and are merged into a single document. When this occurs, the non-image rendition is saved for only the existing document (archived in OnBase or previously indexed in the current batch), not the document that is being appended to it.

Multiple renditions of non-image documents cannot be merged into a single document.

When the image documents are merged into a single document due to matching bar code values, the target document (i.e., the pre-existing document already archived in OnBase or previously scanned in the current batch that the newly-scanned/swept images are being appended to) becomes the “parent” document and the documents that are appended to it as the subsequent pages cease to exist as independent documents. Their renditions, Keyword Values, and histories are lost.

Only the information with the “parent” document is retained.

I am using Kofax to process bar codes, and the bar code format's Search Direction settings are being ignored.

This issue may occur when Kofax attempts to process Code 39 (3 of 9) bar codes.

By default, OnBase attempts to process all Code 39 bar codes as Enhanced Code 39 bar codes, regardless of if you are using Kofax hardware/software or the Hyland Bar Code Recognition software.

If Kofax attempts to process bar codes as Enhanced Code 39 bar codes and the bar code format's Search Direction setting is set to 0, then Kofax will search in all directions to read the bar code (i.e., the bar code format's Search Direction settings are ignored). This is the Kofax hardware/software's expected behavior.

To force Kofax hardware/software to respect the bar code format's Search Direction setting, you must configure Kofax to process bar codes as standard Code 39 bar codes, not Extended Code 39 bar codes. For more information, see Processing Code 39 Bar Codes as Standard Code 39 Bar Codes.

When scanning documents in duplex and performing batch bar code processing via the Bar Code Recognition Server, the scan queue's Discard Back of Patch Code Page option (located on the Capture tab of the Assign Process Options for <Scan Queue Name> dialog box) and the bar code format's Discard Back of Pages with Keyword Bar Codes and Discard Back of Document Type Separator Page options (on the bar code format's Process Type dialog box) are not respected.

When scanning in duplex, front pages and back pages are identified only at the time of scanning. Once a batch has been routed to the Awaiting Bar Code Processing batch status queue, OnBase has no knowledge of the pages in the batch that were identified as fronts and the pages that were identified as backs.

Because of this, the three Discard Back of... bar code/patch code processing options are not respected for batch bar code processing via a processing workstation licensed for the Bar Code Recognition Server.