Kofax Transformation Modules 7.1.0 Fix Pack 13

AZL does not map extraction results valid alternatives to Field.

The extraction results for an Advanced Zone Locator are mapped to fields as expected.

Validation: Extend API to define table column position by script.

Use the following script to order the table columns in the Validation form.

Note: The OrderValFormTableColumns() method should be called from the Application_InitializeBatch event.

Private Sub OrderValFormTableColumns(ByVal className As String, ByVal valTabIndex As Integer, ByVal tableIndex As Integer, ByVal requiredColumnOrder() As Integer) If Not Project.ScriptExecutionMode = CscScriptModeValidation Then Exit Sub End If Dim valForm As New CscValidationForm Dim valTab As New CscValidationTab Dim validationTable As CscValidationTable 'getting validation form & validation tyab objects based on class index Set valForm = Project.ClassByName(className).ValidationForm Set valTab = valForm.ValidationTabs.ItemByIndex(valTabIndex) Set validationTable = valTab.ValidationTables.ItemByIndex(tableIndex) Dim columnCount As Integer columnCount = validationTable.ValidationTableColumns.Count-1 'Checking the column order is in the required order or not If IsColumnsAreRequiredOrder(requiredColumnOrder, validationTable) Then Exit Sub End If 'Storing the columns into a temporary collection ReDim valTableColumns(columnCount) As CscValidationTableColumn Dim i As Integer For i = 0 To columnCount Set valTableColumns(i) = validationTable.ValidationTableColumns(i) Next i 'Removing the columns from the table For i = 0 To columnCount validationTable.ValidationTableColumns.RemoveByID(valTableColumns(i).ColumnID) Next i 'Inserting the columns according to the required order Dim validationTableColumn As CscValidationTableColumn For i = 0 To columnCount Set validationTableColumn = GetValidationColumn(valTableColumns, requiredColumnOrder(i)) If Not validationTableColumn Is Nothing Then validationTable.ValidationTableColumns.Add(validationTableColumn) End If Next i End Sub Private Function IsColumnsAreRequiredOrder(ByVal columnOrder() As Integer, ByVal validationTable As CASCADELib.CscValidationTable) As Boolean Dim i As Integer For i = 0 To UBound(columnOrder) If columnOrder(i) <> validationTable.ValidationTableColumns(i).ColumnID Then IsColumnsAreRequiredOrder = False Exit Function End If Next i IsColumnsAreRequiredOrder = True End Function Private Function GetValidationColumn(ByVal valTableColumns() As CASCADELib.CscValidationTableColumn, ByVal columnId As Integer) As CASCADELib.CscValidationTableColumn Dim i As Integer For i = 0 To UBound(valTableColumns) If valTableColumns(i).ColumnID = columnId Then Set GetValidationColumn = valTableColumns(i) Exit Function End If Next i Set GetValidationColumn = Nothing End Function

Here is how to invoke the method:

OrderValFormTableColumns(<className>,<ValidationTabIndex>,<tableIndex>, <ColumnOrder>)

For example:

'required column order ReDim requiredColumnOrder(6) As Integer requiredColumnOrder(0) = 2 requiredColumnOrder(1) = 1 requiredColumnOrder(2) = 10000 requiredColumnOrder(3) = 9 requiredColumnOrder(4) = 20001 requiredColumnOrder(5) = 3 requiredColumnOrder(6) = 4 OrderValFormTableColumns("Dell", 0, 0, requiredColumnOrder)

The Enhanced results are found under the page representation, but not in the Bar Code Locator results in the XDC file.

The enhanced bar code recognition results are now available in both the XDoc page representation and the Bar Code Locator results.

The entire text of the "USPS OneCode 4-State Customer Bar code" was not being recognized.

After upgrading the OmniPage recognition engine, the specified bar code is recognized as expected.

Check locator performance is slow, causing delays and low throughput in result extraction.

Throughput of the Check Locator was improved.

Check Locator Fails to Recognize Date Value.

The Check Locator now extracts the date values as expected.

ODBC - IBM DB2 - Failing to display the first database rows in the UI causing a configuration issue.

It is possible to successfully select a table entry from an ODBC data source that is connected to a DB2 database.

Format Locator does not return all spaces with dictionaries.

The Format Locator includes spaces between words of matched text returned from a dictionary.

The Table Locator needs much more time to extract big tables than in old version.

Improvements have been made to table extraction, minimizing the time required to extract large tables.

OmniPage OCR text is missing at runtime.

OCR text extracted using the OmniPage recognition engine is no longer missing at runtime.

Server fails to extract data from a multi-page document.

Multi-page documents are successfully extracted by the Server module.

Folder fields are not readable by script when pages are rotated by the Server module.

Folder fields are accessible by script, even when pages are rotated by the Server module.

CheckLocator does not return "CheckType" parameters as did the A2iA CheckReader.

The Check Locator has a new setting to extract the document type subfield.

The following sample script enables the DOCUMENT_TYPE subfield and CscCheckLocatorDocumentType enumeration values are the possible outcome for DOCUMENT_TYPE subfield:

Private Sub Document_BeforeLocate(ByVal pXDoc As CASCADELib.CscXDocument, ByVal LocatorName As String) If (LocatorName = "CheckLocator") Then Dim Locator As CscCheckLocator Set Locator = Project.ClassByName("CheckClass").Locators.ItemByName(LocatorName).LocatorMethod Locator.RecognizeDocumentType = True End If End Sub typedef enum CscCheckLocatorDocumentType { CscCheckLocatorDocumentTypeUnkown = 0, CscCheckLocatorDocumentTypePersonal = 1, CscCheckLocatorDocumentTypeBusinessOrCashTicket = 2, CscCheckLocatorDocumentTypeDepositSlip = 3, CscCheckLocatorDocumentTypeMoneyOrder = 4, CscCheckLocatorDocumentTypeIrd = 5, CscCheckLocatorDocumentTypeIrdBusiness = 6, CscCheckLocatorDocumentTypeTravelers = 7, CscCheckLocatorDocumentTypeBusiness = 8, CscCheckLocatorDocumentTypeInternal = 9, CscCheckLocatorDocumentTypeNotMoneyOrder = 65540 } CscCheckLocatorDocumentType;

Omnipage OCR incorrectly recognizing zeros (0) as capitol o (O)

The OmniPage recognition engine is now able to successfully recognize the difference between zeros (0) and captial os (O).

Database object CscDatabase does not close file handle anymore, so deletion of temporary files fails.

This error no longer occurs after database import due to file handling improvements.

The license utility shows error on Cursive Handprint Recognition as not licensed.

An incorrect licensing error for the FormXtra recognition engine is no longer displayed when performing cursive handwriting recognition.

AZL test confidence level is lower with OmniPage Engine although the text exactly matches that one on the document.

The confidence level is now increased for accurate text as expected after an upgrade of the OmniPage recognition engine to V22.0.0.7.1.

KTM Server large batches (> than 200 pages) failed in KTM Server due to error 'Item with name 'kfxParentDocumentsInBatch' not found.'

This error no longer occurs due to changes when creating child batches.

Omnipage OCR text is missing at runtime.

OmniPage OCR text is now available at runtime, as expected.

Project Save does not save project when upgrading from previous version.

Projects are now saved after upgrading from a previous version.

Number "1" when alone is not recognized by OmniPage.

After an update to the OmniPage recognition engine, the number "1" is recognized as expected.

Project not saved after extraction training.

Projects are now saved after extraction training.

Database Locator does not exclude Own Address from Document during Extraction.

The Database Locator correctly excludes the records in the exclusion database during extraction.

Empty field value after confirming value in drop down box filled by dictionary in the Validation module.

The field value selected from a list populated from a dictionary is now saved as expected in the Validation module.

KBLS service crashes after enormous service memory increase.

The Knowledge Base Learning Server no longer crashes due to memory issues because improvements were made to memory handling.

Two properties are now available in the Bar Code Locator to improve recognition time and accuracy. These properties are BarTradeOff and BarScanInterval.

The following script sample shows how to use these properties in the BeforeLocate event.

Private Sub Document_BeforeLocate(ByVal pXDoc As CASCADELib.CscXDocument, ByVal LocatorName As String) If(LocatorName = "BarcodeLocator") Then Dim Loc As CscBarcodeLocator Set Loc = Project.ClassByIndex(0).Locators.ItemByName(LocatorName).LocatorMethod Loc.BarTradeOff = CscBarcodeLocTradeOffFastest Loc.BarScanInterval = 5 End If End Sub

1985957

Bar Code Locator using OmniPage engine returns bar code of previous document.

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

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

1982562

Patch codes are not recognized with OmniPage engine on some documents.

1956906

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

1956911

Bar Code Locator shows wrong results from PDF417 bar code with both FDF417 recognition profiles.

1956901

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

1954128

Bar codes not reading with OmniPage.

1953811

Bar code type Code 39 vertically is not detected.

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 using the fast and accurate mode. 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.