Release Notes

Bug fixes:

• CMMN Execution claim can’t be checked when creating or updating a Client App.
• Range and list data types could be incorrectly rendered when used as a data output of a user task.
• Protected data should not protect null values.
• The group claim of OIDC token can now be prefixed with the Trisotech namespace for the Digital Distributed Container.

Bug fixes:

• An error can occurs with the data policy checks of collection types preventing their proper automation.
• Boundary event inside event subprocess could not always be properly triggered.
• Inline types could be incorrectly referenced by the data type validation.
• Special characters in field name could confuse the parser in filters of filters.
• Error events could not be used as start of Event Sub-Process.

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.

Bug fixes:

• From the settings application, when creating a new identity of type OAuth2, changing the flow type hide the additional fields.
• Modeling a recursive data type at the first level prevented the deployment of service.
• A workflow model in BPMN containing an invalid data association serialized at the wrong level would prevent the model import.
• An expression could get corrupted when clearing an existing expression and then adding an iterator expression.
• Some operations cannot be dropped from the connector panel when other operations from the same interface exist.

Bug fixes:

• Decision table inside BKMs were not exporting the output type.
• The information markers on the diagram that are displayed when testing only display the last output if there are multiple outputs.
• Transforming a literal expression to an iterator/conditional/filter could introduce a duplicated identifier.
• The usage of B-FEEL could cause a compilation problem with some type of decision logic in data mapping.
• The left side panel of the admin application did not properly scroll vertically.

Bug fixes:

• Opening a Decision model while testing a Workflow model could not show the model properly sometimes.
• Additional warnings could be incorrectly reported for an filter expression inside a for expression.
• One time password by email identity provider did not properly allow to make access requests.
• Publishing a Digital Distributed Container from the Service Library did not properly support Managed Identities.

Bug fixes:

• User invitations emails are not being sent when inviting new users from the Client Access License administration page.
• The gateway conditions dialog does not open properly.

Bug fixes:

• Group members could not be deleted from the administrator interface.
• Digital Enterprise Graph synchronization could introduce invalid type on context entry used for mapping.
• Type displayed in an invocation row created from a BKM parameter were not correct when using a list of custom type.

Bug fixes:

• Additional warnings could be incorrectly reported for an filter expression referencing the item variable when the item value was null.
• Version 12.9.2 introduced a security patch that inadvertently prevented the deployment of more than 10 models at once.

Bug fixes:

• Improve the handling of external file on process completion to be fault more fault tolerant.

Bug fixes:

• A warning could be incorrectly reported for an filter expression referencing the item variable when the item value was null.
• Some license types would cause an error message at Digital Distributed Containers startup.
• Data inputs in a pool could be duplicated when moved across lanes.

Bug fixes:

• When moving a call activity between lanes it could remove the data associations.
• A warning could be incorrectly reported for an filter expression referencing the item variable.

New and improved features:

• The place navigator now allows to resize its columns.
• It is now possible to export as a transport zip file, a model with all its dependencies from the place navigator.
• It is now possible to import from a transport zip file, a model with all its dependencies from the place navigator.
• A new library of custom FEEL functions to manipulate unstructured documents (PDF, Word) was added.
• A new Orientation Onboarding eLearning is available to modeling users.
• A new Orientation Onboarding eLearning is available to socialization users.
• A new event connector for connecting to incoming emails using IMAP is now available.
• A one-time password by email user provider authentication method was added.
• Administrators can now contribute new connectors.
• Administrators can now hide provided connectors from modelers.
• The Public API of the Digital Enterprise Suite is now available as a connector.
• A new message correlation is available for start events to prevent starting a new process instance based on a tag already existing.
• Simplified the configuration of subtopics for Digital Enterprise Suite events bindings.
• The connector panel operations are now grouped by tags.
• When submitting feedback with multiple files, they are zipped together in the resulting feedback message.
• Duplicated data types could be introduced by reusing an element related to an included type with the same name.
• Process using data stores could not be used in cases automation.
• A model containing a business knowledge model with an iterator of type some or every could not be imported properly.

Bug fixes:

• Enumeration could be duplicated when saving Case models.
• It was not possible to properly use multi-instances send tasks.
• Indexing a case modeler file with a data type could lead to an error preventing its indexation.
• Timer expression for months and years durations caused an error at runtime.
• Errors in FEEL filter expressions were not properly reported to the user.
• Cases manual activated task with event listener could not be triggered.
• EPIC EHR does not perfectly align its payloads with the CDS Hook card feedback specification. We now support their slightly off specification format.
• When using special characters in the name of a data object or a case file item, a FEEL expression referencing them could fail. Note that it will not fix existing models and will require slightly adjusting your FEEL expression logic.
• Cloning a place with public access could result in an incorrect error message.
• Renaming an output data association could create an additional one.
• Renaming an inner data input did not propagate the new name to all possible reuse.
• Timers could only be triggered once in the case animator.

Deprecation notice:

• Trisotech Accounts will be removed as an Authentication Method for user provider. Starting with the next release, this will not be a configuration offered anymore. To prepare for that change, administrators using Trisotech Accounts to connect will be contacted in the next few weeks to schedule a migration to the new one-time password provider.

Bug fixes:

• Avoid sending duplicate authorization header if you have overloaded it locally in your data mapping.
• There were some problems with deleting and sharing identities in the settings page.
• Morphing a complex item definition to a simple one did not work.
• Connectors layout changed sometimes when exporting the Diagram to an image for some models.
• IfPart context was not populated correctly when an exit criterion was attached to the case plan boundary.

Bug fixes:

• Could not obtain the JSON template from a resume point.
• The reported error for throw events not bound to an actual implementation did not properly point to the node in error.
• The relinking of a dependency could cause a duplication of data type.
• Events from the connector panel could not be dropped in expanded sub-processes.
• It was not possible to enter complex expression for data type constraints when accessing the constraint from the canvas.
• Prevent data types to be unnamed.
• When renaming a test case, its name does not refresh in the side panel.

Bug fixes:

• Security fixes.