Kofax Transformation Modules 7.1.0 Fix Pack 15
Build Date: Month DD, 2024
© 2024 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
You can install Kofax Transformation Modules 7.1.0.15 to resolve the issues listed below.
Note: To install Kofax Transformation Modules 7.1.0.15 successfully, an existing full installation of Kofax Transformation Modules 7.1.0 is required.
If you need to perform a full product installation, see the Kofax Transformation Modules Installation Guide for instructions.
Issues resolved in this fix pack
ID | Issue | Solution |
---|---|---|
2156123 | Bar Code Locator - Datamatrix - Support ISO 8859-1 charset. |
The ISO 8859-1 character set is supported by the Bar Code Locator. |
2148260 | Automatic image cleanup does not work. |
Image cleanup using background removal has been improved and works as expected during runtime. |
Issues resolved in previous fix packs
Fix Pack 14
ID | Issue | Solution |
---|---|---|
2145251 | OCR is not generated for 200+ pages scanned batches. |
OCR data is now available for all documents, including documents with greater than 200 pages. |
2138110 | Multiple calls to FormXtra are increasing the response time. |
Calls to FromXtra have been reduced, response time has been improved, and a caching mechanism is available to optimize field reader object creation and overall response times. Configure the FieldReaderCacheSize setting in the C:\Program Files (x86)\Common Files\Kofax\FormXtra7.6\Kofax.FormXtra.Host.exe.config file. The default value for the FieldReaderCacheSize setting is 20. The value for this setting must be a numeric value and if the value is less than or equal to 0, the cache mechanism is disabled. |
2134986 | Performance Issue on Document Routing |
Document routing has been improved to eliminate performance issues. |
Fix Pack 13
ID | Issue | Solution |
---|---|---|
2131164 | AZL does not map extraction results valid alternatives to Field. |
The extraction results for an Advanced Zone Locator are mapped to fields as expected. |
2129939 | 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) |
2128899 | 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. |
2127985 | 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. |
Fix Pack 12
ID | Issue | Solution |
---|---|---|
2122341 | Check locator performance is slow, causing delays and low throughput in result extraction. |
Throughput of the Check Locator was improved. |
Fix Pack 11
ID | Issue | Solution |
---|---|---|
2111035 | Check Locator Fails to Recognize Date Value. |
The Check Locator now extracts the date values as expected. |
Fix Pack 10
ID | Issue | Solution |
---|---|---|
2110992 | 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. |
2101939 | Format Locator does not return all spaces with dictionaries. |
The Format Locator includes spaces between words of matched text returned from a dictionary. |
2100501 | 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. |
Fix Pack 9
ID | Issue | Solution |
---|---|---|
2100058 | OmniPage OCR text is missing at runtime. |
OCR text extracted using the OmniPage recognition engine is no longer missing at runtime. |
2099007 | Server fails to extract data from a multi-page document. |
Multi-page documents are successfully extracted by the Server module. |
2087612 | 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. |
Fix Pack 8
ID | Issue | Solution |
---|---|---|
ER2087993 | 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; |
2037037 | 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). |
Fix Pack 7
ID | Issue | Solution |
---|---|---|
2085057 | 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. |
2070115 | 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. |
2068647 | 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. |
2066633 | 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. |
2038357 | Omnipage OCR text is missing at runtime. |
OmniPage OCR text is now available at runtime, as expected. |
Fix Pack 6
ID | Issue | Solution |
---|---|---|
2061620 | Project Save does not save project when upgrading from previous version. |
Projects are now saved after upgrading from a previous version. |
2061910 | Number "1" when alone is not recognized by OmniPage. |
After an update to the OmniPage recognition engine, the number "1" is recognized as expected. |
2061616 | Project not saved after extraction training. |
Projects are now saved after extraction training. |
2057622 | Database Locator does not exclude Own Address from Document during Extraction. |
The Database Locator correctly excludes the records in the exclusion database during extraction. |
2038009 | 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. |
1985051 | 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. |
Fix Pack 5
ID | Issue | Solution |
---|---|---|
1996513 | Performance Issue In Barcode Locator When Selecting 2D Barcodes |
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 |
Fix Pack 4
ID | Issue | Solution |
---|---|---|
1996619 | Validation module - floating docker not visible after module close. | The visibility of the floating document viewer window is no longer lost. Instead, its position is saved to the user settings, and its position is the same each time the Validation module is used. |
1994347 | Fox-Exception: Index (-1) out of range (0-1) in Validation when opening document. | An error no longer occurs when opening a document in the Validation module. |
Fix Pack 3
ID | Issue | Solution |
---|---|---|
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. |
|
1984414 | The Validation module does not reload form with scripted document reclassification. | The batch tree is correctly updated when scripted document reclassification is used. |
1983215 | Database lookup button with alternatives fails to fill read-only fields. | Read-only fields are successfully filled when a database lookup button is configured to find locator alternatives and there are subclasses with inherited locators. |
1982557 | Add Project Merge Tool option to copy the online learning settings. | The Project Merge Tool can now merge online learning settings. |
1980071 | OmniPage is experiencing problems when trying to read data that is in front of a bar code. |
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 |
1978056 | Bar code type PDF 417 High Accuracy does not extract value from a PDF 417 bar code, but PDF 417 BC type does. |
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. |
1971306 | Clicking the backspace key in Document Review when searching for a class name removes multiple characters at once. | In the Class search textbox, if the entire text is selected then pressing the backspace key removes all the selected text. Otherwise, pressing the backspace key removes one character at a time. |
Fix Pack 2
ID | Issue | Solution |
---|---|---|
1970519 | In Project Builder, switching to a different configuration set does not work because the previously saved configuration set is being set to the active configuration. | It is now possible to successfully switch to a different configuration set. |
1975170 | Project merging overwrites and clears existing resource localizations. |
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. |
Fix Pack 1
ID | Issue | Solution |
---|---|---|
1968104 | Extraction training in Project Builder causes out of memory error. | An out-of-memory error is no longer encountered when performing extraction training in the Project Builder. |
1967336 | Registration of the zone is not working properly in AZL. | Zones are now registered correctly when using an Advanced Zone Locator. |
1966998 | Validation is not opening when running in a terminal or Citrix session. | To overcome the logging concurrency issue, every module and process now creates its own log file. This makes the Logs Aggregation setting in the Service Configuration Tool obsolete. |
1962460 | Omnipage OCR MRZ line with "<<" read as single character « or additional quotes. |
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. |
1962408 | Project Builder crashes when importing a text file into local fuzzy database if data for a column has more than 96 characters. |
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. |
1961726 | Typing a wrong character in Document Review when searching for a class deletes everything that has been typed. | Typed text is now preserved so if you type an incorrect character, the existing content in the search box is not deleted, even when there are no matching entries in the class list. |
1957760 | OMR Zone Test not showing the "Blackness" in 7.0. | OMR zones are now correctly displaying what percentage of an OMR zone is marked. |
1956970 | Resetting the window positions causes an error in the Validation user module which cannot be closed. | Resetting the window positions no longer causes an error in the Validation user module. It is also possible to close the module afterward. |
1956736 | Document Review module drop-down classification search issue. | The selected class is now highlighted and displayed in the drop-down list. |
1951911 | Project Settings Mixed recognition page profile is set to None after Project Merge Tool. | After projects are merged with the Project Merge Tool, any Mixed Print recognition profiles are merged as expected. |
1951391 | Duplicate execution + log entries for most of the licensing calls. | Duplicate licensing related entries are no longer included in the log. |
1946462 | Volume count is not decrementing from "KTM Invoice Add-On Pack License" when we process Lim Locator in runtime. | Added missing fallback implementation redirecting to Invoice Add-on license if the Line Item Matching Locator license is missing. |
1946345 | AZL - Copy locator method fails on specific project - invalid stol argument. | An error is no longer encountered when using the Copy Locator Method setting for an Advanced Zone Locator. |
1934791 | StructuredException in Validation when the user reclassifies via script. | An error no longer occurs when a user reclassifies a document in Validation via script. |
Applies to
This fix pack is cumulative and includes the resolved issues released in previous Kofax Transformation Modules 7.1.0 fix packs.
You can apply this fix pack to update Kofax Transformation Modules 7.1.0.
Files included
This fix pack includes the following files:
File name | Version |
---|---|
KofaxTransformationModules.exe | 7.1.0.15 |
CscProj.24.dll | 7.1.0.15 |
FoxForms.24.dll | 7.1.0.15 |
FoxRecogFineReader.24.dll | 7.1.0.15 |
FoxRecogOmniPage.24.dll | 7.1.0.15 |
ReadMe-KTM-7.1.0.15.htm | N/A |
Install This Fix Pack
Before installing this fix pack, note the following:
-
You must have full Windows administrative privileges to perform these procedures.
-
Make sure that Kofax Capture and Kofax Transformation Modules 7.1.0 are installed before applying the fix pack.
-
Install the fix pack on each client and standalone workstation running Kofax Transformation Modules.
Use the following procedure to install this fix pack.
Close all Kofax Transformation Modules applications and services.
-
Double-click KofaxTransformationModules-7.1.0.15.exe to install this fix pack.
When you are notified that the installation process has successfully completed, click OK to clear the confirmation message.
Note A log file is created automatically in the location defined in the TEMP environment variable. Access this path by typing %Temp% in Windows Explorer.
Remove This Fix Pack
Before removing this Fix Pack, note the following:
-
You must have full Windows administrative privileges to perform these procedures.
-
Have access to KofaxTransformationModules-7.1.0.iso", the original installer program for Kofax Transformation Modules 7.1.0 .
Mount the ISO image or use the network resource.
Use the following procedure to remove the fix pack.
- Terminate all running Kofax Transformation Modules applications and services.
- In Control Panel, select Programs and Features > View installed updates.
- On the list of updates, in the Name column, select the item that corresponds to Kofax Transformation Modules 7.1.0 Fix Pack 11.
- Right-click and select Uninstall.
- Restart any applications/services that were stopped prior to removing the fix pack.