#KTA 8.0 Fix Pack,#TTA 8.0 Fix Pack #Tungsten TotalAgility 8.0 Fix Pack #Tungsten TotalAgility 8.0
TotalAgility 8.0 Fix Packs – All
Fix Pack 10 – 4th Apr 2025
| Component | Issue |
|---|---|
| Webservice | When saving the SOAP web service that used a client certificate, the following error occurred: “A secure SSL/TLS channel could not be established.” |
| Process | The notification email sent from an ordinary activity did not show the URL link correctly as it became text due to an additional “\r\n” added as a prefix. |
| Transformation | Could not perform recognition due to the following internal Omnipage error: “General Protection Fault in the Engine.” |
| Form | Blind double keying failed during validation on the third and subsequent documents because empty values were not recognized. |
| 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 after the rule was validated. |
Fix Pack 9 – 24th Jan 2025
| Component | Issue |
|---|---|
| Process | 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. |
| Form | The error message in a TotalAgility form included details about the form which could cause security risks. |
| Config | The retention settings were incorrectly modified and set to zero when a tenant license was reactivated. |
| Conversion | Could not convert the HEIC format files to TIFF. |
| 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 8 – 24th Jan 2025
| Component | Issue |
|---|---|
| Process | 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. |
| 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. |
| Scan | The scanning could not be performed via flatbed using a Kodak S3100f scanner with a flatbed accessory when using TotalAgility. |
| Transformation | An error occurred when the Online Learning folder was locked during the document deletion process. |
Fix Pack 7 – 19th Dec 2024
| Component | Issue |
|---|---|
| Process | When the activities containing expressions were executed, the jobs were suspended with an error. |
| 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.” |
| API Config | 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. |
| Transformation | Document extraction failed due to exceeding data egress limits from a low retry interval, resulting in request failures. |
| Form | TotalAgility application became unresponsive, and an error appeared when confirming the last field with actions on the form multiple times. |
| 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. |
| 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.0 fix pack failed with the “Violation of Primary Key Constraint” error. |
Fix Pack 6 – 21st 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. |
| Process | The DirectIngest settings were not included in the Azure Config Schema. |
| Scan | The CAP_PRINTERINDEX web service call did not work for a scan using a Ricoh fi-8950 TWAIN driver with Imprinter disabled. |
| Form | Tungsten TotalAgility 8.0.x Validation Form will change to “Best Fit” layout after Re-Login. |
| Process | 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. |
| Transformation Designer | In the Transformation Designer, the extraction results for a sample document encountered errors. |
| Web capture | When Canon scanner with Web Capture was used for scanning in TotalAgility, an error occurred during the scanning process. |
| API | Broken Access Control within resources actioned Simple Object Access Protocol application programming interface (SOAP API). |
| SDK | SQL injection vulnerabilities or database errors were observed when sending a SOAP request to the UpdateDocumentVariant SOAP action in CaptureDocumentService. |
| 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, an error occurred when logging out. |
Fix Pack 5 – 28th Oct 2024
| Component | Issue |
|---|---|
| Coreworker | In a TotalAgility production environment with a large number of tenants and CoreWorker load, .Net or Capture activities sometimes failed with errors. |
| Pacakage | On importing the process via patch package, the work type that was included in the package was no longer associated with the process. |
| 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. |
| Form | The SetFocus event was targeting 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 RPA (Robotic Process Automation) activity, the TotalAgility job was completed without any errors, instead of getting suspended. |
| Process | In a process, the Subject and Body fields for all Email activities appeared empty. |
Fix Pack 4 – 20th Sep 2024
| Component | Issue |
|---|---|
| Form | 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. |
| Package | When a case definition with skins was added to a package, IIS did not work. |
| Transformation | The extraction process failed due to an evaluation setting issue. |
| Package | When creating or importing a category, all items were associated despite not being associated before. |
| Process | When calling a business rule with a Boolean initialization variable from a process and not mapping it with any variable or value, the job was suspended with the following error: Failed to execute business rule: . The executor returned: “Variable is declared as Bool in the process map , it cannot have value as “.”. |
| Transformation | Extraction results using AZL for extracting a date were dissimilar at runtime versus design time. |
| Coreworker | Azure WaWorkerHost.exe maxed out Core Worker Role CPU with Unity logging enabled. |
| Process | The process could not access the *_tmp file, as it was in use with another process. |
| Transformation Designer | The Transformation Designer projects could not be opened due to the following error: “External component has thrown an exception”. |
| Reporting | The Reporting process failed with the following error: “Cannot insert duplicate key in object ‘dbo.@p'”. |
| Reporting | The Reporting Retention query consumed a lot of CPU. |
| Repporting | An error occurred when reporting tried to add duplicate entries to the “doc_accum_fact” table. |
| Form | When an Activity form was regenerated on a process that contained the input and output variables, the following error occurred: “Index must be within the bounds of the list.” |
| Import Connector | An error occurred when the “BinaryObject.Id” seed value exceeded the maximum integer value, and when the messages were transferred from the Import Connector to TotalAgility. |
| Process | When an API call was used to classify documents in TotalAgility, the Category and Classification group were displayed as ‘Not Set’ in Analytics for TotalAgility. |
| Conversion | The PDF/A generated with file attachment did not comply with the PDF standard. |
| Process | The document data was not displayed in the Analytics for TotalAgility reports. |
| Process | Database timeout occurred when large data was added to the TotalAgility database as part of the JobEvaluation worker task. |
| Import Connector | Kofax Import Connector cut off the sides of certain images so that they became unreadable. |
Fix Pack 3 – 15th Aug 2024
| Component | Issue |
|---|---|
| Configuration Utility | When the Configuration Utility was used to modify database connections, only the main database could be altered, and not the other database connections. |
| Process | The Loop activity failed with the following error: “The job has been suspended.Variable LOOPID does not support null value.” |
| Authentication | Could not configure an oAuth server that used the shared secret key JSON Web Token authentication method. |
| Form | When a DB query action was used in a multi-line text box to manage database records, a null value was returned, and an error occurred. |
| Process | The variables of a TotalAgility process did not appear on the Variables tab of a TotalAgility process. This problem is specific to large processes. |
| Transformation | There was a performance issue with Check Locator in processing the documents when compared to A2iA Zone Locator. |
| Conversion | The document conversion failed when certain documents were converted to “PDF/A-2b” or “PDF/A-3b”. |
| Process | The client assertions generated by TotalAgility resulted in issues with a few providers such as AWS and TotalAgility token endpoint. |
| Form | The legend for the Chart control was cut off. |
| SDK | ImportPackageFromStream in custom code resulted in an “object reference has not been set to an object instance” error for large packages. |
| Form | The following error occurred in a Validation activity: “Cannot insert duplicate key object ‘dbo.@valuesTable’. The duplicate key value is (XXX)when a processing job.” |
| Conversion | When a process was configured with an Image processing activity, converting the text files to Tiff caused font and alignment issues. |
| Transformation Designer | When the extraction group was opened in the Transformation Designer, an error occurred. |
| SDK | The encryption of ImageID was not added to all SDK methods, that resulted in the usage of the same URL to view multiple images. For more details, see Additional information. |
| Import Connector | When the Import Connector was configured to poll the messages, the polled messages were moved to the processed folder but remained unread instead of being marked as read. |
| Process | TotalAgility jobs did not the return OCR results. |
| Conversion | The attachments names were missing from the ‘Body’ document after conversion. |
| Import Connector | When there were multiple RightFax connectors, there was a delay importing the RightFax files into TotalAgility. |
Fix Pack 2
| Component | Issue |
|---|---|
| Coreworker | Agility.Server.Core.Executor.exe process consumed 100% of CPU space on Azure Core Worker roles. |
| Process | On debugging a process that contained a business rule node in which the Complex variable was used as an output, the process debugging failed. |
| Form | When a job was created on a Scan form, the SPP resource ID was entered instead of the logged on resource ID. |
| Transformation Designer | In the Transformation Designer, when Online Learning was performed on a folder, the documents were not moved from the “Ready to Train” folder to the “Temp” folder, and an error occurred. |
| Form | When a Business rule action was called in the Complete Activity event of a Validation form, the business rule failed with the following error: “Service Call Failed: 0 – error’ when making a GetFolder() call.” |
| Transformation | Could not perform Tungsten Transformation Toolkit Online Learning on a folder. |
| Form | When a skin was used, the new Validation form assigned to the process or skin was not used after modification and regeneration. Instead, the old Validation form was retained. |
| Process | When a document variant was used during validation and specific table columns were ignored, this resulted in the table not being valid at runtime, and the activity could not progress. |
| SDK | When the CreateJobSyncWithDocuments() was used against an RTTS instance pointed to the Azure tenant, the job was suspended with an index error. |
| Package | When a package that contained the currency codes was imported, the Artifact filter did not work. |
| Scan | Could not perform scanning via the flatbed using a Kodak i3400 scanner with a flatbed accessory when using TotalAgility. |
| SDK | The ActivityService.GetWorkqueueOverview API timedout with a relatively low number of jobs, especially when additional activity resources were added. |
| Transformation | The document for online learning was missing page images and a source file, which led to processing errors. |
| Process | When a data model column was updated with a date variable containing milliseconds, the returned date format did not include the milliseconds value. |
| Process | On debugging the business rule, the activity was suspended with the following error: “Variable does not support null value.” |
| Transformation | The following error occurred when Advanced Zone Locator was used: “Fox-Exception: Index (127) out of range (0 – 126).” |
| Form | The global variable, “Job ID” was not set after it was used in an action and saved. When the action was reopened after being saved, the “Job_ID” global variable was replaced with the form control of the same name. |
| The carriage return (\r) and line feed (\n) characters did not work correctly in TotalAgility. |
Fix Pack 1
| Component | Issue |
|---|---|
| Form | When a form control was configured with the “Document type auto complete match type” option set to “Starts with match”, the items that were highlighted on the list of document types were not the same as displayed on the “Document Type” field. |
| Process | The connection string server variable was updated three times in a Data Access (DAS) activity even though the variable was not used as an output. |
| Quick Apps | When the resource group “Quick Apps Designer” was created and assigned “Full Control” access to Quick Apps, the users of this group were not able to use Quick Apps due to the following error: “Access denied” You do not have the required permissions.” |
| Coreworker | The settings that controlled the automatic clean-up of the “Generated Documents” folder were not available in the configuration file that supported backward compatibility. |
| Transformation Designer | In the Transformation Designer, when the settings were changed on a locator in the extraction group, the following error occurred: “Invalid URI: The host name could not be parsed.” |
| Form | When an Activity form was regenerated on a process that contained the input and output variables, the following error occurred “Index must be within the bounds of the list.” |
| Reporting | The “DeleteMachineDim” query, which was responsible for deleting machine dimension records as part of the reporting retention process, timed out. |
| Coreworker | The settings that controlled the automatic clean-up of the “Generated Documents” folder did not work in a TotalAgility Azure environment. |
| Form | An issue occurred when the search was performed within the dropdown lists contained in the Capture table cells of the Choice type field. |
| Conversion | In a Document conversion activity, certain documents failed while conversion, and the activity was suspended with an error. |
| Process | In a Document creation activity, all the fields were not detected when the document templates contained merged fields. |
| Transformation | For a project in the Transformation Server that had Online Learning enabled, an issue occurred with the Transformation Server Cloud Online Learning. |
| Package | When a package was created that contained the custom service, the web service data was not displayed on the Deployment configuration tab. |