Digital Enterprise Suite

Bug fixes:

• The Digital Distributed Container base image now contains additional utility libraries.

Bug fixes:

• An incorrect validation error could be reported for output decision tables columns defined using an included data type.
• The option to allow null on decision tables input and output columns was not always visible.

Bug fixes:

• It was not possible to edit a decision table cell when defined in a column that was typed as a complex structure.

Bug fixes:

• When validating a model with open range numeric constraint, the validation was failing.
• The responsiveness of the Settings interface was improved for a small range of screen width.
• Certain plugins installed on Safari could cause an error when exporting a Word report.
• There was an error when trying to export a diagram to an image if it had a newline character in its name.
• The OpenAPI import in the Operation Library now properly consider the enumeration of number extension (x-enum).

New and improved features:

• Improved the data type validation
  • It is now possible to enter multiple constraints on a data type. Additional constraints are FEEL expressions.
  • A user-provided validation failure message and code can be entered for each constraint.
  • A new convenience Not Null constraint has been added to restrict null values from being considered a valid value.
  • The Simple constraint type was renamed to Range.
  • When entering an expression constraint, FEEL code completion is now available.
  • Expression constraints now fully support the question mark (?) explicit value identifier for unary tests.
  • Expression constraints for structures can now reference their sibling fields (an improvement coming to DMN 1.5).
  • When deploying a service, a new option now allows to define the validation level for the service: None (backward compatible), External data entry (validate data types when new data is sent to the service), Always (validate data types every time data is generated).
  • It is possible to set the validation level for the test functionality in the preferences (File -> Preferences). We strongly suggest to change this value to always for testing.
  • The service REST API for service deployed with a validation level different from None could now return validation errors (HTTP 400).
  • Enumeration type constraint is not offered anymore for boolean data types.
• It is now possible to change the identities and server URL (override service descriptors) used by services once they have been deployed.
  • When promoting a service in the Service Library that defines an interface to an external system, the promotion dialog now allows to override the security information defined in the model.
  • Using a Digital Distributed Container (Single or Multi Service), it is now possible to override the service descriptors to update the security information used by the service(s). See the Digital Distributed Container Help for more information.
• The Service Library detail dialog now has a direct link to the running instances of a service when applicable.
• The default mapping (when no mapping expression is provided) is now displayed in the data mapping dialog.
• A new dialog now allows to edit conditions for outgoing sequence flows (Conditions in the contextual menu).
• The process animator now animates loops.
• A warning is added when a boxed context entry name collides with an existing name in the context (override a function for instance).
• A new custom FEEL function is available under the Automation library to retrieve user task assignation information: automation.task assignees(name).
• A new custom FEEL function is available under the Automation library to retrieve the current instance information for long running services: automation.instance info().
• Improved our locking mechanism for long-running service instances using the file system persistence.
• A new visual spinning icon next to the model name indicates that the Digital Enteprise Graph is synchronizing.
• The number of calls required to synchronize the elements reused in a discovery accelerator model was significantly reduced.

Bug fixes:

• When testing a business knowledge model (BKM) with multiple inputs, in some cases the parameters were not sent in the proper order.
• Invoking a decision service through a boxed context invocation defined in a model that contains multiple consecutive spaces in its name does not work as intended.
• For case automation, the email sent to the performer of a task could contain an invalid URL to perform the task.
• The Public API for endpoint for building containers was not accepting bearer tokens with the Execution Environment Download claim.
• When an element linked using a Copy Of link source was deleted, the lock icon was not immediately became red.
• Text can now be selected in the FEEL function help dialogs.
• The dialog for the details of a linked term is displayed under the rich text editor toolbar preventing it from completely being visible.
• The test and publish buttons became temporarily disabled when creating a blank page.
• An incorrect error message was shown when adding a date or a date and time enumeration constraint.
• Validation errors are now displayed when testing a model.
• Markers were lost on the diagram when switching between a decision logic and a diagram while testing
• The play button on attachment in the Decision Modeler was not visible.
• Dynamically generated decision services did not properly validate the direction of links.
• DMN XML import did not properly import the definition of terms.
• The XSD data type gYear is now imported as a text because it can also contain a timezone.
• When automating a case, the on part of was not always properly considered when multiple entry criterions were present.
• Updating data to null while testing could keep the old value.
• A decision table with a column using a numeric enumeration will not add double quote around numbers when selecting them from the suggestion.
• Submitting a form using a numeric enumeration with an empty value would submit 0 instead of null

Non-Backward Compatible Changes:

• The OpenAPI data type definition for an enumeration will not be nullable by default anymore. The data type can be modified to check allow null on the enumeration to explicitly make it nullable again.
• For clients not deploying in a container, this release requires the Java 17 JRE.

Bug fixes:

• Fixed an additional potential issue where 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.
• The form interface to resume a process instance in error could incorrectly return an error that the instance was not found.
• Optimized working with large boxed contexts.
• When importing an XSD from the data types dialog, the Gregorian XSD types were not imported (gDay, gMonth and gYear).
• When requesting to select a shape in the modeler, if that shape was on another page, it was not always selected properly.

Bug fixes:

• The custom FEEL functions were not always packaged in Digital Distributed Containers.
• The simple FEEL data types type names are not properly rendered in reports.
• Copy of and semantic links could be marked as missing when references came from different graphs.

Bug fixes:

• A fix in version 11.3.2 to the XSD import introduced a non-desired side effect of renaming the virtual attribute to hold the element text when facing a mixed of text and attributes. That side effect was reverted.
• Testing results of decision tables inside boxed context are now properly highlighted.
• The testing result of a decision table is now displayed with the information icon.
• It was possible that a model would refuse to load if the requirement panel was open.
• Sources URI should be clickable in the report.
• Switching to/from FEEL unparsed could cause a DMN 1.2 export to use the wrong FEEL XML namespace.
• In rare cases, the debug raw outputs event for ServiceNodeFinished of a boxed context containing a decision .
• The number of output headers that will be automatically created when creating a new decision table has been increased from 5 to 15.

Bug fixes:

• A concurrency problem that could cause dependent asynchronous events to be executed in parallel could cause a process instance serialization corruption using the filesystem persistence.
• Importing test cases that did not define the TCK name attribute would cause a rendering issue in the test case panel and the test case selection for testing.
• The ability to use rich text when doing the data mapping was not always offered and prevented the data mapping tab from properly expanding.

Bug fixes:

• For digital distributed containers mounting a persistent volume on /data/des/pinstances, there was a possibility that it prevented active triggers from being registered properly.
• When synchronizing a large number of elements from the Digital Enterprise Graph, the modeler user interface could become unresponsive for a period of time.
• Improved the documentation of the any() and all() FEEL functions as well as their non-null equivalents.

Bug fixes:

• Importing the same XSD for the second time could break local data types referencing the types in the XSD.
• Optimized the performance when deleting a large number of data types.
• The FEEL Quick Guide panel should be restored after testing a decision table page.
• Data Mapping for workflow and cases could incorrectly be made read-only by a preference of the Decision Modeler to view the decision logic in standard mode.
• An issue affecting a small number of services could cause unexpected 500 HTTP responses on a REST service call under heavy load.
• Fixed a few typos in the BPMN Quick Guide.
• The include dialog for CQL, PMML, DMN and Custom FEEL functions incorrectly had up/down mouse arrows to reorder them.

Bug fixes:

• The preferences were not properly transfered to Digital Distributed Containers resulting in some containers not being licensed properly.

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.

Bug fixes:

• Fixed a rare condition that could cause a timer trigger to be unregistered before being registered causing other triggers of the process to be removed as well.
• In the workflow modeler, when saving your models under certain conditions, relative digital enterprise graphs to process, decision or case could be made absolute.

Bug fixes:

• For clients not subscribing to the Trisotech Automation Suite, models will not be upgraded to use custom FEEL functions anymore.
• The DMN XML export had the wrong value serialized in the name attribute of a custom FEEL function library import element.
• The non-null functions (ex: nn count(), nn sum(), …) are still recognized properly by the FEEL highlighter.
• A digital enterprise graph semantic link was incorrectly added on top of a reuse link for BPMN call activities.
• The authorization header of the Digital Distributed Container base image can now be properly resetted from the admin interface when left empty.

Bug fixes:

• An initialization issue could rarelly prevent a decision model from properly loading in the Decision Modeler.