Resolved issues

2265711

Deleting records from Dynamic complex variables caused the process to fail with an error.

The Delete row action now removes the row as expected, and processing continues through the workflow without errors, reaching the End activity successfully.

2265689

In multi-tenant TotalAgility installations where tenant data resided in a single combined database, the code erroneously used the RepeatableRead isolation level for SQL reads rather than ReadCommitted. Because RepeatableRead held shared locks until the end of the transaction, this led to database blocking and query timeouts.

TotalAgility is updated to always apply the ReadCommitted transaction isolation level for SQL operations when no transaction is currently in progress, ensuring that shared locks are no longer held until the end of a transaction.

2265349, 2244995

When processing a low-quality page, the barcode locator in Transformation Designer failed to read the barcode and displayed an error message similar to the following:

The execution of a locator method failed. Class = "Invoice", Locator = "Barcode", Original error message: Could not perform recognition due to an internal OmniPage error: Barcode module error.

Barcode values could not be extracted from affected documents, causing processing failures and potentially resulting in suspended jobs.

Upgraded the OmniPage engine to 2025.1.5 (OmniPage DLL version 22.3.26329.1100), resolving the barcode recognition issue and improving processing of affected low-quality documents.

2264769, 2262081

2264553

After upgrading to 2026.3.x, jobs could fail with a Value cannot be null error when an Expression node updated a Data object field configured to allow null values.

This issue was commonly encountered in scenarios where jobs were created or updated through API calls using JSON payloads. Some Data object fields were intentionally configured with a default value of null, and the incoming JSON could contain either a valid value or null for those fields.

When an Expression node attempted to update a Data object containing fields with null values, the job could fail and become suspended. This behavior was observed in 2026.3.0 but did not occur in 2026.1.

2264540

In TotalAgility 2026.3, confidence levels were introduced for Auto Extract Locator (AEL) fields. The AEL prompt instructs the AI model to return one of the following confidence values: Very Low, Low, Medium, High, Very High, and Blank.

However, the model could intermittently return an unsupported value of "0" for FieldConfidence. This unexpected value caused extraction to fail with the following error:

Web service failure: error code=0x803d0013

The server returned a fault: External component has thrown an exception.

The same projects and documents were processed successfully in TotalAgility 2026.2.3, where confidence level handling was not implemented.

2264388

When a Boolean value was passed via a DB query activity and implicitly converted to a varchar parameter/column, the value True was corrupted on write and/or read actions.

All datatypes are now consistently serialized and Base64-encoded before being sent to the DAS repository, ensuring the repository's decode step always receives valid Base64 input.

2264305

In TotalAgility 2026.2.3, the Transformation Server's locking mechanism behaved differently than in 7.11 and reduced performance by 50%.

When the "Noisy neighbor" feature is not enabled, complete the Worker task before locking any activities.

2263984

A saved Workspace query name was rendered without encoding, allowing HTML/JavaScript entered as the query name to execute when displayed.

The code was updated to HTML-encode special characters (such as <, >, ", ', and &) when rendering saved Workspace query names. This prevents injected HTML/JavaScript from being executed in the browser, mitigating the stored Cross-Site Scripting (XSS) vulnerability.

2263895

2263464

Once the session timeout period had expired, any subsequent API calls would not reset the timers. This caused the session expiry warning to continue appearing even though the user was actively interacting with the application and API calls were still being made.

2263179

When a single row was added and populated, then selected and interpolated, TotalAgility inserted the first row again instead of continuing the table from the existing row, resulting in a duplicate entry.

CalculateBoundaries now excludes cells with -1 values, treating them the same as zero-valued cells (that is, cells with no selected words in the Image Viewer).

2263033

"IsTenantManagement" setting was missing in the TotalAgility configuration files, causing increased CPU utilization on the application servers.

IsTenantManagement setting is now included in Agility.Server.Core.WorkerService.exe.configuration file.

2263002

On upgrading to TotalAgility 2026.2.3, the Transformation Servers' throughput dropped significantly for systems having a single tenant.

When the "Noisy neighbor" feature is not enabled, complete the Worker task before locking any activities.

2262735

2262696

.NET Store DLLs did not work after the cloud upgrade to 2026.3.1. Jobs were getting suspended with the The system cannot find the file specified error while executing a script or method. The assembly failed to be resolved when a class was passed as an input parameter.

2262537

The internal API identifier that was used to hide the LicenseClient API section from the standard Swagger user interface, was exposed without authentication in a client-side JavaScript file, raising security concerns.

Internal API validation is now performed server-side; the client no longer has access to InternalAPIs_GUID."

2262514

Process debug failed with an error when debugging a business process that contains an RPA activity configured to run asynchronously.

The fix adds the same callback handler setup to the Process Debug execution path that already existed in the normal live execution path. When an RPA activity runs in Process Debug mode, the fix now:

• Creates the callback handler before calling the robot.

• Waits (blocks) for the robot to finish.

• Collects the robot's output values once it completes.

2262502

When Reporting service was running on a dedicated machine(with no Core Worker installed), an inactive entry was displayed in the Management Console.

Added a condition to exclude the Reporting Service machine name from being inserted into the Machine Names table.

2262081

Certain TotalAgility services/resources could be accessed without authentication and returned configuration information to unauthenticated users.

Authentication is now enforced, and unauthenticated requests no longer receive configuration details.

2261992

Adding only a variable or form control in the condition text, without completing the syntax, caused validation to fail with "Condition text is invalid" error.

Validation now provides a clearer, more specific error indicating the condition is incomplete.

2261656

For every Profile form request, no server-side ownership or authorization validation was performed. As a result, an authenticated user could substitute another user's RESOURCE_ID or RESOURCE_NAME and retrieve the associated resource.

Added a server-side authorization check in GetWorkerResource: verify the requested RESOURCE_ID matches the authenticated user's own resource ID, or that the caller has explicit permission (such as manager/admin role) to view that resource.values

2261649

When a user attempted to create a job and the operation was canceled because one or more documents contained validation errors, form validation did not function correctly afterward. After correcting an invalid field and pressing Enter, the field validation rules were not triggered, leaving the document in an invalid state.

2261451

2261236

The access-denied response revealed the name of the other user's private Work queue query.

GetActivitiesWithQuery2 access-denied responses no longer disclose the name of another user's private Work Queue query; a generic denial message is returned instead.

2261193

TotalAgility's differing login error messages ("Incorrect username or password" and "Account is locked") allowed unauthenticated users to determine whether a username exists. The inconsistent messages created a username enumeration vulnerability.

The authentication error handling was updated to mitigate the username enumeration vulnerability. The "Account is locked" message is now returned only when valid credentials are provided; for all other cases, including locked accounts with invalid credentials, the system consistently returns the generic "Incorrect username or password" error. As a result, an attacker can no longer confirm the existence of a valid username by observing a change in the error message.

2260967

The Document creation activity could generate a corrupt Microsoft Word document, causing downstream processing failures.

The activity incorrectly added a duplicate xml:space attribute to a table cell in the generated Word document, resulting in an invalid document structure.

The corrupt Word document caused subsequent Document conversion activities to fail, resulting in job suspension. Attempting to open the generated document in Microsoft Word also produced an error.

2260895

The On-Premise Multi-Tenant server called the OAuth token URL instead of the Integration Server, so requests never reached the intended business logic.

Endpoint routing has been corrected; the On-Premise Multi-Tenant server now calls the Integration Server as expected.

2260602

On upgrading TotalAgility, Data Access activity (DAS) parameters sent as plain text were corrupted in the custom database because the DAS repository always Base64-decoded all values, but only string types were encoded.

The fix ensures all data types are now serialized and Base64-encoded before transmission, preventing this issue.

2260249

In Tungsten Search and Matching Server 6.10, connecting to Microsoft SQL Server tables through an ODBC connection could result in the following error:

Unable to cast object of type 'System.DBNull' to type 'System.String'

This issue occurred when the table contained nullable columns with NULL values. The same data loaded successfully in version 6.9 but failed in version 6.10.

2259616

After upgrading to TotalAgility 2026.2.1.0.140, some jobs using the Generative AI activity were suspended with the following error:

The job has been suspended. Error performing automatic activity.

This issue occurred when the Generative AI response was mapped to a Data object variable. The error was not encountered when the response was mapped to a String variable.

A null value handling issue could occur when processing Generative AI responses mapped to Data object variables, causing the activity to fail and the job to be suspended.

Updated the Generative AI activity to handle the issue and prevent the Value cannot be null error when mapping responses to Data Object variables.

Workaround: Use a model with a higher token limit or reduce the size of the input content and prompt.

2259499

In TotalAgility 2026.2, the Due Date window occasionally displayed the activity due date as one day earlier.

For example, when the Activity Due Date was 07/28/2026 07:58:00, the Information window and LIVE_ACTIVITY.DUE_DATE both showed the correct date. However, the editable Due Date window displayed 07/27/2026 07:58:00.

The issue occurred because the due date was stored correctly in the database, but the due date dialog read the date object using UTC methods instead of local-time methods.

If the UTC in the original value was earlier than the user's time zone offset (for example, before 8:00 AM for UTC+8), the UTC date became the previous calendar day, causing the dialog to display one day earlier than expected.

2259328

The Image Conversion Error: 80004005 error occurred when exporting documents using the IBM FileNet Content Manager Export Connector under load.

The Export Connector encountered a transient CommunicationException while calling the WCF service; a temporary network disruption or a backend service processing issue may have caused it, resulting in the export process failing.

2259277

When a PDF generation or Document conversion activity failed and triggered the Automatic Activity Failed exception (EXP0038), the exception process was created with the NODEID populated, but the NODENAME field was left empty.

The issue occurred because the required properties were not copied when the job was suspended, resulting in the NODENAME value missing in the exception process.

Updated the implementation to use the correct copy of the JobActivityIdentity when suspending the job, ensuring that all required properties, including NODENAME, are correctly populated in the exception process.

2258322

2257936

Invoking an RTTS call against a newly added Dev environment (using the Production license) failed with the following error: "[8081] LicAct: Licensing has not been activated."81] LicAct: Licensing has not been activated.

A condition is added to retrieve the license deployment specific to the RTTS Azure tenant. With this change, RTTS correctly resolves the license when a DEV environment shares the Production license, and jobs no longer fail.

2257651

When an error occurred while executing an automatic activity, the job was intermittently suspended, and the activity was taken twice before the job was suspended. This caused unwanted behavior depending on the activity type. For example, when a Web Service activity exported a document to a backend system, the activity was expected to suspend on error, but the document was still exported, resulting in the document being exported twice.

Changed the activity cancellation logic so that a cancelled activity transitions to the Pending state instead of the Locked state.

2257499

When using the GPT-5.4 model, the following error occurred:

Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.

The max_tokens parameter is ignored when its value is 0 in the AI Provider configuration.

A new Use Legacy Max Tokens Syntax checkbox is added to the AI Provider configuration:

• When enabled (default), the max_tokens parameter is passed in the request.
• When not enabled, the new 'max_completion_tokens' parameter is passed.
• If the value is 0, none of the max_token parameters are passed to the request.

2256315

When a package was imported into an environment where a category with the same name but a different CATEGORY_ID already existed, associated items were correctly skipped. However, the .NET reference was still inserted into the REFERENCE table using the source CATEGORY_ID. This created an orphaned reference that was not visible in Advanced Studio, and any subsequent attempt to recreate the reference failed with the following error: "Reference path already exists."

.NET references whose associated category either conflicts by name (same name, different ID) or is missing in the target system are now skipped and reported during import, instead of being silently inserted with the source CATEGORY_ID. This prevents orphaned references and eliminates the "Reference path already exists" error.

2256090

In the Work Queue, the due date (Between) criteria automatically changed to “All” whenever metadata (filter) fields such as vendor, business unit, PO number, and more were edited. Saving the settings could affect other users/members.

It was expected that:

• The [due date] and [metadata] are retained as the last edited query within the session without refreshing the Workspace.
• The values are retained until the user navigates away from the query.
• Whilst still on the same query, even if you do not save but run the query, then go back or edit it, updates are retained.
• If you move to another query or move from the form entirely, only then should the query revert to the default saved settings.

2255553

The 'Resource Name' (work type) and 'Assigned To' (default) columns could not be selected together in a work queue query. Although the UI allowed the selection to be saved, it could not be persisted; reopening the query showed the last-selected column deselected.

Duplicate query columns are now removed, and System columns and custom columns are deduplicated separately. This allows a System column and a custom column with the same name to coexist in the query.

2255340

A branching rule without a valid condition represented an incomplete process configuration. When the process was executed at runtime, it failed with the "Object reference not set to an instance of an object" error.

A branching rule without a valid condition no longer causes an "Object reference not set to an instance of an object" error at runtime. The branch path is now always followed correctly.

2254670

A Capture Combo Box configured as Free Content and set to Read Only through a display rule could still be modified by users. Although the field appeared read-only, selecting the field and typing a character would overwrite the existing value. For example, if the field contained "Testing", entering a character would replace the entire value with that character, and each subsequent character entered would overwrite the previous one.

This issue did not occur when the Combo Box was configured as Restricted Content.

2254502

The field confirmation behavior during the Validation activity changed between TotalAgility 8.1.0 and 2026.2.

In TotalAgility 8.1.0 and 2026.1, selecting Complete Activity after editing a valid field allowed the activity to complete successfully without first pressing Enter.

In 2026.2.x, if a user edited a field but did not press Enter to confirm the change (the field continues to display the red indicator), then moved to another field and selected Complete Activity, the message "Please confirm all changed fields before continuing" was displayed, and the activity could not be completed.

The Complete Activity behavior in the Validation activity has been corrected.

2254393

"MaxSyncProcessingDurationInSeconds" was incorrectly listed under the "Web" tab in the Tungsten TotalAgility Configuration Utility Guide.

The "MaxSyncProcessingDurationInSeconds" is now removed from the Web tab of the guide.

2254352

When executing a REST web service call in TotalAgility, an HTTP 400 (Bad Request) response from the service caused the activity to suspend with a low-level .NET System.FormatException ("Index (zero based) must be greater than or equal to zero and less than the size of the argument list"), rather than a clear, actionable error message. This was due to malformed error message construction in TotalAgility's error handling logic.

Updated the error handling logic in TotalAgility's REST web service activity to ensure that, when an HTTP 400 (or any 4xx/5xx) response is received, the activity suspends with a clear, actionable error message.

2253849

When the web service returned an HTTP 400 response, TotalAgility could not handle the error response gracefully and surfaced a meaningful error (the HTTP status code and response body) instead of suspending the activity with an unrelated format exception.

The save logic is updated so that when a job activity filter is saved, the Job ID is now included in the filter criteria.

2253561

In a Firefox, branching rule validation failed with the following error: "The evaluation of this rule will not result in a true or false outcome." when validating the second path of a branch whose process/business rule name contains spaces.

Zero-width space characters (\u200B) inserted by Firefox are now replaced with empty strings to prevent validation issues.

2253414

The DAS (Oracle) activity configuration was displayed as empty on upgrading from 7.10 to 8.1, to 2026.1, and finally to 2026.2.

The DAS configuration was displayed in 2026.1; however, it did not load in 2026.2.

When the connection string was configured using a server variable, the connection string value could not be fetched, and the isOracledb flag was not set correctly.

2253411

If a Work queue filter was consumed when using “Complete and Take Next” in an activity form, the next taken activity was not as expected. The TakeNextActivity2 action had the WORKQUEUE_FILTER (global variable) configured in the UseFilterData parameter.

The filter field data is saved in the WORKQUEUE_FILTER session variable, correctly showing the next “taken” activity.

2253147

Jobs were suspended at Extraction with the following error: " The process cannot access the file because it is being used by another process." error.

There was an issue closing the FoX/RecogOmniPage/PageRecognizer.cpp file in the OmniPage engine.

FoX/RecogOmniPage/PageRecognizer.cpp is properly closed.

2252761

The username with a space difference caused an item with the same key has already been added error. The same person appeared twice in the reports with split activity data.

The behavior has been fixed.

2252646

The EML to PDF conversion failed when the source EML file contained a PDF portfolio attachment.

Added support for Unix/Linux-style LF (\n) line endings, enabling correct parsing of files created in non-Windows environments without manual conversion.

2252646, 2234189

The EML to PDF conversion failed when the source EML file contained a PDF portfolio attachment.

Added support for Unix/Linux-style LF (\n) line endings, enabling correct parsing of files created in non-Windows environments without manual conversion.

2252495

The SESSION_NOT_VALID message appeared when a popup was used in the custom validation form.

The issue did not occur when opening a redirect form.

The form opens without any issues.

2252301

A DB query configured on a “Device scan create new job” form failed when accessing the form through the MFP Emulator.

For example, the form contained a DB query action configured to populate FIELD2 based on a value in FIELD1. When the user entered a value into FIELD1 and moved focus away from the field, the MFP Emulator displayed the "Forms Server error occurred. Contact your administrator" error with System.MissingMethodException.

This error occurred because the first FormEvent found was selected from either Text Changed or Field Validate events, rather than the first active FormEvent of the correct type, which sometimes executed an incorrect or non-existent generated event method, resulting in MissingMethodException.

The field event is changed from Text Change to Field Validate.

2252143

When exporting table fields using the XML Export Connector, the configured Table field export delimiter did not appear to take effect. The source document contained table rows where the material field includes semicolons. For example: Row 1 material = 1a;1b;1c;1d;1e, Row 2 material = 2a;2b;2c;2d;2e, and Row 3 material = 3a;3b;3c;3d;3e

As a result, the XML Export Connector did not preserve these values in the XML output and split/truncated them during export.

The Row Separator is set to match the delimiter used to split table field values in the Document type configuration, so the export connector can correctly read multi-value table fields via the Row Separator.

2252138

When a form was opened from a Document review activity using a Redirect action configured to display the target form in a popup window, closing the popup caused the main Image Viewer region to become hidden. The document navigator and thumbnail panel remained visible, but the Image Viewer/document preview area appeared blank until the page was refreshed.

The region pane swapping logic has been corrected so that the Image Viewer region's visibility state is properly restored whenever a pane swap completes - including when a popup form closes and focus returns to the main review page.

2251926

Enabling the Async option on the Tungsten AI Provider caused the error Unable to find Variable 'xxxxxxxx' mapped to an activity at runtime, because the Data Object variable mapped to the Generative AI node's response was blank.

The Data Object variable mapped to the Generative AI node response populates successfully at runtime regardless of the Async option being enabled and disabled.

2251558

Workspace queries did not offer operators for metadata fields of type String, making it impossible to build filter conditions (e.g., equals, contains) against those fields.

The standard string filter operators (=, !=, contains and more) are now available for the field.

2251523

In TotalAgility Workspace, the query did not display the Greater Than, Greater Than or Equal, Less Than, or Less Than or Equal operators when configuring filters against string job variables.

The same operators remained available in TotalAgility Advanced Studio for identical string fields, and queries created in Advanced Studio executed successfully in Workspace.

All the operators are added to metadata and filter fields.

2251444

Classification now completes successfully using the available OCR data.

2250474

The condition is now validated successfully.

2250392

When a Data access (DAS) activity attempts to populate a data model date with `NULL`, the following error occurred: "Variable "RECORDSDM_527C1260EE70E9CD5B01C29FAEB6E1D5" is declared as Date in the process map "Records" and cannot accept an empty value."

For fields mapped to Data Object fields, the corresponding field IDs are now passed and their values are set to NULL.

2250301

In the Verification activity, the field did not become valid after changing its value without confirming (pressing Enter).

Undoing changes still made the field dirty and marked it with an error message.

Undoing changes returns the existing status.

2250300

An error occurred when 2250301logging into the Tenant Management System on upgrading TotalAgility from version 2026.1 to 2026.2.

Exception handling was added to the retrieval logic, and the capture storage type is now retrieved using the latest deployment host URL instead of the live host URL, ensuring the correct storage configuration is resolved.

2250224

When a Workspace session expired due to inactivity, the browser's HTML5 sessionStorage was not cleared, and values such as RESOURCE_NAME, RESOURCE_ID, and SESSION_ID remained present after the user was redirected to the login page.

The session-end logic is updated to remove RESOURCE_NAME from sessionStorage upon timeout.

2249981

In TotalAgility 2026.2, a document validation form threw the following error message:

Your session is not valid or has expired. If performing an activity, you can log out and log back in to retake the activity from the work queue, or you can reset the activities taken. If creating a new job, you need to start again.

This error occurred because the previous error was ignored at the activity form level.

The error is shown for the correct activity.

2249580

The issue has been fixed and the upload is successful.

2249529

The GetResources2 API documentation was missing information indicating that Resource ACL permissions are required to execute the API.

Updated the API documentation.

2249507

When a separator profile was configured in the Classification activity, the Classification Group script caused incorrect barcode-based separation.

When merging barcodes, only required barcodes from the existing set are included.

2249018

When Replay Protection was enabled in TotalAgility, Transformation Designer threw an "Access Denied" error when trying to log in.

When this is disabled, the user could log in successfully to Transformation Designer.

When Replay Protection is enabled with TotalAgility authentication, the Access denied error does not occur when logging in from Transformation Designer

2248806

When generating a PDF using a PDF generation activity, the FoX exception number 8 error appeared.

Key-value pairs with invalid word references are removed.

2247721

In extraction group tables with a "Require manual field confirmation" column, existing rows were incorrectly marked as valid (green) when a new row was added even though their cells were never confirmed via Enter. This bypassed the manual confirmation requirement.

For newly added cells, the IsConfirmedManually field flags are updated based on the RequireManualFieldConfirmation definition flags when values are changed before validation. UI synchronization between IsConfirmedManually and RequireManualFieldConfirmation allows validation to be processed correctly.

2247638

2247635

2247060

Exporting a workflow from TotalAgility Studio failed when the workflow title contained certain Japanese characters. Instead of the workflow package, an error.txt file was downloaded with the message "Specified value has invalid control characters. Parameter name: value."

The workflow is now exported successfully and the generated ZIP file retains the original Japanese workflow title.

2247055

2246976

When jobEvaluation failed, the corresponding task remained in the Worker task table. Subsequently, when a terminateJob task was added with the same job ID, a primary key constraint violation occurred.

An updateStatus parameter is added to CompleteWorkerTask() so that when a stale EvaluateJobTask is deleted to make way for a new TerminateJobTask, the in-memory status is not set to Completed. This ensures the re-inserted task is stored with Active status and is picked up by the worker to complete the job termination.

2246405

The document conversion profile was unexpectedly removed from the Document Conversion node in a business workflow, causing job failures.

The deletion logic is updated to first check the process and activity tables for references to the document conversion profile. If the profile is found to be in use by any process or activity, deletion is skipped, preventing the profile from being removed while still in use.

2245735

Visibility of process maps, categories, resources, and work types within the “Edit Query” interface of Work queues and Job lists is restricted. This ensures that:

• Users only see artifacts associated with their roles or permissions.
• Unrelated process elements are hidden from the query editor altogether.
• The query-building experience remains scoped to the user’s functional perimeter.

2244220

In TotalAgility 8.1.0, when navigating between documents in a Validation activity, the previously viewed document remained in the Viewer until the next document was completely rendered.

This resulted in a brief visual effect where the previous document appears just before the new document is displayed.

Image Viewer displays the exact document that has been selected on the Navigator panel (or Thumbnails panel).

2238714

When a Complex variable activity was used to add a row to a Capture table, the operation intermittently failed with the error: "Could not find file 'c:\windows\system32\inetsrv\-304.98'."

The Complex variable activity now obtains the column type from the table and updates the variable's type accordingly, preventing type mismatches when adding rows to capture tables.

2213639

On upgrading to TotalAgility 8.1.0.10, exports to SharePoint failed with the following error:

“Could not load file or assembly Microsoft.IdentityModel.Abstractions”

A similar issue occurred when loading the SharePoint export connector in the Export user interface.

Agility.Server.Core.ExportWorker.Host.exe.config has been updated to include a dependentAssembly entry for Microsoft.IdentityModel.Abstractions. After installation, the configuration is included by default.

2203379

On upgrading TotalAgility, the export connector failed with the "Unable to load UI" error.

Validated the specified bindingRedirect for log4net in the application configuration files.