Digital Enterprise Suite

Digital Enterprise Suite – Release Notes – Feb 12th, 2022

Title Shadow
New and improved features:
  • Case automation is now available as a beta.
    • The case modeler now has an option to cloud publish case models.
    • The service library can now launch case services.
    • This initial release support most of the constructs of CMMN (case file item, human tasks, stages, entry/exit criterions with their on/if parts, performer assignation, case file items authorized roles, discretionary tasks and milestones).
  • It is now possible to publish a service as a SMART on FHIR app. This new app is only usable with the new beta system of engagement. A new Healthcare integration dialog is available under Rest API.
  • Execution environments now have a global access (default access to all users) access right.
  • A new group was created to represent all users with a client access license to the instance. This group can be used anytime a resource is shared.
  • An SVG export is available under the image export. Note that the SVG export uses foreign objects containing HTML and may not work with some SVG tools.
Bug fixes:
  • Collections of Any are now always parsed according to the JSON data type.
  • When using datastores, the detection of a date vs a date time was improved from Excel.
  • When using datastores, numbers could be rendered with a different precision when serializing to JSON for service calls.
  • In the new beta system of engagement, user task information is now displayed in the order of the defined data type.
  • Slash characters inside the path of an operation (REST call) are now properly encoded.
  • The output data mapping of a script task was limited to a single data object assignation.
  • In very rare occasion, the validation of a DMN model would generate an unexpected cryptic error.
  • Healthcare terms coming from decision models called within a workflow model were not considered in the healthcare FEEL functions.
  • CDS Hooks now receive additional information when an error occurred (new error key as an extended attribute to the response).
  • Emitters configured from the user interface could create a filter with an empty string that caused the emitter to match no messages.
  • The security model of certain message topics was too aggressive in preventing administrators from emitting events from other users.
  • Conditional expression were not properly imported in process instance name and process instance tags.
  • Data types created by data stores should now be properly removed even when the model is not open when the data store is deleted.
  • Terms defined in the Knowledge Entity Modeler could not be referenced with a semantic link.

Learn how it works

Request Demo

Confirm your budget

Request Pricing

Discuss your project

Request Meeting