Tungsten Transformation Modules (KTM) 7.1.0 Fix Pack 3 | Release Date: September 8, 2023

Problems Resolved in this Fix Pack

1985957: Bar Code Locator using OmniPage engine returns bar code of previous document
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. 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.
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:

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.

Problems Resolved in previous Fix Packs

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.
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.