Digital Enterprise Suite

Bug fixes:

• The dependency panel was not always properly refreshed when a workflow task had data associations.
• When searching for Value Sets with a space in the name, some FHIR server could return an error that prevented the proper matching.
• Value Sets returning codes without coding systems were not indexed in the graph.
• Using the underscore character to link to a term in Discovery Accelerator does not properly link the term.

Bug fixes:

• Making a REST call that returns information in an HTTP header would fail if the Header was not present.
• Copy/pasting a boxed context result row would generate an invalid model.
• Data types are not updating their missing status in the dependency panel.
• When searching for a term in the graph, the automatic matching should not occur if more than one match is found.
• When renaming a recursive data type, the recursive names are not updated properly.
• Removing an included model does not properly sync with the dependency panel.
• Decision services with missing nodes cannot be unlocked.
• Hitting CMD on MacOS while a shape is selected could clear the label.
• Changing a collapsed sub-process to/from an event sub-process does not update the icon next to the page tab.
• Internal DES services can now be called from Decision Models.
• Discovery accelerator could fail to load models whith a dependency to an accelerator.

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.

Bug fixes:

• Under some circumstances, the operation path containing spaces could be incorrectly encoded.
• To improve the support of legacy OData servers, query parameters containing spaces are URL encoded using %20 instead of +.
• When expanding a knowledge entity model that contains business rules from the digital enterprise suite, it could create an error and prevent the expansion.

Bug fixes:

• Some Workflow and Decision models invoking models could fail to publish to the automation.
• In certain conditions, decision services with missing data types would generate an error when synchronizing with their reference.
• The dependency panel could fail to load if a graph was unknown.
• When an element that is reused from the digital enterprise graph is reconnected, the lock stay red.
• The name of elements in the dependency panel is not always properly refreshed from the source model in Discovery Accelerator.

New and improved features:

• The automatic model comparison is now available in Discovery Accelerator (subscription required).
• The dependency panel is now available in Discovery Accelerator.
• A new security page is available to admins to control the web session length, the cross origin and iframe usage settings.
• For services that have a single input, the REST endpoint now supports submitting the input name or omitting it in the API call. By default the Open API representation of the input will omit the single input name but this change is backward compatible and messages containing it will still behave as they did before.
• The expression context in the Case Modeler now offer FEEL autocompletion.
• Roles cannot be assigned to Case File Items.
• The severity level of messages when opening a model where there are missing references to the Digital Enteprise Graph were adjusted to warnings.
• A new shortcut option was added to compare with the last saved version of the current model.
• The reuse buttons in the ribbon bar of the modeling products now display the product names instead of the standard they implement (BPMN to Workflow Modeler).
• Now supports the header x-forwarded-port when deployed behind a proxy.
• A new function is available for workflow automation to extract the text of an HTML string.
• When deployed in audit and debug mode, invoking BKM and Decision Services will now emit ServiceNodeStarted and ServiceNodeFinished messages.

Bug fixes:

• Re-importing OData definition disconnected the invocations to the operation.
• Generating a Word report containing test cases could produce an invalid Word document.
• It was possible to create an invalid BPMN XML file when using attended tasks.
• Sometimes Data Types would show up in the model comparaison without having been modified.
• Attachments URL and obsolete alternative names are now properly compared between models.
• Some performers of tasks could be impossible to rename.
• Data Types imported from a different Digital Enteprise Graph were not always properly mapped.
• Automatic translation could fail when translating a text with large images.
• Events are interrupted from being delivered to websocket emitters after a timer execution.
• A start message without data mapping introduced a context with the message name to the target data object.
• When resuming a workflow from a timer event, the base url setting of the automation is not considered when generating absolute URLs.
• The OpenAPI definition file could incorrectly represent messages that were input for messages when they were collections.
• The same message can now properly be used for both starting and during a workflow automation.
• The scope input field size was not aligned with the description and notes.
• Exporting to BPMN, the Data Objects are not properly connected to their activities.
• It should not be possible to lock missing copy of relationships.
• Reuse links can now be changed to copy links (unlocking) even when the link is broken.

Bug fixes:

• The typing context for iterator and filter boxed context could be lost preventing the proper parsing of ambiguous FEEL expressions.
• When making a REST call, certain characters in Query parameters are not properly encoded.
• Importing an OData metadata file containing entities without primary keys would fail.

Bug fixes:

• Attachments on elements can’t be deleted.
• Sometimes the HTML export fails when there are items with copy or reuse links in the model.
• With some configurations, the accepted Access Requests invites do not disappear.
• The FEEL now() function could cause an incompatibility when used in a decision table to compare with another date.
• The signal events in email sending incorrectly required an identity to be triggered.

Bug fixes:

• When exporting a Discovery Accelerator model to the Workflow Modeler (BPMN), the data objects links will now all be connected.
• Events changes are now properly reported by the model comparison.
• The term addition is not always rendered correctly in Firefox.
• Comments changes are not displayed when comparing models.
• Custom attributes changes on models are not displayed when comparing models.
• Data isCollection attribute changes are not displayed when comparing models.
• Removing a code sometimes doesn’t show properly when comparing models.
• Certain newly added elements would not show up when comparing models.
• Conditional expression on intermediate events cannot be modified.
• Only updated elements are now refreshed in the dependency panel.
• Improve how we present the model compare when a decision logic type was changed.
• Hit Policy and aggregation are not properly saved in Process Instance Name and Process Instance Tags decision tables.

Bug fixes:

• The DMN validation would report errors on validation for models that did not contain errors.

New and improved features:

• It is now possible to compare the current model to a previous version of that model. This option is available in the Teamwork ribbon (separate subscription required).
• When publishing a service (workflow or decision), 3 profiles are now available:
  • Production: Will generate a minimal amount of service events at automation for performance.
  • Audit: Will generate additional service events for each model node traversed at automation.
  • Debug: Will generate additional debug information for traversed nodes used for debugging purpose only.
• A new Dependencies side panel lists all reuse of the current model to external models.
• Terms can now be dragged from the Digital Enterprise Graph as entities in the modelers.
• Test cases, process instance names/tags and data mapping are now available in the documentation (html/word).

Bug fixes:

• Event emitter update API function could fail for certain emitter types.
• A workflow service with a dot in its process name would generate files with the wrong extension when trying to download the automation results.
• Reading XML context data now ignore non-alphanumerical character from attribute names when matching to the data types.
• The OpenAPI definition of a service containing a collection of collections could generate invalid files.
• Defining the condition of a complex gateway could fail.
• Parameters and outcomes are not properly synchronized when reused on decision services.
• Sometimes autocompletion is not offered inside boxed context entry in a deep context.
• OData import does not properly support multiple namespaces in the metadata definition.
• Fixed an issue where creating a boxed context inside another boxed context could create a rendering issue.
• Fixed an issue where creating a conditional expression inside a boxed context could create a rendering issue.
• Fixed an issue where a FEEL unparsed marker could not be cleared properly.
• Translation on hidden items could prevent the model from being opened.
• The second and third parameter of a BKM invocation could experience some autocompletion issues in specific situations.
• Workflow modeler could freeze when drawing a data association between two lanes (not in a pool).
• Invocation of reused decision service with missing type gives a blank page.
• Input/Output on case are not exported.
• FEEL autocompletion not suggesting sub-components after a filter in a for loop.
• Invalid test cases could prevent a decision model to be exported to DMN XML.
• Data input/data output cannot be synchronized with their related graph element.
• Resume point form description could in some rare cases be incorrectly rendered.
• The product FEEL function edge case product([]) = null was corrected.

Deprecation:

• In version 10.10.0 (June), authenticating using the AuthToken session cookie to the APIs will not be supported anymore. Please use bearer tokens generated from Client Apps.

Bug fixes:

• The rich text editor of the detail dialog was not properly displayed preventing the edition of rich text.
• The excel export dialog is not always visible.
• The REST based emitters defined by users could run into a race condition preventing them from being correctly re-instantiated from configuration.
• The REST API user interface would appear frozen when an error happened when expanding an operation.

New and improved features:

• It is now possible to mark a workflow task as Attended. Attended tasks can add a manual validation step before and/or after a task at automation.
• The HTML rendering of the OAuth page was improved and now allows to set expiration dates for tokens.
• Added a default Content Security Policy (HTTP CSP) to reduce the possibility of exploiting Cross-Site Scripting.
• The digital distributed containers now support an additional environment variable (BASE_CONTEXT_PATH) to deploy them under a specified URI path (ex: /decision instead of /).

Bug fixes:

• Under rare circumstances, some user places would not be visible anymore to some users.
• The play button on attachments does not show properly to select if an attachement should be played or not during animation.
• The reporting (word and html) could fail if there were semantic links attached to terms.
• Allow to import BPMN XMLs that have the common flaw of referencing semantic elements in the BPMNDI namespace instead of the target namespace.
• Identities of linked models are now properly asked when publishing for automation.
• Ctrl-Click to select multiple shapes on the canvas was not possible when clicking on the label.
• The default location value for APIKey identities would sometimes be incorrectly interpreted when making a REST call.
• The file menu is displayed under the text view.
• The dropbox connector for attachments caused an error.
• Changing an activity to multi-instance was not undoable.
• Fixed refresh issues with the identity dialog when publishing a model for automation.
• The automatically generated decision service name should not change based on the interface language.

Deprecation:

• The one drive connector for attachments was deprecated.
• The XPDL 3.0 export was deprecated.

Bug fixes:

• There are cases where the try it form would not display the advanced errors when using JSON or XML inputs.
• The documentation could only be viewed with an authorized account.
• An exception prevented the results of a decision model test that contained a data type with a file as an component.
• An error prevented collapsed capabilities from properly expanding.
• Decision service types was sometimes created as a copy instead of a reference when synchronized from the Digital Enterprise Graph.
• Choreography participant labels were not properly refreshed when resizing a choreography activity.

Bug fixes:

• When viewing decision models in the Kommunicator, a configuration issue was preventing the action bar from being properly displayed.
• The email notifications for user mention on issues and comments were not always properly encoded in html.
• The email notifications for user assignment to an issue contained the issue GUID instead of the issue number.
• In the text view, the choices of multiple collection when tagging could pop under the text editor.

New and improved features:

• Terms from the Knowledge Entity Modeler can now be linked in the name of shapes in diagrams.
• A new type of emitter (Audit) is now offered to all deployment types. It keeps the last 60 days of events and can be downloaded as a log file through the REST API.
• The auditing functionality of Cloud Execution was integrated with the audit emitter and now available from a single tab.
• It is now possible to select Any as a data type to mean that it is unknown at design time.
• Errors when execution services now includes more technical details.
• The Try It form now displays the technical details of errors when executing services.
• The distributed container administration page now has an area to enter a Kubernetes template. This template can be used in the Service Library to automatically generate a YAML file to deploy the container.
• When using the Rich Text editor for data mapping, it is now possible to view the HTML source code of the mapping.
• When using the Rich Text editor for data mapping in HTML source mode, any element attribute can be replaced by a feel expression by prefixing it with data-feel-expression- (ex: href=”…” -> data-feel-expression-href=”My FEEL Expr”.
• A new parameter is available on the Public API method to retrieve modeling places members including those from groups.
• When assigning groups to modeling places, these users are now available when assigning issues.
• The mention user interface in comments and issues was improved.
• Importing an invalid BPMN XML model that does not use DataObjectReference but instead depicts DataObject will now be automatically fixed.
• In the dialog to see the previous versions of a model, the current version of the model is now shown at the top of the list.
• The base container image of the automation engine and the distributed container are now based on alpine (as it was before V10) to eliminate CVE of the latest debian base image and reduce the contianer image size.
• A new Asynchronous Event was added for WebSessions.
• It is now possible to link to terms using the underscore character (_) in Discovery Accelerator.

Bug fixes:

• The description toggle button had no effect on the search for terms.
• When the automatic language translation fails, an error message is now properly displayed.
• When setting a translatable value (name, description, …) in an alternate language, this value will not be set to the main language anymore.
• In the Operation Library, re-importing the same OData definition twice duplicates the operations and data types.
• When undoing the naming of a data object reference, the state could not be restored correctly.
• When transforming a literal expression to an iterator the space after the iterator keyword was not considered.
• Weeks is not offered anymore as an option for Days and time duration constraints.
• ServiceStartedMessage event (under the service topic) for processes used the id of the process instead of the name as serviceName.
• Message correlation filters that returns a non boolean value will not trigger an error but be considered false.
• When processing a message on the message trigger REST endpoints, the HTTP context was not propagated correctly resulting in issues when trying to generate relative URLs.
• The message trigger endpoint would wrap certain messages in an extra layer on very specific data definition.
• Assigning a group as the performer of a workflow task will now send notifications to all members of that group.
• Resuming a process that was in an error state now only offer to change the inputs to the failed task.
• Renaming a model and trying to open it could fail.
• The description is now properly displayed over linked terms.
• The styling of the tags were aligned with the other modeling applications.
• Using an HTTP GET on the REST api to resume a workflow could incorrectly return the data type of the workflow input.
• The FEEL parser was not always recognizing the instance of function.
• The Identity Management page could not create all types of HTTP and ApiKey identities.
• The Webhook emitter could not use all type of identities.

Non-Backward Compatible Changes:

• The audit log format of service execution was slightly changed to align with the Cloud Events standard. Similar information is available but clients that are parsing these audit logs should modify their implementation to align with the new format.
• Client Hosted: With the change on how audit logs are defined in Cloud Execution, existing audit configuration will need to be reconfigured after the deployment.
• Trisotech Hosted: Audit logs generated before this version will not be downloadable anymore from the Cloud Execution user interface. Our support can send you these logs if required.