Release Notes

• Security fix Long Term Support release.

Bug fixes:

• Execution environment created before version 11.3.0 (November 2022) have their triggers disabled.
• Setting a Frame Ancestors domain in the administration application could cause certain Trisotech functionalities of the Kommunicator and the Digital Automation Suite to not work as expected.
• Accessing a variable property after a closing parenthesis was being recognized as a string.
• Sorting a collection with a filter expression would cause the data type information of the collection to be lost.

New and improved features:

• New modeling product: Shared Data Modeler.
  • Based on the OMG Shared Data Model and Notation (SDMN) 1.0 specification.
  • Visualize data items and data types in diagrams.
  • Fully integrated with the Digital Enterprise Graph and other standard capabilities of the Digital Modeling Suite.
  • Exchange SDMN models using the XML import and export.
• Data types display properties can now be customized to alter how they interact with users when used as either data inputs or outputs.
  • Customize the default value when inputting or outputting.
  • Select the control type (single text line, multi-text line, drop-down, radio button, …)
  • Define the Custom Renderer name used for a data type.
  • The different interaction channels (form, email, teams) do not support all customization. Refer to the documentation to know which customization works with which channel.
• It is now possible to administer and visualize a workflow process instance visually (overlaid over the process diagram) from the Execution Instances interface.
• A new admin interface is available to upload Custom FEEL functions written in Java by developers.
• The product navigation menu (nine-tiles) is now segmented into Modeling, Automation, Administration and Documentation categories.
• The Digital Enterprise Suite application tile was rebranded Digital Modeling Suite.
• A new user facing application called Digital Automation Suite is now available from the tile menu.
  • Exposes services available to be started.
  • Exposes tasks that need to be completed for long-running services.
  • Now the default application when accessing a Digital Distributed Container through the web interface.
• Forms now display the description of the required inputs.
• The authorization model of execution environment was improved to now be defined as:
  • Performer: A user can execute services from this environment such as starting instances, performing tasks, etc.
  • Deployer: A user can deploy and delete services from this environment.
  • Builder: A user is allowed to download an offline version of this service (in a container for instance) or build a container image of the service.
  • Admin: A user can manage long running instances of services in this environment.
• It is now possible to create new models from the Place Navigator.
• The interfaces and operations from the Operation Library are now indexed in the Digital Enterprise Graph.
• OpenID Connect (OIDC) is now supported as a user provider.
• Digital Distributed Containers are now secured by default.
  • A new Client App is automatically created for each execution environment.
  • The Digital Distributed Container are now connecting back to the Digital Enterprise Suite using OIDC to validate users based on that new Client App.
  • For deployment scenarios where a Digital Distributed Container can’t connect back to the Digital Enterprise Suite, it is possible to override that behavior.
• The Digital Enteprise Suite now supports logging using the JSONL format (using GCP schema).
• Pasting multiple lines of text in an enumeration definition now creates multiple enumerations entries.
• A new option allows to hide inner data inputs from being displayed on the form when executing a user or manual task.
• The client hosted configuration for HTTPS certificate was simplified to accept PEM certificates and keys.
• The sub-menus of the data type menus are now shown on mouse-over.
• Collection and ranges in the data type selector are now grouped.
• Fixed an issue that was preventing a diff after a version has been published.
• The option to create a token was incorrectly offered on data objects when testing a model.
• Tokens in error could not be moved anymore when testing a model.
• The font size is now properly imported from DMN XML.
• Automatic translation was ignoring description, notes and examples fields.

Bug fixes:

• The new version of safari on OSX had an improper interaction with our loading spinner for the detail panel of elements.
• The sort function implementation could generate errors when sorting context keys that are equals for objects.
• Incorrect FEEL highlighting for variables after a filter is found inside a context definition of a for loop literal expression.
• Incorrect FEEL highlighting for variables inside multiple level of filtering inside a for loop.

Bug fixes:

• Some links in email and Microsoft Teams notification could be incorrectly generated.
• Dragging to select multiple elements could cause the canvas to move in incorrect directions.

Bug fixes:

• The SAML AssertionConsumerServiceURL assertion will not contain the query string anymore.
• When updating the base image credentials for digital distributed containers to a registry not requiring an identity, it could prevent the image from properly being pulled.
• Cycles in decision model inclusions could prevent a model from properly saving.
• While testing, updating the value of a data object could not work as expected unless it was selected in the diagram.

Bug fixes:

• Improved the loading speed performance of test cases using models with type recursion.
• When a model that is reused is saved multiple times, depending models might get synchronized multiple times.
• Fixed an issue with reused data types from included models.
• Updating a context entry description does not make the model dirty.

Bug fixes:

• Long data type enumerations bleed over the table in the documentation.
• The order of the data types was not always properly kept.
• Fixed an issue when loading older models that contained unsupported features of data types.
• Fixed various FEEL syntax highlighting in filters.
• To improve SAML compatibility, login requests now includes the AssertionConsumerServiceURL.

Bug fixes:

• The first synchornization of a data type from a graph data store could not produce the right result for some data types.
• Warnings attempting to fetch some data from a data store could incorrectly instead generate an error.
• Custom XML parsing of a textual element based on a data type with both a type reference and allowed values could result wrong data type being considered.

Bug fixes:

• Result highlighting for some context box expression were not properly displayed.
• JSON and XML template generated for services would not properly represent collection of strings and repeating containers.
• Date and times with a time zone were not serialized consistently in cloud events (emitters) to the way they were serialized in REST calls.
• Allowed values defined in a parent type were not always properly checked when the data validation was turned on.
• Testing a workflow model with attended tasks were not properly allowing to complete the attended part of the task.
• The filter boxed expression required the item prefix for filters.
• Fixed a FEEL highlighting issue for context inside loops.
• Displaying a date and time in the system of engagement could yield an invalid date message.
• Importing data types from a JSON or XML schema could disconnect their references in the model.
• The command line client (des-cli) was not able to re-index the graph properly.

Bug fixes:

• Clicking on the plus icon to open a sub-process or a collapsed stage would not work under certain circumstances.
• Fixed syntax highlighting in FEEL expressions after a function with parameters is used inside a returned context.
• Paste by value/by reference doesn’t paste where the contextual menu was opened.

New and improved features:

• APIs Guru (an open marketplace for APIs) is now integrated in the Operation Library to facilitate the access to thousands of integrations.
• Interfaces in the Operation Library can now have their icons customized.
• When testing a workflow process, it is now possible to move/create/delete tokens.
• Process and cases reused through the Digital Enterprise Graph now offer their end/milestones variables for output mapping.
• It is now possible to update the data type of a decision logic in addition to creating a new one.
• When dropping or synghronizing a data type with the Digital Enterprise Graph, it is now possible to select a Replace All option.
• An option to automatically refresh the page on changes is now available in the service instances and my tasks views of Cloud Execution.
• Executing java classes in Business Knowledge Models (DMN) or Script Tasks (BPMN) now allows the usage of the java.lang.Math library in all deployment scenarios.
• A new Public API allows to fetch deployed models inside of services in the Digital Automation Suite.
• A new Process Service API allows to reassign user tasks to other participants.
• Allow users to decide if they want to update existing data type when importing from JSON Schema.

Bug fixes:

• When right-clicking on a shape immediatly after dropping it on the canvas, the browser contextual menu could be shown.
• Digital Enterprise Graph synchronization issues are not displayed anymore in the Kommunicator.
• When adding input requirements to a decision model, existing test cases would report missing inputs.
• Deploying a CMMN model through the Public API deployment resource could result in an error.
• When a decision was defined as outputting a Text but something else was actually returned, the test case could not be saved.
• Some workflow process services that invoke case tasks would not properly deploy.
• Various improvements to the FEEL parser inside filters.
• In an activity data mapping, a context typed as Any can’t always be filled properly.
• Some tasks in the My Tasks view could have been generated with an incorrect link. This will require an administrator re-index.
• Digital Distributed Containers were not properly establishing user sessions in the system of engagement which caused an error to be logged in the container.
• Adding an issue to a model in the example places should not be allowed.
• Can’t assign performers to signal/message events and sub-process.
• The issues overlay does not always refresh properly.
• Removing an interface from the operation logic of an imported BKM triggers an error.
• The breakpoint tab in the testing functionality of the workflow modeler would not display all breakpoints when a model was calling another one.
• The contextual menu would not be shown when clicking directly on a gridline.
• Some data types were wrongly identified as being used when selecting the delete all option.

Non-Backward Compatible Changes:

• We have deprecated and removed the XPDL import and export, the BPEL export and the Project import from the Workflow Modeler.

Bug fixes:

• The notification bell on the main page of the Digital Modeling Suite could not be clicked.
• A workflow service containing a data output named end and a case service containing a case file item named milestone would not be able to generate a valid OpenAPI definition of their service.
• Certain FEEL expressions were impacted by the right operand and and or expressions being executed without being required.

New and improved features:

• It is now possible to migrate long running service instance (process and cases) between different versions of a service.
• A new admin API is available on long running services (process and cases) to move, create or delete tokens.
• The place filtering was replaced by a place search that allows to find files in a local place or through all places.
• It is now possible to promote a place into another place. Promoting a place replace the content of the target place with the content of the source place without affecting the history of the target place and optionally assigning a version and state.
• Constraints can now be added to collection data types.
• It is now possible to add more than one flag on an element.
• When renaming a data type, its name will also be updated in the FEEL logic using the instance of function.
• A loading feedback was added for large model requiring some time to load.
• Included decision model elements now have a link to their included model in the detail panel.
• New FEEL warning messages are now reported when trying to do boolean operators (equal, not equal, greater than, and, or, …) using two expression of incompatible types.

Bug fixes:

• The instance of FEEL operator would not properly differentiate years and months duration from days and time duration.
• When reaching a dead end in a workflow, the process test functionality could incorrectly keep tokens that did not exist anymore on the canvas.
• It was not possible to hide some links in the Knowledge Entity Modeler and the Workflow Modeler.
• The browser default contextual menu was not displayed anymore when right-clicking on a rich-text input.
• Administrator using the test functionality could sometimes get incorrect results because they would also receive other users results in parallel.
• Importing an OpenAPI that does not define its output and/or error make them unusable for data mapping.
• Markdown tables not imported in the OpenAPI import.
• There are missing functions in the context of the FEEL expressions in the data type in the Knowledge Entity Modeler.
• Included decisions that are not in the current context were incorrectly added to the whole model decision service.
• When an included model could not be found, the model might not be able to load its pages.
• Custom FEEL functions were not updated in item definition constraints when the prefix was changed.
• Decisions from included models did not depict ellipsis on missing requirements.
• When clearing the search field in the data type dialog, some letters may stay highlighted.
• The save button of the products section of the user provider tab in the administrator instance would not properly save for certain clients.
• The dependency panel and where used panel would not always load.
• Improvements to the FEEL context parser with an untyped global variable, a global variable inside a loop and on a collection inside an inline context.

Bug fixes:

• Test cases from some models with data types defined recursively could not be loaded.
• CMMN XML models that had sentry graphically depicted under the element to which they were attached could not be imported.

Bug fixes:

• Optimized the delay when saving a model with a large number of data types to a different place on a high latency internet connection.
• Some models published before version 11.10.0 and using the healthcare custom FEEL library were not loading properly.