Kofax Transformation Modules 7.0.0 Fix Pack 14

It is now possible to improve the recognition of text adjacent to bar codes by enabling bar code zoning.

Note: If this setting is enabled using script, it is possible that the bar code is recognized as random characters when full page OCR is performed.

The Bar Code Locator still recognizes bar codes successfully.

The following example shows how to enable bar code zoning via script:

Private Sub Application_InitializeScript() Dim pageProfile As IMpsRecogProfile Dim pageProfileOP As MpsPageRecogProfileOmniPage Set pageProfile = Project.RecogProfiles.ItemByName("OmniPage") Set pageProfileOP = pageProfile pageProfileOP.EnableBarcodeZoning = True End Sub

When a high accuracy bar code is selected, extraction is first attempted with the OmniPage recognition engine. If that fails, a specialized recognition engine is called. This helps ensure that bar codes are recognized with higher accuracy.

In addition to the PDF 417 High Accuracy bar code, there are also the Data Matrix High Accuracy and QR Code High Accuracy bar code types. The recognition of high accuracy bar codes prioritizes recognition accuracy over speed.

Localizations are no longer overwritten during a project merge where the destination project contains localizations and the source project does not.

This is because the 'copy localizations' setting is not activated in this situation.

A new setting for OmniPage page profiles and the OmniPage zone profiles is available to process MRZ. This new setting is called MRZ Mode.

When selected, a specialized recognition engine is used to process the document and the recognition accuracy of any non-MRZ text may be reduced.

In addition, for OmniPage zone profiles, the Print Type is automatically set to OCR-B.

Project Builder no longer crashes if a database value has more than 96 characters.

Instead, up to 255 characters are now allowed, and in the unlikely event that a value exceeds this length restriction, the value truncated after 255 characters and Project Builder runs as expected.

1953285

Bar code type Code 39 vertically is not detected.

The OmniPage recognition engine was updated to the 21.1.0.11 fix pack.

This improves the recognition of Code 39 bar codes regardless of their orientation, PDF417 bar codes, patch codes, and recognition accuracy.

1953130

Bar Code Locator does not reliably recognize patch codes on the page.

1942751

Accuracy: 'O' vs '0' nonrecognition in Invoice Numbers.

1937773

Bar codes not reading with OmniPage.

1900005

Bar Code Locator does not reliably recognize patch codes on the page.

XValues are no longer lost when using multiple instances of KTM Server.

If two Server instances (Server1 and Server2) are used for a project and one instance performs classification and the other performs extraction, then the following script sample shows how to copy the XValues so they are available in KTM Server2.

The following script sample calls a function from the project script for the Document_AfterClassify and Document_BeforeExtract methods.

Public Sub CaptureFieldsToKTMFields(pXDoc As CscXDocument) If Project.ScriptExecutionMode=CscScriptExecutionMode.CscScriptModeServer Then Dim lCount As Long For lCount = 0 To pXDoc.Fields.Count - 1 Dim Key As String Key = "AC_FIELD_" & pXDoc.Fields.ItemByIndex(lCount).Name If pXDoc.XValues.ItemExists(Key) Then pXDoc.Fields.ItemByIndex(lCount).Text = pXDoc.XValues.ItemByName(Key).Value End If Next End If End Sub

It is now possible to configure Kofax Transformation Modules so that each process of a KTM Module application generates its own separate log file.

To configure this, open the Service Configuration Tool and set the Log aggregation setting to False.

A new setting called Idle time before terminating process [min] is now available in the Service Configuration tool.

This setting enables you to specify how long to wait before terminating an idle extraction process.

A new setting called Show All Columns is now available when configuring a fuzzy database lookup.

When selected, all database columns are displayed in the Database Lookup Window in Validation, even if they are not selected and included in the fuzzy search.

This setting is set to FALSE by default.

When filtering the list of classes in the Document Review Class List combo box, the entered text filters the text in two ways:

1. First, any classes that start with the filtered text appears in alphabetical order in the filtered list.

2. Next, any classes that contain the filtered text anywhere in their name are displayed at the bottom of the list, also in alphabetical order.

For example, if you have 5 classes called Invoices, Purchase Orders, Service Orders, Order Forms, and Accounting Orders, and you type ‘order’ in the Class List, the results are as follows:

• Order form

• Accounting Orders

• Purchase Orders

• Service Orders

When a user enters a value in the Class combobox to search for a class and then uses the down arrow to select a class, the full results are no longer displayed.

Instead, the entered value filters the class list based on the entered string as expected.