Resolved issues
This topic lists previously reported issues that are resolved in Tungsten TotalAgility 2025.2.
| ID | Description |
|---|---|
|
2202142 |
The Message Connector failed to connect to the Tungsten Import Connector mailbox because the buffer size allocated for storing the server's return token was insufficient. |
|
2196591, 2191482 |
In the Transformation Designer, the Advanced Table Locator did not detect tables correctly. |
|
2194522 |
When using the default Tungsten Generative AI provider configuration in the Transformation Designer, filtering content based on a prompt resulted in an error from the Auto Extract Locator. |
|
2193193 |
When the "Field forced valid" event was executed in the Validation form, the actions configured in the "Text changed" event were also triggered, leading to unintended behavior. |
|
2193168 |
When inserting a new record, the system failed to recognize that a duplicate record with the same key already existed, resulting in the following error: "Violation of UNIQUE KEY constraint 'group_value_uq'." |
|
2192759 |
The "StructuredException" error occurred when using a classification with Script locators. |
|
2192544 |
The changes made to the Script locator regions were not retained when releasing a project in the Transformation Designer. |
|
2190978 |
The server data required to execute OCR with Azure AI Document Intelligence via the Tungsten proxy server was missing from the script events for document separation in Transformation Designer. |
|
2190737 |
The eVRS image processing in Web Capture Service was slow, affecting the ability to scan large batches. |
|
2190423 |
In the Integration Server, when multiple jobs attempted to access the same resources or activities simultaneously, activities remained pending due to the failure of the LockActivities() call. |
|
2190372 |
The source file of the last page in a batch was empty after scanning. |
|
2189206 |
When using a form template that had multiple actions configured, the actions appeared without the postfix text in the forms. |
|
2189204 |
Secure server variable values were written to the job note when the job was suspended on a .NET activity. |
|
2188522 |
When saving the SOAP web service that used a client certificate, the following error occurred: "A secure SSL/TLS channel could not be established." |
|
2188031 |
The Session Validation setting in a TotalAgility form failed to enforce session-based authentication, allowing the execution of server-side actions without a valid session and posing a security risk. |
|
2187552 |
The behavior of the Radio button list control changed between different TotalAgility versions, specifically when the Changed Event was triggered, and the "Clear Selection" action was used. |
|
2187167 |
When an additional filter was applied in the work queue, the original field filter was removed. |
|
2186745 |
The inline styles applied to the Capture combo box were not reflected in the drop-down data at runtime, although the label styles worked properly. |
|
2186515 |
If the PDF generated by the GetDocumentAsFile2 method was large, it could not be downloaded. |
|
2186395 |
When a Post Validation Handler that called a business rule returned a Dynamic complex variable as an output, the following error occurred: "Illegal characters in file name." |
|
2186288 |
There were orphaned entries in the AW_RESOURCE table after upgrading the job for the map that used floating roles. |
|
2185471 |
The documents rejected by the Transformation Server were not logged in the reporting table. |
|
2185091 |
When a Dynamic complex variable was mapped to the document conversion Password field, the process could not be saved or released. |
|
2180502 |
In a TotalAgility multi-tenant environment, several tenants experienced a decrease in job throughput due to an activity that consumed 76% of the Core Worker activity thread time over two hours. |
|
2180410 |
A .NET activity created and configured on the Integration Server remained pending and did not progress at runtime. |
|
2179719 |
The TotalAgility installer incorrectly indicated a successful installation, even though it failed to rename the performance counters. |
|
2178900 |
Could not save the sorting in a query when a metadata field was created. |
|
2178871 |
Blind double keying failed during validation on the third and subsequent documents because empty values were not recognized. |
|
2177145 |
In TotalAgility, the jobs were suspended with the following error: "The process cannot access the file because it is being used by another process." |
|
2176670 |
On running the Configuration Utility, TotalAgility 8.1 did not display the additional authentication options related to Entra ID. |
|
2176669 |
The installation of TotalAgility 8.1 with SQL Azure encountered a problem opening various TotalAgility components post-installation. |
|
2176549 |
The "CleanOnRoleRecycle" setting for the Transformation Server roles was not set to false, which caused the cached .NET assembly to be deleted upon rebooting the Transformation Server roles. |
|
2176548 |
The Transformation Server activities in TotalAgility were suspended with an error. |
|
2176326 |
The keyboard navigation failed on the Complete Activity message triggered by the Refresh capture action. |
|
2175529 |
There was a difference in how the same format locator extracted and returned date values between two versions of Transformation Designer. |
|
2175452 |
On upgrading TotalAgility, the icon for the Generative AI chat control was missing. |
|
2175156 |
The transaction associated with the current connection was completed instead of being disposed of before the connection could be used to execute SQL statements. |
|
2175121 |
In Reporting, there was data loss when a transaction exception occurred. |
|
2174815 |
The reporting queries were timed out after 30 seconds instead of using the timeout configured for DatabaseCmdTimeoutSec. |
|
2174325 |
Could not convert the HEIC format files to TIFF. |
|
2173988 |
There was a difference in the behavior of the Radio button list control between different versions of TotalAgility. |
|
2173685 |
When installing TotalAgility using SQL Azure mode with the authentication method set to "Microsoft Entra ID - Managed Identity (User Assigned)", an error occurred. |
|
2173605 |
Could not delete all field values in the validation process when the InPlace Editor was enabled. |
|
2173464 |
The retention settings were incorrectly modified and set to zero when a tenant license was reactivated. |
|
2173204 |
An error occurred when generating the XML document using the "Compare and deploy" option on a package for deployment to another environment with the same TotalAgility version. |
|
2173019 |
When a calculation rule was created in a form and specific categories were filtered to add different global variables, not all variables were displayed correctly after rule validation. |
|
2171789 |
When a work queue query was configured with "Return query total" enabled, the total count returned was incorrect. |
|
2170267 |
When a corrupt email was received in Import Connector, the Passive Input for that mailbox changed from green to red, and any further ingestion of email was effectively disabled. |
|
2169200 |
The silent installation of the separate license server fix pack failed and required Internet Information Services configuration. |
|
2168098 |
In TotalAgility Designer, when federated security was configured to use "TotalAgility and Provider" logout option with the endpoint type set to SAML, SLO (Single Logout) did not work as expected. |
|
2166981 |
When a condition was used in the form, the decimal delimiter did not work. |
|
2166848 |
The text could not be selected on a document after merging documents on the Validation screen. |
|
2165734 |
The user interface of the TotalAgility Designer was unusable after installing the fix pack if the server had no internet access. |
|
2164864 |
The image from the store did not load in a table (hyperlink). |
|
2164165 |
When the activities containing expressions were executed, the jobs were suspended with an error. |
|
2164021 |
Scanning could not be performed via flatbed using a Kodak S3100f scanner with a flatbed accessory when using TotalAgility. |
|
2163570 |
When debugging a process, a business rule could not be executed due to an "Illegal characters in path" error. |
|
2162820 |
Could not save an Azure OpenAI Generative AI provider with the OAuth setting, as it kept loading indefinitely. |
|
2162066 |
Jobs were suspended with the following error: "The process cannot access 'XYZ.dll' or one of its dependencies because it is currently in use by another process." |
|
2162029 |
The startup time for the secure sandbox of a Core Worker service was not aligned with the startup time of IIS. |
|
2161851 |
An error occurred when the Online Learning folder was locked during the document deletion process. |
|
2159400 |
An issue occurred when the AI locator was used with the splitting feature during document review. After the initial extraction, when a document was split for review, the subsequent extraction was suspended. |
|
2159371 |
A Scan form failed to automatically generate a unique number using a stored procedure and populate a field via a DB query action. |
|
2158324 |
The SafeScripting sandbox start time was notably slower in TotalAgility 8.0. |
|
2153156 |
The DeleteBatchSessSnapshotFact1 step consumed excessive CPU during Reporting retention, affecting the user's performance. |
|
2151256 |
The GetJobs4() API method did not return any jobs when a system session ID was provided as an input, and job access was restricted in the TotalAgility Designer system settings. |
|
2151031 |
Document extraction failed due to exceeding data egress limits from a low retry interval, resulting in request failures. |
|
2150927 |
The TCM compose activity was suspended when the process map was configured to run in a synchronous mode. |
|
2150741 |
The Online Learning Dynamic Specific Knowledge Base files failed to handle encryption correctly, leading to the uncontrolled growth of the knowledge base training files during each iteration of Online Learning. |
|
2149520 |
In the Transformation Designer, the extraction results for a sample document encountered errors. |
|
2149203 |
The private key JWT client (JSON Web Token) assertion body contained quotes for numeric field values iat and exp. |
|
2149159 |
A user assigned maintenance permission on a classification or extraction group, directly or via a group, could log in and change the permission level assigned to self. |
|
2149063 |
In a TotalAgility production environment with a large number of tenants and CoreWorker load, the .NET or Capture activities sometimes failed with errors. |
|
2148441 |
After logging out and logging back in, the Validation form automatically changed to a "Best fit" layout for image previews. |
|
2147695 |
When a Canon scanner with Web Capture was used for scanning in TotalAgility, an error occurred. |
|
2147261 |
Scanning via the flatbed using a Kodak i3400 scanner with a flatbed accessory could not be performed when using TotalAgility. |
|
2147237 |
The Broken Access Control within the resources actioned the Simple Object Access Protocol application programming interface (SOAP API). |
|
2145336 |
SQL injection vulnerabilities or database errors were observed when sending a SOAP request to the UpdateDocumentVariant SOAP action in CaptureDocumentService. |
|
2144539 |
The CAP_PRINTERINDEX web service call did not work for a scan using a Ricoh fi-8950 TWAIN driver with the imprinter disabled. |
|
2142485 |
The installation of the TotalAgility 8.1 fix pack failed with the "Violation of Primary Key Constraint" error. |
|
2141275 |
When the document and activity variants were used to generate the "Scan create new job" and "Validation" forms, the variations were not applied as expected. |
|
2138124 |
In a process, the Subject and Body fields for all Email activities appeared empty. |
|
2144214 |
TotalAgility application became unresponsive, and an error appeared when the last field with actions on the form was confirmed multiple times. |
|
2138000 |
When a classification group was used as a dynamic variable in a "Document review" activity, the document type could not be selected after the document was loaded. |
|
2135955 |
The extraction process failed due to an evaluation setting issue. |
|
2087808 |
The recognition could not be performed due to the following OmniPage error: "Recognition process hard TimeOut." |
|
2085396 |
The system returned a bad request when Federated Security used "TotalAgility and Provider" logout option with the SAML endpoint type. |