#KTA 8.1 Fix Pack,#TTA 8.1 Fix Pack #Tungsten TotalAgility 8.1 Fix Pack #Tungsten TotalAgility 8.1
TotalAgility 8.1 Fix Packs – All
Fix Pack 6 – 13th Apr 2025
| Component | Issue |
|---|---|
| Transformation | The required server data 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. |
| Integration server | In the Integration Server, when multiple jobs attempted to access the same resources or activities simultaneously, the activities remained in a pending state due to the failure of the LockActivities() call. |
| Transformation | An error occurred while running OCR with Azure AI when “bring your own license” was used for Azure AI Document Intelligence. |
Fix Pack 5 – 3rd Apr 2025
| Component | Issue |
|---|---|
| Process | Could not save or release a process when a Dynamic complex variable was mapped to the document conversion password field. |
| Coreworker | 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 a two-hour period. |
| Coreworker | A .NET activity created and configured on the Integration Server remained in pending state and did not progress at runtime. |
| Forms | Blind double keying failed during validation on the third and subsequent documents because empty values were not recognized. |
| Installation | When installing TotalAgility using SQL Azure mode with the authentication method set to “Microsoft Entra ID – Managed Identity (User Assigned)”, an error occurred. |
| Installation | The installation of TotalAgility 8.1 with SQL Azure encountered a problem opening various TotalAgility components post installation. |
| Config Utility | On running the Configuration Utility, TotalAgility 8.1 did not display the additional authentication options related to Entra ID. |
| Form | When a calculation rule was created in a form and specific categories were filtered to add different global variables, some of those variables did not display correctly on validating the rule. |
| Transformation | There was a difference in how the same format locator extracted and returned date values between the two versions of Transformation Designer. |
| Form | A “Denial of Service” vulnerability was observed through JSON Object Injection when duplicate query columns were included in a request. An error occurred if the number of query columns exceeded a predefined limit of 50. |
| Transformation | Could not convert the HEIC format files to TIFF. |
| Form | The error message in a TotalAgility form included details about the form which could cause security risks. |
| Import Connector | When a corrupt email was received in Kofax Import Connector, the Passive Input for that mailbox changed from ‘green’ to ‘red’, which effectively disabled any further ingestion of emails from that mailbox. |
Fix Pack 4
| Component | Issue |
|---|---|
| Process | The jobs in TotalAgility were suspened with the following error: “The process cannot access the file because it is being used by another process.” |
| Transformation | When trace logging was enabled with multiple-file rollover in the Transformation Server roles, it stopped logging after a few hours, causing most of the Transformation Server roles to become unresponsive. |
| Process | When a nested business rule was executed within a form, it encountered an issue and resulted in the following error: “illegal characters in path.” |
| Transformation | 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. |
| Transformation | The Transformation Server activities in TotalAgility were suspended with an error. |
| GenAI | On upgrading TotalAgility to 8.1, the icon for Generative AI chat control was missing. |
| Reporting | In the Reporting server, data was lost when a transaction exception occurred. |
| Transformation | When using the new Azure Read OCR profile in Quick Capture, extraction failed with an “Invalid Rectangle” error for the Auto Extract Locator. This issue was also observed in Test Designer (TD) and during runtime extraction. |
| Package | When generating the XML document using the “Compare and deploy” option on a package for deployment to another environment with the same TotalAgility version, the following error occurred: “There was an error generating the XML document.” |
| Form | Could not delete all field values in the validation process when the InPlace Editor was enabled. |
| Reporting | The retention settings were incorrectly modified and set to zero when a tenant license was reactivated. |
| Workspace | When a workqueue query was configured with the “Return Query Total” option enabled, the total count returned was incorrect. |
| Transformation | An issue occurred with the stored procedure during document extraction using the CloudOCR package via PDTL (Predefined Document Type Locator). |
| Security | In TotalAgility Designer, when federated security was configured to use the “TotalAgility and the Provider logout” option with the endpoint type set to SAML, SLO (Single Logout) did not work as expecetd. |
| API | The GetJobs4() API method did not return any jobs when a system session ID was provided as input, and job access was restricted in the TotalAgility Designer system settings. |
| Transformation | Could not select the Line Item Matching Locator in a Table Locator configuration. |
Fix Pack 3 – 23rd Jan 2025
| Component | Issue |
|---|---|
| Form | When a condition was used in the form, the decimal delimiter did not work. |
| Form | The text could not be selected on a document after merging documents on the Validation screen. |
| Form | The Blind Double Keying process failed on the second document, allowing empty values to be accepted. |
| Form | The focus moved to the first page after rotation in an invalid document. |
| Designer | The user interface of the TotalAgility Designer was unusable after installing the fix pack for 8.1 if the server had no internet access. |
| Scan | The scanning could not be performed via flatbed using a Kodak S3100f scanner with a flatbed accessory when using TotalAgility. |
| Form | The image from the store did not load in a table (hyperlink). |
| Process | When debugging a process, a business rule could not be executed due to an “Illegal characters in path” error. |
| Process | When executing activities in a secure sandbox, expressions were suspended with a”Critical error.” |
| Transformation | An error occurred when the Online Learning folder was locked during the document deletion process. |
Fix Pack 2 – 24th Dec 2024
| Component | Issue |
|---|---|
| Gen AI | Could not save an Azure OpenAI Generative AI provider with the OAuth setting, as it kept loading indefinitely. However, it saved successfully when set to ChatGPT, and then it could be switched back to Azure OpenAI without issues. |
| Import Connector | Could not generate a PDF when importing the eml file that was digitally signed and contained a PDF attachment via Import Connector. |
| Core worker | The startup time for the secure sandbox of a Core Worker service was not aligned with the startup time of IIS. |
| Process | The 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.” |
| Transformation | Document extraction failed due to exceeding data egress limits from a low retry interval, resulting in request failures. |
| Transformation | 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. |
| Form | TotalAgility application became unresponsive, and an error appeared when confirming the last field with actions on the form multiple times. |
| Process | The KCM (Kofax Communication Manager) compose activity was suspended when the process map was configured to run in synchronous mode. |
| Core worker | In a TotalAgility production environment with a large number of tenants and CoreWorker load, the .Net or Capture activities sometimes failed with errors. |
| Installer | The installation of the TotalAgility 8.1 fix pack failed with the “Violation of Primary Key Constraint” error. |
Fix Pack 1 – 28th Nov 2024
| Component | Issue |
|---|---|
| Process | The SafeScripting sandbox start time was notably slower in TotalAgility 8.0. |
| Package | If non-default US date and time formats were used, the following error occurred when importing a package: “String was not recognized as a valid DateTime”. |
| Reporting | The DeleteBatchSessSnapshotFact1 step during Reporting retention consumed a lot of CPU affecting the user performance. |
| Scan | The CAP_PRINTERINDEX web service call did not work for a scan using a Ricoh fi-8950 TWAIN driver. |
| Form | After logging out and logging back in, the Validation form changed to a “Best Fit” layout for image preview. |
| Authentication | The private key JWT client (JSON Web Token) assertion body contained quotes for numeric field values ‘iat’ and ‘exp’. |
| Permission | 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. |
| The DirectIngest settings were not included in the Azure Configuration Schema. | |
| Transformation Designer | In the Transformation Designer, the extraction results for a sample document encountered errors. |
| Transformation | The Online Learning Dynamic Specific Knowledge Base files failed to handle encryption correctly, leading to uncontrolled growth of the knowledge base training files during each iteration of Online Learning. |
| Web capture | When a Canon scanner with Web Capture was used in TotalAgility, an error occurred during the scanning process. |
| Broken Access Control within resources actioned Simple Object Access Protocol application programming interface (SOAP API). | |
| SDK | The SQL injection vulnerabilities or database errors were observed when sending a SOAP request to the UpdateDocumentVariant SOAP action in CaptureDocumentService. |
| Form | The SetFocus event targeted the wrong field when the form loaded. |
| Form | 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. |
| Process | When an exception was raised during the execution of the RPA (Robotic Process Automation) activity, the TotalAgility job was completed without any errors instead of getting suspended. |
| Process | The Subject and Body fields for all Email activities in a process appeared empty. |
| Authentication | In TotalAgility Designer, when federated security was configured to use the “TotalAgility and the Provider logout” option with the endpoint type set to SAML, an error occurred when logging out. |
| Transformation | 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. |
| Installer | The installation of the TotalAgility 8.1 fix pack failed with the following error: “Illegal characters in path.” |