Digital Enterprise Suite – Release Notes – August 18th 2025

New and improved features:

• New Data Policies.
  • When modeling a data type, the data type himself or one of its components can be protected.
  • Protected data types are displayed using the shield icon in the data type dialog and in the Shared Data Modeler.
  • Protected data will not be sent to untrusted endpoints.
  • The administrator application has a new panel to configure Trusted Endpoints that are allowed to receive protected data.
  • Client Apps can also be marked as trusted in the administrator panel to allow the access to protected data.
• Unstructured Documents Management (PDF, Word, Excel, PowerPoint).
  • Places can now store unstructured documents.
  • Unstructured documents can be dragged from the Digital Enterprise Graph into diagrams as Knowledge Sources.
  • Attaching an unstructured document to a user task makes it available to the task user interface.
  • Unstructured documents are packaged as part of Business Knowledge Packages.
• Decision and Workflow services deployed in the Service Library can now be exposed as a tool to AI Agents using the Model Context Protocol (MCP).
• The performer of a user task can now be an AI Agent. The administrator can configure agents from Microsoft Azure AI or OpenAI Assistants and make them available as performers.
• Support for the OAuth2 Client Credentials flow for obtaining API tokens through Client App.
• It is now possible to create Client Access Licenses that are service accounts.
• The Digital Automation Suite now supports the Open Telemetry standard.
• When using the one-time password user provider, users are now prompted to enter their names on their first login.
• Added native support for Amazon SQS and Google PubSub in connectors and as emitters.
• The term auto-linking can now be used in the Knowledge Entity Modeler.
• The term auto-linking can now be scoped on element names only.
• When entering a value for an enumerated type, offer suggestion based on the enumeration.
• OIDC user provider now supports PKCE with client secret.
• The client hosted deployment documentation for both the Digital Enterprise Suite and the Digital Distributed Container was integrated with the Trisotech Helm and greatly improved.
• New logging configuration is available for both the Digital Enterprise Suite and the Digital Distributed Container to output logs in JSON format.
• Added an headless (no User Interface) deployment option to the Digital Distributed Containers.

Bug fixes:

• A decision model with a single input bound to a data store would not always get populated properly at runtime.
• The OIDC provider of user accounts did not always generate a Client Access License on successful login.
• Timer in case models event listener did not work with expressions.
• Only the first data association was available in the output mapping of rule task.
• The public api now trims email addresses in the different endpoints to prevent matching errors.
• Disabled emitters are not shown in the Settings application.
• After loading a test case, the data validation messages were not displayed in the form panel.
• The validation of a decision model would fail if it included a shared data model.
• Variables were not recognized in the expressions for escalation events.
• Clicking on a simple data type from the diagram did not open its constraints properly.
• Importing data types from a DMN 1.6 model could cause an invalid XML export.
• Switching from B-FEEL to FEEL as the expression language could cause the conditional expression of data mapping to stop properly compiling.
• Large context test results were not displayed.

Deprecation notice:

• The Digital Enterprise Suite will no longer use the gravatar public service to user image.
• The link to the introduction of the Method and Style courses were removed.

Security issues:

• It was possible to make certain interaction with workflow, case and decision models using the REST API through a Client Application that did not have the appropriate (BPMN/CMMN/DMNN) execution claims. If you had not selected the automation execution claims for your application, you will need to do that before being able to make calls.