#KTA 2025.2 Fix Pack,#TTA 2025.2 Fix Pack, #Tungsten TotalAgility 2025.2 Fix Packs, #Tungsten TotalAgility 2025.2
TotalAgility 2025.2 Fix Packs – All
Fix Pack 1 – 16th Oct 2025
| Component | Issue |
|---|---|
| Transformation | Email body conversion did not work correctly. |
| Transformation | An issue occurred with PDF generation where some images generated from email bodies appeared blurred. |
| Package | During package export and import, security tokens and roles assigned to controls embedded within a Scan control were not included. |
| Process | Debugging a business process that calls a Restful Webservice failed with the following error, “The job has been suspended. Error. Failed to execute business rule.” |
| System | The TotalAgility application failed to load the assembly System.Diagnostics.DiagnosticSource (version 6.0.0.2) or one of its required dependencies. |
| Forms | Duplicate rows appeared when working through a long table. |
| Security | The replay protection mechanism failed, allowing the RequestToken from a previous unsuccessful response header to be re-used, thereby enabling replay attacks. |
| Reporting | After data retention in the Reporting system, the unique doc_key in Kofax Analytics for TotalAgility was reused. Instead of continuing from the next identity value, it was reassigned starting from the current maximum ID in the table. This resulted in mixed and inconsistent report data, as old keys overlapped with newly generated ones. |
| Forms | The calendar year was not displayed properly when the browser zoom level was set to 75% or higher. |
| Transformation | If an Online Learning–enabled activity was completed while the Online Learning system task was still processing, the operation stayed in a ‘Processing’ state until a timeout occurred. |
| Transformation | An error occurred when completing an Online Learning–enabled activity while the Online Learning system task was still active. |
| Reporting | The document variants were not deleted once the retention policy criteria were met. |
| SEcurity | In TotalAgility, there was a security issue where the TotalAgilityPasswordBlacklist.txt file, which contained a list of forbidden passwords, was exposed without authentication. |
| Transformation | The “LLM license not found” error appeared for each document during classification/extraction, indicating that GetAIProxyServiceInfo() was invoked even though no related features were in use. |
| Transformation | Connecting to the Production Transformation Designer returned “Insufficient licensing” for the requested module or feature. |
| Forms | An error occurred with the Begin Condition action when the target field being checked was empty or null. |
| Import connector | The original filename was recorded incorrectly when using a Tungsten XML import file. |
| Package | When processes were deployed from one TotalAgility system to another (such as test or production), the user who last modified the asset (processes, forms, and more) changed unexpectedly. |
| Package | After deployment, the “Last modified by” value changed unexpectedly. |
| Import Connector | When the unsupported or invalid emails were received in a polled mailbox, TotalAgility (via the shared Message Connector pool) could not import them, resulting in a backlog of emails in the mailbox. |
| System | An issue occurred with SMTP settings using oAuth configuration. |
| Transformation | XLS to PDF document conversion failed with the following error: “Conversion to PDF failed with error code 50102: Unable to convert file to specified format – Shape to image Error!”. |
| Transformation | When the classification group was used for project-level classification, running the classification locator ignored the project-level logic, returning only general categories like Instructions and Content Classification. |
| Transformation | Running OCR with an Azure profile returned an error. |
| Core Worker | Rolling over consolidated logging caused a memory leak in the Core Worker process. |
| Transformation | The following error occurred during the completion of validation processes: “Cannot process OL folders. ExecuteNonQuery requires an open and available Connection. The connection’s current state is closed.” |
| Transformation | When processing a large batch of documents through classification/separation, the job was suspended with an error. |
| Forms | The Capture control changes via an event incorrectly triggered another event. |
| Transformation | The PDF generation activity was suspended despite enabling the “Reject documents on exceptions” setting. |
| Transformation | When an attachment was added to a document and processed through PDF Generation with the new compression setting, the attachment was lost. |
| Forms | The predefined rejection reasons from the first document type validated in a session were persistently displayed for all subsequent document types in a Validation form, instead of showing the rejection reasons for the current document type. |
| Forms | When an expression node was executed synchronously within the CompleteActivityAndProgress() method, the following error occurred: “Index was out of range. Must be non-negative and less than the size of the collection.” |
| Forms | An error occurred in an Expression activity, when multiple fields were mapped, each referencing the same document but different attributes. |
| Transformation | Normalize to PDF/A failed to convert a document. |
| Transformation | A PDF document was ingested, but the resulting document contained fewer pages than expected. Some pages were not processed, possibly due to blank-page removal or unrecognized content. |
| Transformation | Predefined Document Type Locator returned “License details are invalid” when the license server used a MAC address as machine ID. |