Optimizing barcode recognition with IBM Datacap Taskmaster Capture

Optimizing barcode recognition with IBM Datacap Taskmaster Capture

Problem

What can be done to give the best recognition results in Datacap Taskmaster?

Cause

During printing, the ink can bleed or spread out over the white area, and then, during scanning, additional spreading of black may occur. As a result, the white spaces end up disappearing and the bars blend into each other. This can be seen by looking at the scanned image at high magnification. The barcode must meet the specifications after accounting for this.

Solution

To optimize barcode recognition:

• The width of the thinnest bar (called the X-dimension) must be at least one pixel, and two pixels are recommended for best results. At 200 DPI this means each bar must be at least .01 inch. Generally this translates to about 4 to 5 characters per inch.


• The X-dimension or width of the narrowest black bar and white space between bars must be at least 20 mils (1/50 inch, 1/2 mm). When scanned perfectly at 200 DPI this would result in 4 pixels, and at 300 DPI 6 pixels.


• For Code 39 symbols: a 20 mil X-dimension results in a density of approx 3.6 characters per inch. Optimally the height should be at least 1/4 inch or 15% of the width, whichever is greater, though this is not an absolute requirement. The minimum quiet zone (white space before and after the bar code) specified by the standard is 1/5 inch.


• Scanning can sometimes introduce white or black stripes on the image running in the scanning direction, typically vertical stripes if the paper is scanned in Portrait orientation. Bar codes printed in normal horizontal orientation cannot be read reliably when this occurs. It is advisable to print barcodes perpendicular to the direction of scanning. If the barcode must be printed horizontally on a page, scanning in landscape orientation will make the barcode more robust in the presence of common scanner issues.


• By default, Taskmaster Capture only accepts high confidence barcode images. To modify it to accept low confidence barcodes also, add the following action to run prior to barcode detection:
  
  SaveAsCurrentObjVariable (ReqConf, -1)
  
  


• Performing image enhancement (ImageFix) prior to running any barcode recognition action can possibly degrade the barcode, lowering recognition. If it is necessary to use image enhancement prior to barcode recognition, pay close attention to the configuration settings, especially vertical line removal and despeckle. To ensure image processing is not interfering with barcode recognition, test with the ImageFix() action removed.

Verify unable to populate fields during Click n Key in IBM Datacap Taskmaster Capture

Verify unable to populate fields during Click n Key in IBM Datacap Taskmaster Capture

Abstract

The fields are not getting populated during Verify in Taskmaster when selecting data from a page (Click n Key).

Cause

Full Page Recognition action was never called.

Resolving the problem

Recognize Page ruleset must call a Full Page Recognition action from ICR, OCR or OCRA in order for Click n Key to work properly.

How to restrict batches with IBM Datacap Taskmaster Capture

How to restrict batches with IBM Datacap Taskmaster Capture.

Abstracct

How can users be restricted to run only their own batches in Taskmaster Client or Taskmaster Web?

Solution

To have users scan, upload and verify only their own batches (or something similar), use the Store and Queue To task settings specified in Taskmaster Administrator's Workflow tab.

1. Run Taskmaster Client or Taskmaster Web.


2. Select Settings, Workflow in the client or go to Settings tab of Administrator in Taskmaster Web.


3. Highlight each Task in turn, and set the following:
   
   
   
   • Queue To - Select the option on how batches need to be restricted.
   
   
   • Store - Select the information that needs to be stored. Note that Queue To settings will not work properly if the needed information was not set to Store in the previous Task.
   
   
   
   


4. Select the Users tab if using TMA or LLLDAP authentication; else navigate to the Groups tab.


5. Highlight each user or group for which this restriction will apply and uncheck the Priority/Operator/Station change or Priority/Operator change privilege under the Job Monitor section.

By design the Store and Queue To settings will not have the same behavior in Taskmaster Client for pending batches. For example, a Verify pending batch may be run by any user, not necessarily by the operator who originally scanned the batch. However, batches that are in hold status can be limited to the operator that originally ran the task (e.g. Verify). 

Note: This requires that the general Job Monitor not be used to run the batch. Batches should be run through the Operations panel or tab.

Example configuration:

• Scan - (Store) Station and User


• Upload - (Queue to) Same station same user


• Verify - (Queue to) Same user

In this example, all batches scanned by a user will be uploaded only when logged into Taskmaster Web with the same user name and station ID, where the operator is a restricted user, and selecting the appropriate Operations shortcut. The same batches will be verified when logged into Taskmaster Web with the same user name, but not necessarily the same station ID.

How to make a Batch Pilot combo box list read only in IBM Datacap Taskmaster Capture

How to make a Batch Pilot combo box list read only in IBM Datacap Taskmaster Capture

Question

How to make a Batch Pilot combo box control drop down list read only.

Cause

By default, users may be able to type custom values into the control.

Answer

To make the control read only:

1. Open the form in Batch Pilot standalone and select the combo box.


2. Right-click and choose Properties.


3. Update Style to 2 - DropDownList.


4. Apply and save changes. Users will only be able to select a list option once accessing the updated form.

Using the Match Required and Locked properties can also provide similar behavior.

How to configure NENU for Windows authentication with IBM Datacap Taskmaster Capture

How to configure NENU for Windows authentication with IBM Datacap Taskmaster Capture

Question

My Taskmaster Server service uses Windows authentication (ADSI, LDAP, or LLLDAP). How do I configure NENU to authenticate to the Taskmaster Server service?

Answer

Employ the SetUser action to specify the Windows user name to use for authentication.

• example: SetUser(MyDomain\UserName)

Note: The SetPassword action is not used for this type of authentication and should not be included in the NENU ruleset.

Rebuild button missing on Fixup window with IBM Datacap Taskmaster Capture

Rebuild button missing on Fixup window with IBM Datacap Taskmaster Capture

Abstract

When performing a Fixup operation, the Rebuild button is not visible.

Cause

Feature is not enabled in Task Settings.

Resolving the problem

To enable the Rebuild button:

1. In Taskmaster Client, select Settings, Workflow.


2. Expand the Fixup job, highlight the Fixup task, and select Setup.


3. Check Allow Assemble and click Done, Apply, Done.

 

Why is an error received when IBM Datacap Taskmaster Client Service VScan accesses a remote directory?

Why is an error received when IBM Datacap Taskmaster Client Service VScan accesses a remote directory?

Abstract

IBM Datacap Taskmaster Client Service reports 'Folder ... does not exist' on the VScan rule action SetSourceDirectory(), where the directory path is a remote shared directory.

Symptom

 

• Remote shared directory is specified using UNC path such as \\server\share.


• Remote directory does exist.


• Taskmaster Client (thick client) works (without reporting the error).


• Taskmaster Client Service Logon User is set to a user having full permission to read/write to the remote directory.


• Remote share is a Unix-hosted file system.


• vscan_rrs.log reports Error: Folder '\\server\share' does not exist.

Cause

The Logon ID format is not accepted by the remote host.

Environment

Windows 2008

Resolving the problem

Change the Taskmaster Client Service Windows service Logon ID from a "User1@Domain" format to a "Domain\User1" format. For example, use the format FINANCE\jdoe instead of jdoe@FINANCE.local.

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Abstract

When running NENU, it fails on the SetPassword action with the following error:


13:45:13.811 (93) t:12E8 p:35FEED8 Error (-2147352567=hex:80020009). In CCom::Call: Action execution failed: object [Datacap.Libraries.Nenu.Actions] method [SetPassword] [api source:]

Cause

There is no password defined in the SetPassword action. This most commonly occurs when setting up a NENU ruleset to connect using Windows (NTA) authentication, as NTA authentication does not use a password.

Resolving the problem

If no password is needed, remove the action completely. Do not leave it in the ruleset with a null parameter.

Can Fixup rescan in duplex or multi-stream with IBM Datacap Taskmaster Capture?

Can Fixup rescan in duplex or multi-stream with IBM Datacap Taskmaster Capture?

Abstract

When scaning a batch using duplex and/or multi-stream, can the Rescan button be made to rescan in duplex or multi-stream also?

Answer

No. Only simplex rescanning is supported with the standard Fixup screen.

 

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Abstract

When running NENU, it fails on the SetPassword action with the following error:

13:45:13.811 (93) t:12E8 p:35FEED8 Error (-2147352567=hex:80020009). In CCom::Call: Action execution failed: object [Datacap.Libraries.Nenu.Actions] method [SetPassword] [api source:]

Cause

There is no password defined in the SetPassword action. This most commonly occurs when setting up a NENU ruleset to connect using Windows (NTA) authentication, as NTA authentication does not use a password.

Resolving the problem

If no password is needed, remove the action completely. Do not leave it in the ruleset with a null parameter.

Lookup column headers in wrong order with IBM Datacap Taskmaster Capture

Lookup column headers in wrong order with IBM Datacap Taskmaster Capture

Abstract

When using the Lookup field variable with Taskmaster Web, selecting the field lookup link during Verify brings up a window with Lookup results. In the window, the column headers do not align with the column data.

Symptom

When a column is selected, data posts correctly. That is, it posts to the fields as defined in the Lookup variable, not as shown in the Lookup window.

Cause

The column headers are being listed in alphabetical order, not the order defined in the Lookup variable. This has been identified as a product defect under APAR IO16583

Resolving the problem

The workaround is to list the database fields in alphabetical order within the SELECT query when configuring the Lookup variable.