Release Notes

Bug fixes:

• Disabled emitters are not displayed after an infrastructure restart.
• The form generation does not work properly with a data type containing an id with a space in it (require an external import).
• Service migration between versions may causes duplicated subinstances for cases.
• Pasting an iterator in a context result in an incorrect graphical rendering.
• Multi-instance output data mapping was not properly offering certain variables as collections.

Bug fixes:

• Under some rare conditions, an incorrect validation message about decision services could incorrectly be displayed when validating a decision model.
• Some process instances could not be accessed throught the case REST api.
• Method and style validation of Collect table could return an incorrect message.
• It was possible that sending email notification to performer would not work properly for complex inputs.
• CDS Cards feedback endpoint would return HTTP status 500 when the process or decision was not equiped to handle feedbacks.

Bug fixes:

• Using OIDC tokens with groups with the Digital Distributed Container could generated an exception preventing login.
• The incorrect data type could be created or updated when a context entry was of type list of type.
• Deleting unused data types with graph references had some preformance issues on a large number of references.

Bug fixes:

• Licenses for the Digital Enterprise Suite and Digital Distributed Containers set as environment variable could not be parsed if they contained a space character.
• Importing a Busines Knowledge Package (BKP) that was created using a previous version could introduce an empty folder in the Digital Enterprise Graph.
• HTTPS certificate errors were incorrectly serialized as events when executing service tasks.
• Connectors between criterion and Stage/Task are lost when importing older CMMN models from XML.
• Custom logos are not transfered from the operations in the connector panel.
• The feedback could fail when the model includes other models.

Bug fixes:

• OIDC user provider provisioning groups could fail logging in users.
• An exessive number of call could be issued to synchronize data types when validating, testing or deploying large models.

New and improved features:

• Testing case models is now possible in the Case Modeler.
• Places can now be synchronized with an external Git repository.
  • Git configuration for places is accessible from the administration interface of places.
  • A place can be imported from Git. This creates a new place that will automatically pull new changes from the source repository.
  • A place can be exported to Git. This push (force) all changes made to a place to an external repository.
• The connector panel now offers a Service Library tab that allows to drag and drop services that you have locally deployed.
• New FEEL functions from the upcoming DMN 1.7 specification were added: trim(), intersection(), years and month duration() and days and time duration().
• New custom FEEL functions are available to encode and decode files to and from base64.
• New custom FEEL functions are available to add or remove service instance tags.
• The default photo for users is now a circle with the user initials instead of being a gray human shape.
• Messages consumed from messaging systems are not queued anymore in the Digital Automatation Suite and will remain in the queue until they are processed.
• Messages consumer for Kafka, RabbitMQ, AWS SQS and Google PubSub now support multiple replicas.
• Identities can be edited to update their values.
• The details dialog of elements now allows to copy the identifier (id) of the element.
• The rich text editor now offers an option to clear all styling.
• When more than 10 pages are available, the ‘More Pages’ navigation between diagram will now always list all pages which now also contains a filter.
• When validating a model with invalid data associations, these validation messages are not displayed.
• Included data types were incorrectly copied when pasting an element that was also referring it.
• In some case, copying elements from an included model could introduce duplicated ids.

Bug fixes:

• The data store definition API was not accessible using a bearer token.
• B-FEEL incorrectly logged a warning for unresolved variables in some specific cases.
• DMN Validation does not properly report duplicated context entry name.
• Case models with repeated stages should consider each state and its inner task independently.
• Case models with operations triggered by case file events should respect other activation rules.
• Case automation did not properly trigger the “fault” onPart when a process ended with an error event.
• Case and Process instance names would not refresh properly in the form and Cloud Execution display.
• Sometimes description of the service isn’t the description of the main case or process.
• Unconnected sequence flow reports an error that does not link back to the element.
• DataStore shared with the ‘All Users’ group is not accessible at deploy/runtime.
• It was not possible to assign related element when creating a new issue.
• Clicking on a completed call activity would not open the model when viewing completed process instances.

Bug fixes:

• Date and time values in the Digital Enterprise Suite API could be incorrectly serialized under heavy load.

Bug fixes:

• Test cases execution could fail if they include an SDMN model.
• Adding a second column to a decision table inside an iterator return statement could fail.
• The user interface could malfunction when copying and pasting an iterator inside a BKM boxed function.

Bug fixes:

• Some already published case model could not be loaded anymore.
• Could not use an included Share Data Model data type as the return type of an iterator box context.

Bug fixes:

• We disabled the fix from v12.11.0 that was generating incorrect error and warning messages on certain model test and deployment.
• The option to package models when deploying was not working as expected for certain license configuration where the automation was not subscribed to.
• A blank page could be displayed when an iterator decision logic was in a context entry of a type containg spaces.
• There was no user feedback when trying to delete all unused data types.
• The wrong prefix could be used in the data mapping when including a Shared Data Model inside a workflow model.
• B-FEEL could incorrectly report error for missing variables that were present but had null values.
• It was not possible to test or deploy a decision model including a Shared Data Model that was using textual annotations.

New and improved features:

• It is now possible to create change requests between modeling places.
  • Can be used as an option when promoting a complete place.
  • Can be used to promote only a model and its local dependencies to a different place.
  • Change requests tracks a description of the changes and can be assigned to reviewers.
  • Reviewers of change request can validate each of the model changes before approving or declining the request.
  • A history of requests is kept.
• Service Library details of a service now displays the inputs and outputs name and descriptions of services.
• Modeled node tags and custom attributes are now returned on resume points.
• Digital Enterprise Graph dependencies are now considered when deleting unused types.
• The information dialog of the model now contains the path of the currently open model.
• It is now possible to redirect the web flow after the submission of a form (formURL) after starting a service or using a resume point.
• A name can now be provided for the data types when creating a Data Store from an Excel sheet.
• Added a configuration to toggle PKCE support for Authorization Code OAuth2 flow.

Bug fixes:

• Process containing lanes inside sub-process cannot be properly executed.
• Client Credential flow of OAuth2 now properly support generating tokens with scope.
• An exception could prevent the tasks from being displayed in the Digital Automation Suite application.
• Manual tasks name was not always properly returned in the tasks REST endpoint.
• Spaces before or after a text were not properly preserved when saving test cases.
• When creating a relation using a complex type, each complex sub-element were incorrectly expanded using the dot notation.
• When deploying a model, data types of transient models were not synchronized with their current version in the Digital Enterprise Graph.
• Exporting and Reimporting Business Knowledge Package containing a DMN Model with a reused Decision Service converted it to a Business Knowledge Model.
• Importing form API Guru is not working properly on certain browsers.
• A timeout race condition could prevent the startup of ideation sessions.
• A user event could block the auto-completion of a stage.
• Client Apps created a few years ago could not properly load at startup.
• Can’t rename boxed context entry when using iterator expressions with every and some.
• Email invites were not always sent from the Client Access License page of the Admin application.

Bug fixes:

• Including a Shared Data Model into the Decision Modeler would fail for certain models.
• SAML2 metadata signature certificates are trimmed of white spaces to prevent user error when creating them.
• The data mapping for case services calling a workflow process would not properly map the data in rare cases.
• The description of decision services was not properly exported to XML.

Bug fixes:

• Instance viewer report incorrectly a model not found error when viewing a workflow models using data stores.
• Expiration for client access license is not displayed in the administration interface.

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.