VScan limit to number of characters allowed in file path and name of input images in IBM Datacap Taskmaster Capture

VScan limit to number of characters allowed in file path

and name of input images in IBM Datacap Taskmaster Capture

Abstract

VScan limit to number of characters allowed in file path and name of input images in IBM Datacap Taskmaster Capture

Symptom

VScan aborts every time when scanning an image, but is successful when shortening the file name

Resolving the problem

The VScan actions have a limitation to the number of characters allowed in the combined file path and name of a source image attempting to be scanned. If this proves problematic for some images, try shortening the file name, moving files to a less deeply nested file system folder, and/or specifying an input path directory that is shorter in length (e.g. by using an appropriate file share).

IBM Datacap Taskmaster Capture 8.0.0 and later:

• File path and name cannot exceed 200 characters

Taskmaster 7.6 and earlier:

• File path and name cannot exceed 128 characters

 

Supported nesting level for Convert / number is out of scope error reported in IBM Datacap Taskmaster Capture

Supported nesting level for Convert / number is out of

scope error reported in IBM Datacap Taskmaster Capture

Abstract

Supported nesting level for Convert / "number is out of scope" error reported in IBM Datacap Taskmaster Capture

Symptom

During conversion of documents into images using the Convert library actions, you may experience an aborted batch with a "number is out of scope" exception in the RRS log.

Resolving the problem

This behavior is by design as the Convert actions support a maximum nesting level of 3 (FileA -> FileB -> FileC -> FileD). This limitation is noted in the Datacap Studio help text for the Convert actions library. Documents that fail to adhere to this nesting level are unsupported and will abort.

Examples:

Msg -> Zip -> Word -> TIFF is OK

Msg -> Msg -> Zip -> single-page TIFF is OK

Msg -> Msg -> Zip -> Excel -> TIFF is not OK, batch aborts

EML -> Msg -> Zip -> Word -> TIFF is not OK, batch aborts

 

Microsoft Exchange mail actions, EWSMail, do not create images for the message body in IBM Datacap Taskmaster Capture

Microsoft Exchange mail actions, EWSMail, do not create

images for the message body in IBM Datacap Taskmaster Capture

Abstract

Microsoft Exchange mail actions, EWSMail, do not create images for the message body in IBM Datacap Taskmaster Capture

Symptom

When scanning with the Microsoft Exchange mail actions, no images are created for a message's body contents.

Resolving the problem

This is working as designed as documented in the Datacap Studio help text for the EWSMail actions library. When scanning attachments using the Microsoft Exchange mail actions, the body text is placed into the document level Body variable. To obtain an image of the message body, scan the message itself into the batch as an EML file using the action ex_EMLOption(1) prior to ex_scan. Once the EML has been ingested, it can be converted later in the workflow using the Convert library actions.

Note: The Convert library supports a limited nesting level of 3. If the message contains attachments which nest deeply within themselves, an abort may occur during conversion.

 

Batch Pilot task completes without processing any actions in IBM Datacap Taskmaster Capture

Batch Pilot task completes without processing any

actions in IBM Datacap Taskmaster Capture

Abstract

Batch Pilot task completes without processing any actions

Symptom

Taskmaster Client or Taskmaster Client Service task completes with "finished" status but no RRS log is created when task logging is properly configured. This may especially apply after using the Datacap Studio Application Wizard to create a new application based on a preexisting one.

Cause

Batch Pilot tasks run by Taskmaster Client or Taskmaster Client Service execute RRS or actions via a form. For background tasks, Batch Pilot uses \Datacap\BPilot\Rulerun\rrs_run.dcf, which must be assigned at the application (batch) level in the Batch Pilot Project setup. If the form is not attached at that level, then the task will complete without running any rules.
Note: In Verify the forms used are custom to the application and based on the document hierarchy. These forms are assigned at the page, not application (batch), level.

 

Resolving the problem

To resolve this for a background task:

 

1. Open Batch Pilot stand-alone. Use \Datacap\BPilot\BPilot.exe or the Start Menu shortcut


2. Open the Batch Pilot Project (BPP) file for the affected task


3. Right-click the application/batch type, e.g. APT, and choose Pick Form


4. Navigate to and select rrs_run.dcf (This can be a local or UNC path to be run by all Rulerunners)


5. Exit Batch Pilot and choose Yes when promoted to save

Note: This document is intended for background tasks only. If you are experiencing similar behavior in Verify where the form does not load, but the task finishes without error, ensure that the Batch Pilot Project has a Verify form assigned to each page type used by Verify. If this is not the issue, check the page file (e.g. Verify.xml) and ensure that all pages were assigned proper types during page identification.

 

Encountering error, You do not have permission to run DStudio, when attempting to log into Datacap Studio 8.0.1 in IBM Datacap Taskmaster Capture

Encountering error, You do not have permission to run

DStudio, when attempting to log into Datacap Studio 8.0.1

in IBM Datacap Taskmaster Capture

Abstract

Unable to log into Datacap Studio 8.0.1 using the default "admin" account and password.

Cause

Permissions for specific groups and users must be granted..

Resolving the problem

First, check to see if "Datacap Studio" is checked in your Taskmaster Administrator under the Users tab --> "Privileges" --> "Client's" (From Taskmaster Administrator)?

If yes, and you are still not able to log into DC studio, try the following:

1. Update the Admin database to allow selected users and/or groups to access Datacap Studio.Using any database editor, access the Taskmaster Admin database, "tmuser" table, and change the "us_perm" value for the administrative user to "-1". (This gives the administrator all permissions, including the new Datacap Studio and Password Change privileges.)


2. Next,log in (your application) as the Administrator and assign Datacap Studio and/or Password Change permission to other users and groups as desired. (If the Taskmaster Admin database is in Microsoft Access or Microsoft SQL Server, execute the following query: UPDATE tmuser SET us_perm = -1 WHERE us_id= admin;)

 

Why are split batches not keeping the high priority setting in IBM Datacap Taskmaster Capture?

Why are split batches not keeping the high priority

setting in IBM Datacap Taskmaster Capture?

 Abstract

I have a Taskmaster application that performs a split of a batch. If I set the priority on a batch to "high" and Taskmaster performs the split of the batch, the split batch does not keep the high priority and gets reverted back to the default priority.

Symptom

Split batches are not retaining the priority for documents.

Cause

Taskmaster Server is not configured correctly for the Child job to inherit priorities.

Diagnosing the problem

In the Job Monitor, find the column for "Pr". If the original batch is set to priority 1 and split batch is performed, review the column for "Pr" for the new split batch. If it is reverted to the default of 5 and you wish that the new split batch maintains the high priority of 1, then you need to review the configuration of your Taskmaster Server.

Resolving the problem

Run your Taskmaster Server Manager. Click on the "Taskmaster" tab and check to see if the setting "Child job inherits priority" is enabled. Split batches are considered child jobs in IBM Datacap Taskmaster Capture. Once you have this setting enabled, save the settings. You will need to restart Taskmaster Server if the service is running. As a warning, when restarting the Taskmaster Server, make sure no Taskmaster Client services, Quattro services, Taskmaster Web, RuleRunner Servers, or client PCs are running or connected to the Taskmaster Server so that no loss of data or errors occur.

 

AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Auto Delete does not contain a 'suspended'

batch status filter in Datacap Taskmaster Capture

Abstract

AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Resolving the problem

The "suspended" status is normally not used, but batches can be set to the status using the rrunner library action SetTaskStatus or some equivalent. In AutoDelete there is no filter for the batch status; this limitation is removed in IBM Datacap Taskmaster Capture 8.0.0 and later through NENU, the replacement for AutoDelete.

In Taskmaster 7.6 and earlier, batches with the "suspended" status can be deleted manually through the Job Monitor. In IBM Datacap Taskmaster Capture Client the Job Monitor Filter menu has a SQL button where a customized filter can be inserted -- the value qu_status IN ('suspended') can be used to show only batch records with the suspended status. Similar functionality exists in Taskmaster Web with the Monitor's Filter button screen.