Digital Enterprise Suite

Digital Enterprise Suite – Release Notes – October 9th, 2023

Title Shadow
New and improved features:
  • Implemented most of the changes from the new version of the DMN 1.5 standard.
    • The Decision Modeler now imports and export in DMN 1.5
    • The Digital Automation Suite now supports all of the new features of DMN 1.5.
    • It is now possible to include decision models without a prefix into the default namespace by specifying an empty prefix.
    • It is now possible to include custom FEEL function libraries without a prefix into the default namespace by specifying an empty prefix.
    • Support for the alternate graphical notation of Input Data in DMN that aligns with Data Objects of BPMN.
    • It is now possible to assign a specific type of range as a type.
    • The Test and Form functionalities now have proper support for ranges of different types.
    • Improve the support for subtyping of lists, contexts, ranges and functions in the instance of operator in FEEL.
    • The FEEL language now has an updated range() function that takes a string as a parameter (ex: range("[18..21)")).
    • Support the scientific notation to define numbers (ex: 2.3e-5).
    • Negative durations are now supported in the FEEL language (ex: -duration("PT1H")).
    • Suppor the @ notation for temporal expressions in the modeling environment (ex: @"PT5H").
  • When loading a test case, modifying it and saving it, its original name will be offered by default.
  • It is now possible to add external links in rich texts inputs in the modelers.
Bug fixes:
  • Under some conditions, the selection of the data type contextual menu could be partially hidden under the data type selection dialog.
  • Special character such as ‘<‘ were not visible when a FEEL expression was displayed as FEEL unparsed.
  • When pasting a service task link to an operation with errors, errors are not properly linked.
  • Replacing an existing term in a model could cause the modeler to hang.
  • The translation model scroll bars are not always aligned with their container scroll bars.
  • In the test cases, an empty string could be incorrectly serialized as a null in the test cases.
  • Loading a test case with an empty list incorrectly trigger a detection of a type change.
  • The file data type was not always properly saved in test cases.
  • When entering a non FEEL value in the scripting language picker, reloading the modal could cause an incorrect value to be displayed as the scripting language.
  • Creating a data type from the output of a decision service would always create it as Any instead of properly proposing a data type based on the Decision Service structure.
  • Importing data types from a JSON schema now support importing nullable objects that define themselves as either a type or null.
  • After completing a graph synchronization, it was possible that the current page would automatically switch without user interaction.
  • The missing status of an element was not updated when that element was replaced by a newly dropped one from the graph.
  • The severity level of messages at deployment times were aligned with the validation severities.
  • Improved the delay when importing a JSON Schema in a model already containing multipe data types.
  • When overing on the elipsis marker on a shape, under certain conditions it was possible that the wrong or no shape feedback was displayed.
  • Term definitions would not follow a copy and paste in a different model.
  • The email configuration channel save and test button were not properly saving and testing the configuration.
  • The offline Trisotech Accounts option was not offered for the proper license type.
  • The date, date and time duration and years and month duration FEEL functions were syntaxed highlighted in red incorrectly if a variable was used as a parameter.

Learn how it works

Request Demo

Confirm your budget

Request Pricing

Discuss your project

Request Meeting