Changes in behavior

The A2iA Cursive Page Recognition (DocumentReader) functionality is now deprecated and no longer available in Kofax Transformation Modules. As a result, if you open a project that uses one or more Cursive (A2iA DR 9.1) recognition profiles that was created in an earlier version of Kofax Transformation Modules, these profiles are replaced with OmniPage page profiles with default settings. Review the new OmniPage page profiles and adjust them as required.

The A2iA Check and Cursive Recognition (FieldReader and CheckReader) functionality is no longer supported in Kofax Transformation Modules 7.0.0 and no further improvements will be made. The Check and Cursive Recognition Add-on is available to migrate existing A2iA Zone Locators. This recognition engine is available for reference purposes and so that existing projects with remaining licenses can make use of this functionality. However, the use of the A2iA Zone Locator is no longer supported. Instead, use the Check Locator.

The Bar Code Locator has been updated to use the OmniPage recognition engine for bar code recognition. All new bar code locators no longer have the FineReader tab. Instead, a Settings tab is provided instead, using OmniPage bar code recognition.

The OmniPage bar code recognition does not support Code 32, Aztec (1D), and MaxiCode bar code types. To use these bar code types, use Enhanced Bar Code recognition instead.

The full classification results are now attached to each alternative of the Classification Locator.

This information is available to scripting for further analysis as needed.

		Private Sub Document_AfterLocate(ByVal pXDoc As CASCADELib.CscXDocument, ByVal LocatorName As String)
			Dim layoutresultxml As String
			Dim layoutresult As New CscResult
			layoutresultxml = pXDoc.Locators.ItemByName("ClassificationLocatorName").Alternatives(0).XValues.ItemByName("__LayoutClassificationResult__").Value
			layoutresult.LoadFromXmlString(layoutresultxml)

			Dim contentresultxml As String
			Dim contentresult As New CscResult
			contentresultxml = pXDoc.Locators.ItemByName("ClassificationLocatorName").Alternatives(0).XValues.ItemByName("__ContentClassificationResult__").Value
			contentresult.LoadFromXmlString(contentresultxml)
		End Sub

This recognition engine is deprecated and no longer installed alongside Kofax Transformation Modules. As a result, if you open a project that was created in an earlier version of Kofax Transformation Modules and that project uses one or more FineReader recognition profiles, a project warning message id displayed explaining that the FineReader recognition engine is no longer available and that you can no longer use those FineReader recognition profiles.

A corresponding OmniPage profile is created for each FineReader profile. The OmniPage copy is a replacement for the FineReader profiles, yet the FineReader profiles are still available for reference purposes. Any unsupported language in the OmniPage recognition engine are mapped to a similar language that uses the same character-set. It is no longer possible to add new profiles or modify any existing profile to use the FineReader recognition engine.

If you attempt to perform OCR when your project is configured to use one or more FineReader recognition profiles, a fallback mechanism performs recognition using the corresponding OmniPage profile. This fallback mechanism does not negatively affect the recognition performance. When you decide to remove a FineReader profile, you are prompted to confirm its deletion and notified that the corresponding OmniPage fallback profile is renamed to match the FineReader profile that you are deleting. All instances where that profile is used, such as locators, profiles, and fields, are updated to use the renamed OmniPage fallback profile. The renaming of the OmniPage profile also takes over the internal IDs used the deleted FineReader profile. This ensures that there are no issues in scripting where references to recognition profiles is done using names and internal IDs.

When modifying an older project that uses FineReader profiles, it is recommended that any additions to that project use the OmniPage recognition profiles instead of the old FineReader profiles.

The OmniPage recognition engine was updated to version 21.10.6.

1409707: If you modify the online learning path, ensure that no other projects are using that path. Any data in the online learning folder may be corrupted and cause problems for other projects.

Now, when a project is opened a backup copy of the training database is created if Project Builder detects that the database structure has changed and the data model requires an upgrade. This can happen when the same learning folder is used for a production project and a copy of that same project is used for development. This backup copy is available to restore the older state of the database if needed.

1299270: Several improvements have been made to the automatic mode of the Table Locator. Because of this, PDF table extraction has significantly improved.

1528486: The arrows to reorder the list of remove fuzzy databases as well as the default icon have been removed because these had no affect on database access.

It is now possible to redirect user settings for rich-client user modules so that they are saved in the APPDATA folder, rather than the default LOCALAPPDATA.

This is done by editing the <%ProgramData%>\DOXiS\CaptureSV\Config\ACConfig.xml file.

Once this setting is in place, user settings related to docking or toolbar customizations are redirected to the APPDATA folder.

Add <AppData UseRoaming="1" /> to the configuration file using the following syntax. Create the <Transformation> node if it does not already exist:

			<ACConfig>
			.
			.
			.
			   <Transformation>
			.
			.
				 <AppData UseRoaming="1" />
			.
			.
			   </Transformation>
			.
			.
			.
			</ACConfig>