Tungsten TotalAgility 2025.2 Update 5

The maximum page limit for the Predefined Document Type Locator is increased from 20 to 50. The limit is no longer hard-coded and can now be configured through the user interface or via script, with a default value of 20 pages.

The Document generation node is enhanced to ensure TotalAgility variable values are correctly passed to barcode merge fields in Microsoft Word templates. You can use TotalAgility variables to populate barcode merge fields, enabling accurate barcode generation based on runtime data.

Follow the steps below to insert a barcode field into a Microsoft Word template.

1. Open the Word document where you want to insert the barcode.
2. Press Ctrl + F9 to insert a pair of Word field braces { }. (Do not type the braces manually.)
3. Inside the braces, type one of the following field codes depending on the requirement. To display the value along with the barcode, include the \t switch.
   
   Dynamic (merge field) barcode:
   { DISPLAYBARCODE "{ MERGEFIELD FieldName }" CODE128 \t }
   Replace FieldName with the actual merge field name used in your data source.
   
   Static barcode example:
   { DISPLAYBARCODE "490123456789" EAN13 \t }
   Note: EAN13 requires exactly 12 numeric characters.
4. Press Alt + F9 to toggle between the field code view and the barcode preview.
5. Save the document as a Word Template (.dotx).

A retry mechanism has been implemented to improve resilience when using the Predefined Document Type Locator (PDTL).

The enhancements include:

• Automatic retries for transient HTTP errors.
• The following HTTP status codes are treated as transient: 408, 429, and 500–599.
• Retry handling for transient empty results that may occur due to server-side conditions.

The Restful Service activity has now been implemented in the Integration Server.

The Artificial Intelligence (AI) Search schema has been updated to support sorting and faceted searches on key fields, enabling future enhancements like analytics, dropdowns, and document counts. These changes improve flexibility and prepare the system for advanced UI and admin features.

The existing "Knowledge base search" activity is renamed to "Knowledge discovery agent."

You can disable the CorrectSplittedNumbers normalization in Azure page profiles.

The new "Microsoft Document Intelligence Layout Model" is now integrated into extraction pipeline services. This enhancement provides more accurate and flexible document data-extraction capabilities. The output generated by the Layout Model is stored at the page level in a JSON file and written to the text-extension field, Kofax.CEBPM.RawPageData.

TotalAgility supports Amazon S3 with IAM Role–based authentication, eliminating the need for Access Key and Secret Key credentials. When TotalAgility runs on an Amazon EC2 instance configured with an IAM Assumed Role that has S3 access, Capture data can now be stored securely in Amazon S3 without static credentials. Use the Configuration Utility to switch existing storage settings to Amazon S3 (IAM Assumed Role).

Note: If you plan to use this feature, uninstall the Repository Browser from "Programs and Features" in the Control Panel and install the updated version included in the update archive.

OAuth authentication is added when configuring the recognition providers in TotalAgility, and OCR providers in Transformation Designer for recognizing OCR documents.

The document generation now retains original fonts during output, including Code 39 barcode fonts.

Accessibility is improved by resolving issues related to screen readers, keyboard navigation, and contrast ratios. These updates make the product easier to use for all users and align with accessibility best practices.

Active Directory synchronization is enhanced to support additional attributes for populating the resource name in TotalAgility. You can now configure the AD_DISPLAYNAME_FIELD server variable to use AD attributes such as UPN (User Principal Name) or CN (Common Name) as the resource name. If no value or an invalid value is specified for AD_DISPLAYNAME_FIELD, the Display Name is used by default when syncing resources.

The Workqueue and Job list filters support group-level supervisor–subordinate relationships. This enhancement improves visibility and management of assigned work.

Federated security is enhanced to handle encrypted SAML responses. TotalAgility Designer provides decryption settings, allowing you to configure a certificate that will be used to decrypt encrypted assertions. If the provider does not return encrypted assertions, assertion certificates are not required.

The "Require Session ID" system setting allows you to enforce session validation for the File Upload control. This ensures that a valid Session ID is required before a file can be uploaded to the TotalAgility database, thereby enforcing authentication and enhancing security.

TotalAgility uses the newer JsonWebTokenHandler .NET class, which supports empty payloads, replacing the older JwtSecurityTokenHandler class previously in use.

The Tenant Management System now supports OAuth authentication for SMTP, replacing outdated basic authentication. This change is essential due to Microsoft Exchange's deprecation of basic authentication. To enable OAuth for Simple Mail Transfer Protocol (SMTP), you must configure the following AppSettings in the Tenant Management System:

Following are the steps to configure OAuth (Client Credentials) for Microsoft Exchange:

1. Navigate to KofaxTotalAgility-8.0.1.11/Utilities/ConfigurationUtility.

2. Run KTAConfigurationUtility.exe as an administrator.

3. Select the TMS tab.

4. In the Send Mail group, provide the OAuth configuration details.

5. On the Authentication list, select OAuth and enter the details for the following settings: Server name with port, User Name, OAuth Client ID, OAuth Client Secret, OAuth Access Token URL, Provide OAuth Scope, and From Address.

6. To enable SSL, select the check box for SSL Enabled.

7. Click Save.

The mapping of data object variables is supported in skin rules. You can only map simple fields in a data model, and this works correctly for top-level items. While you can select nested object fields in the Designer, these fields are currently not supported.