Digital Enterprise Suite

Digital Enterprise Suite – Release Notes – November 6th, 2022

Title Shadow
New and improved features:
  • The Digital Distributed Containers family was expanded to also now allow to build containers with multiple services.
    • The existing Digital Distributed Container was migrated into what is now called Single Service Container.
    • Introduced Multi Service Container that allows to push containers that contain multiple services to a container registry from the Service Library.
    • The Single Service Container was enhanced to allow to push containers to an external container registry.
    • The admnistrator can now control if Single Service Containers are built for each execution environment and their destination (local or external registry).
    • Note that separate subscriptions are required for Single Service Container and Multi Service Container. Clients that purchased the Digital Distributed Container will be migrated to Single Service Container on renewal.
  • A new automation service storage for long-running services (workflows and cases) based on MongoDB persistence can now be used in the Digital Automation Suite and in Digital Distributed Containers.
  • An administrator can now create execution environments that do not register active triggers (Kafka, RabbitMQ, …) when deploying a service. These services can still be built into containers and deployed with active triggers.
  • In the Form interface to services, BPMN signals accessible in the context of the current task are now presented as user actions that can be triggered from the user interface.
  • When testing a decision model, it is now possible to scope the test to a given decision service, decision or business knowledge model.
  • Flags are now displayed in the terms view.
  • The test button is not disabled anymore when the workflow process is not marked as executable. It is now possible to make it executable from a new dialog.
  • When validating an executable process with the validate button in the BPMN ribbon, it will also be validated for attriubtes required by the Trisotech Automation Suite.
  • A data type that has an attributed named instance will not generate a warning anymore.
  • It is now possible to iterate over a range of dates in FEEL. This is an upcoming feature of DMN 1.5.
  • The Trisotech Help now contains the documentation of the Administrator inferface.
Bug fixes:
  • When submitting an XML file to the automation engine, there was a condition that could cause an element defined with a collection data type to be parsed as an element instead of a single element in a collection.
  • It was possible for scopes to not be sent properly when refreshing an OAuth token if the token URL did not echo back the scopes originally in the response.
  • Links inserted into the rich text editor (description/notes) could fail to open in the Kommunicator because of iframe domain restrictions.
  • Adding a second source to a term could result in an error.
  • When editing the type of a case file item with the data type overlay on, the data type Any would appear in error on the overlay until a refresh.
  • Empty example and notes are not displayed anymore in the term view.
  • Labels were not always displayed on connectors.
  • Some elements were not properly alphabetically sorted in the graph scope.
  • An error could be incorrectly displayed when creating a new model and saving a previous one.
  • Optimized the loading type of the Data Type dialog when hundreds of data types were present in the model.
  • Optimized the number of graph queries required to sync data types.
  • When importing Open API in the Operation library of a modeler, item definitions name were created with their title instead of their name which causes referencing problems.
  • When importing Open API in the Operation library of a modeler, simple types definition could incorrectly create circular data types.
  • The description field of connectors and annotations were not properly exported to CMMN XML.
  • Some decision logic pages were not properly made read-only and returned to editable when testing a decision model.
  • Links in comments were rendered smaller then intended.
  • Message flows were incorrectly highlighted in blue in the animator.
  • Suggestion did not show up in decision table, list and relation columns with a boolean or enumeration data type.
  • In rare cases, the DMN XML export of a decision model could contain an import twice. This caused an issue with automating these models.
  • Some errors were not properly reported to the user on a failed deployment to the automation.
  • When using the dot (.) operator after a filter in a literal expression, null values were incorrectly filtered out of the result.
  • When testing or automating an invocation that was calling a function with an undefined prefix, it could cause a non descript exception. The error is now clear.
  • When reloading the Discovery Accelerator with an opened model sometimes all graph links are marked as missing.
Non-Backward Compatible Changes:
  • The monitoring and health checks REST operations were removed from the main HTTP port (8181) and moved to a dedicated port (9080 inside the container). These operations are no longer protected by a basic authorization on the new port and port 9080 should not be exposed publicly. Clients hosting the Digital Enterprise Suite that previously used port 8181 with a basic authorization to access the health check functionality will need to update to port 9080 without authorization.

Learn how it works

Request Demo

Confirm your budget

Request Pricing

Discuss your project

Request Meeting