Digital Enterprise Suite – Release Notes – March 26th, 2023

New and improved features:

• Renaming a Data Object or a Data Store in the canvas now also updates the data mapping, conditions and test cases that depended on that name.
• It is now possible to define a retry on error policy for process and tasks.
• A new custom FEEL function library was added to allow manipulation of Unit of Measure. It is now possible to convert and format measures taken into different units such as mass, length, concentration, etc.
• Added support for the CDS Hooks: medication-prescribe, order-dispatch, order-review, order-select, order-sign, appointment-book, encounter-start, encounter-discharge.
• It is now possible from the Healthcare dialog in the execution ribbon of the modelers to control which CDS Hooks type is implemented by your model.
• The SMART on FHIR configuration was moved from the deployment dialog to the healthcare dialog in the execution tab.
• Deploying and testing models speed has been improved significantly.
• Loading an incompatible test case in the test dialog now inform the user of the mismatch.
• It is now possible to import an excel file without headers as the first column in relation and lists decision logic.
• The administration page for accelerators now load faster.

Bug fixes:

• Renaming a folder did not always properly re-index the graph.
• BKM breakpoints (before and after) were stopping only once when testing a decision model.
• Testing with the full validation disabled the mutable FEEL functions for altering data stores.
• Some docker clients were not able to properly pull images successfully from our image registry.
• When using a rare data type condition, the OpenAPI specification for a service could not be generated.
• Changing the header type of a referred field could modify read only element.
• For boxed context expressions, the attributes of a file data type were not suggested in the autocompletion.
• The trace panel of the test functionality now shows all BKM invocations and not just the last one.
• An issue was preventing the proper edition of the data mapping of multi-instances call activities.
• Data Stores without data associations to a task will not appear anymore in the autocompletion suggestion for FEEL expressions.
• It was possible to generate duplicated inner data outputs when synchronizing it with the graph.
• Invoking a BKM or Decision Service with the same name as its model did not work properly.
• The collection marker was not always displayed properly when editing or viewing the details of a data type.
• The Method and Style validation of decision tables could fail if a cell was left empty.
• When downloading test results, the file name now always reflect the name of the service.
• Improved the error message when a decision model is not properly linked or could not be properly loaded on service publication.
• Corrected the text rendering of FEEL functions returned from decision logic.
• It was possible that the header of a decision table was displaying the wrong right side inclusion marker for range when refering a data type that allowed null.