› Changes in behavior

Changes in behavior

This topic describes changes to the product behavior since the previous release.

Changes to CreateJobSyncWithDocument(s) APIs

In previous releases, the CreateJobSyncWithDocument() and CreateJobSyncWithDocuments() SDK APIs only worked when using TotalAgility RTTI mode.

These APIs now work even when not using the TotalAgility RTTI mode.

Refresh interval in seconds

You can now set the refresh interval on a tile in seconds. In past releases, the minimum refresh interval was 1 minute.

Activity notification changes

Using the activity notification, you can handle the user logon and redirection to the correct take activity page without having to create separate forms.

In the Resource assignment tab of activity properties, if you select Send email under Activity Notification and then select Append associated file, the email includes a URL where the associated file is passed as part of the TargetForm parameter. If you set the URL to http://<machine name>/TotalAgility/Forms/Custom/logon.html, the user will be logged on and redirected to the associated file.

Capture Client: Display of out-of-the-box error

For the "Create New job" event of a Scan control, if the job creation failed for any reason, the following message was displayed: "The 'create new job' operation was cancelled."

The Cancel message box is no longer displayed for all actions, except for the confirm field and field forced valid actions.

Capture Client: Ability to disable the Change Document Type dialog box

When changing the document type in validation activities, a dialog box appears for confirmation that states:

"Are you sure you want to change the document type? The field data may be lost."

You can now disable this confirmation prompt to avoid additional clicks for the validation users.

Features removed

The following features are removed from TotalAgility.

Document process in Workspace

The functionality to generate process documentation is now available in the Transformation Designer; you can no longer document processes from within Workspace. In the Administration menu, the Processes menu is replaced by View Process and the Document Process option is removed.

Monitoring Workload

The Monitoring Workload functionality has not been ported from TotalAgility 5.5 to 7.X. However, only the relevant Exception code (EXP0011) was removed.

The following items are also removed:

  • Work process setting for Workload from system settings: System > System settings

  • Relevant database columns from the SERVER_DATA table (ADVANCE_SCAN_HOURS, ADVANCE_SCAN_MINS)

  • Any relevant functionality being called by the Monitor.

  • The following database columns from the SERVER_DATA table:

    • REOFFER_TIME

    • REOFFER_PERIOD

    • CANCEL_PERIOD

    • CANCEL_TIME

Transformation Server Execution system task for TotalAgility on-premise installation

The Transformation Server Execution system task is only used for TotalAgility on-premise multi-tenant and Azure installations. Therefore, it is removed for the TotalAgility on-premise installation.

Use of .NET 3.5

TotalAgility components no longer require .NET 3.5.

The onLoaded event note for Capture control documentation

As a Capture control behaves the same as non-Capture, the following note is removed for the Capture control onLoaded event documentation in Kofax TotalAgility Designer Help:

Capture activity forms operate differently from other forms types in how they render. This is due to the ThinClient control, which requires that the onLoad actions complete before it can fully render itself. So even though the BeforeRender or AfterRender events may have triggered on the containing form, the form itself may not actually have been rendered to the required state.

Changes to PDF profile

The settings within the Optimization settings and Image encoding groups in the PDF profile are removed.

Obsolete database tables

The following tables in the TotalAgility database are removed, as they are obsolete.

  • ADD_IN

  • XML_TEMPLATE

  • MODULE

  • BAM_NODE_DETAILS

  • BAM_NODE_VARIABLE_INFO

  • CASE_DEF_VF_INDEX_DATA

  • CASE_VF_FILES

  • CASE_VF_FOLDERS

  • COM_ACTIVITY_DETAIL

  • MAP_DISTRIBUTION

Features deprecated

The following features are deprecated in TotalAgility.

A2iA recognition

The A2iA Cursive Page Recognition (DocumentReader) functionality is now deprecated and no longer available in Kofax TotalAgility. As a result, if you open a project in Transformation Designer that uses one or more Cursive (A2iA DR 9.1) recognition profiles that was created in an earlier version of Kofax TotalAgility, 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 TotalAgility 7.10.0 and no further improvements will be made. The A2iA Check and Cursive Recognition are available to migrate existing A2iA Zone Locators, 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.

FineReader recognition

This recognition engine is deprecated and no longer installed alongside Transformation Server. As a result, if you open a project in Transformation Designer that was created in an earlier version of Kofax TotalAgility 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 languages 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.

Bar code recognition

If a Bar Code Locator uses the deprecated FineReader enhanced bar code recognition, the Bar Code Locator is updated to use OmniPage instead. 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.