Digital Enterprise Suite – Release Notes – July 18th, 2021

New and improved features:

• The Knowledge Entity Modeler tab Coding was renamed to Healthcare and now offers autocompletion of codes using ValueSets of CodingSystems from a FHIR Terminology server.
• New healthcare specific FEEL functions (healthcare codes, healthcare term codes, healthcare code in term) are now available to access terms codes at automation.
• The FEEL functions ribbon was moved to the LEARN ribbon and added to the workflow and case modelers.
• A new admin interface allows to configure the FHIR Terminology server settings.
• We now support decision and workflow models that defines CDS Hooks Cards as outputs to explicitly control the content of the returned cards. The default implicit mapping still applies for existing models.
• A new wizard is accessible to define emitters. This wizard is accessible under the /management/emitters URL. From this wizard, both user and system emitters can be created.
• It is now possible to document item components of data types.
• The identity management page (/management/identities) now allows to share identities with groups. Shared identities are usable by member of the group but can be deleted only by their owner.
• The identity management page (/management/identities) now offers an improved wizard to create HTTP identities.
• The progress when searching for a term in the graph is now visible in the rich text editor.

Bug fixes:

• Assigning a constant value in a user task mapping could generate an error for numeric data types.
• A workflow model containing an operation without input or output would not be allowed.
• Posting invalid or incomplete CDS Hooks prefetch data could generate an error without further information on how to fix it.
• The term selection dialog style was aligned with the other modeling products.
• The view ribbon was not fully displayed on smaller screens.
• It was not always possible to change the column data type of decision tables embedded in the return statement of iterator boxed expression.
• Under rare conditions, it was not possible to switch back from Natural Language to FEEL for an expression.
• Under certain circumstances, it was not possible to publish a workflow model including a decision model that includes another decision model.
• Data type subcomponents were truncated after 1 level when exporting the documentation.
• OpenAPI import does not import properly files with undefined object or arrays.
• Creating recursive data types was not allowed in the user interface.
• Links could be created for basic FEEL data types in the report.
• The OData create operation output was not properly poupulated with the OData-EntityId. That value was always null.
• A call activity that call a non executable process did not provide an adequate error message.
• Including a PMML model that contains spaces in its name would fail at publishing.