Release Notes

Release Notes - Digital Enterprise Suite icon May 15, 2022 (Version: 10.15.4)
Bug fixes:
  • XSLT script tasks did not properly accept a Data Object Reference as input.
  • Discretionary stages could cause an error when deploying them for automation.
  • Importing data types from an XSD does not properly validate duplicated data types from the current model.
  • Under some conditions, it was impossible to add input parameters to an operation in the Operation Library.
  • The FEEL functions list contains and the in keyword were too strict when matching numbers and 1.0 would not match 1 in the collection.
Release Notes - Digital Enterprise Suite icon May 1, 2022 (Version: 10.15.3)
Bug fixes:
  • Where used requests were not showing results outside of the same graph where the element was saved in.
  • Selecting a different location to publish a model could display the place selector in an improperly sized interface.
  • The File -> Print option would hide linked terms when printing.
  • The styling of the drop-down menu to change the data type of an activity input/output was not displaying properly.
  • Using Azure Container Registry as a source for Digital Distributed Container base image could create an issue with URLs generated that contains two consecutive slashes.
  • Publishing a workflow service with inner data inputs that were not typed could incorrectly display a warning at deployment time.
Release Notes - Digital Enterprise Suite icon April 18, 2022 (Version: 10.15.2)
Bug fixes:
  • XSLT script tasks returned an error when using XSLT 2.0 constructs.
  • The running process instance data access endpoint of workflow services did not display the filter selector.
  • In the new system of engagement, if an error is present, it will be displayed as intended in the service instance view.
  • When searching for a data type from an accelerator, it was not possible to select a result as a datatype.
  • The identity management page could return an error in rare cases
  • The group REST API was not returning newly added users between server restarts.
  • Active triggers were not registered on Digital Distributed Containers.
  • Workflow services now continue to process events when in error state.
Release Notes - Digital Enterprise Suite icon April 11, 2022 (Version: 10.15.1)
Bug fixes:
  • Sometimes the data types from cloud data store would stay read only after deleting it from the settings interface.
  • The back button for the operation library would not be clickable under some rare circumstances.
  • The report (HTML/Word) would not properly generate for certain models exported from Discovery Accelerator.
  • Assigning a trigger from the connector panel to an existing start or intermediate event would incorrectly change the name of the message in the data mapping.
  • When exporting issues to CSV, in rare case an undefined field could prevent the export from completing.
  • When a null variable was used in a sequence flow condition, there could be a parsing issue if that variable had a FEEL keyword in its name.
  • When a model contained multiple message events bound to the same message, it was possible that a caching issue prevented the proper triggering of the event.
  • In the new beta system of engagement, a rare condition could prevent the collection data from being displayed from a decision service.
  • In the OpenAPI/Swagger definition of a service, the FEEL data type Any was incorrectly mapped to an object instead of an untyped property.
Release Notes - Digital Enterprise Suite icon April 4, 2022 (Version: 10.15.0)
New and improved features:
  • The data type selector available inline when changing the type of data elements was improved
    • There is no need to unlink to link to a new type anymore.
    • Existing types can now be searched.
    • Datatypes can be referenced from the Digital Enterprise Graph or from an Accelerator directly from the type selector.
  • Flags that were previously converted to tags (v10.0.0) in the modelers are now back as an overlay and in the detail panel.
  • It is now possible to import and export models from Discovery Accelerator, Knowledge Entity Modeler, Landscaping and Capability Modeler.
  • Issues of a model can now be exported to a comma-separated file from the modelers issue view.
  • Place issues can now be exported to a comma-separated file from the place issue view.
  • It is now possible to define interfaces to servers that require the implicit, password and client credentials OAuth 2 flows.
  • A FHIR trigger connector was added to work with the FHIR Subscription resource.
  • A RabbitMQ connector is now available to push and pull messages from a queue in workflow services.
  • A RabbitMQ emitter is now available to push events to queues.
  • In the knowledge entity modeler healthcare tab, Resource was renamed FHIR Resource.
  • A new place shared place can be added from the places tab in the admin for clients subscribing to the Healthcare Feature Set.
  • Allow to use error definitions without error code to support ‘catch all’ error events in workflow automation.
Bug fixes:
  • Fixed a backward compatibility issue with rare workflow models.
  • The public API functions to retrieve issues without an open parameter was incorrectly only returning the closed issues.
Release Notes - Digital Enterprise Suite icon March 28, 2022 (Version: 10.14.4)
Bug fixes:
  • Improved our support for reverse proxy that partially pass forwarded headers.
  • Do not send SMTP credentials when the username is an empty string.
Release Notes - Digital Enterprise Suite icon March 27, 2022 (Version: 10.14.3)
  • Method and Style decision table analysis could report non-existent gaps for date intervals.
  • The retrieval of terms from a value set was limited to the paging size of the FHIR terminology server.
  • Under some conditions, it was possible to export a DMN 1.2 XML with the incorrect FEEL namespace.
  • The issue overlay would sometime not find the proper element to attach to.
  • Optimized the workflow process services resource consumption for models with large data definitions and data mappings.
  • Decision Service audit execution profile does not output the decision outputs.
  • Decision Service audit execution profile outputs invocations inputs/outputs only using the debug profile. They should be available with the audit profile.
  • Service startup could cause a race conditon that would return an error response.
  • It is now possible to deploy message start/intermediate/end events and send/receive tasks without having to defined a message data type.
  • CDS Hooks prefetch for queries by ID could generate an invalid count parameter internally.
  • An error was generated when trying to resume a service task in error without input parameters.
  • Allows the usage of error events in workflow services without code (catch all).
  • Documentation for the public api service deployment was added.
  • Various edge case improvements to he FEEL parser: context scoping levels, spaces before the [] operator, inline collection detection, crash prevention.
  • It was possible for collections types to be incorrectly displayed in red in the data mapping.
  • The issue navigator was not always loading from the launcher application.
Release Notes - Digital Enterprise Suite icon February 23, 2022 (Version: 10.14.2)
Bug fixes:
  • Using special characters could prevent the term linking from properly working.
  • The BPSim editor was generating an error preventing it from opening.
  • The Method and Style decision table validation will not detect gaps between dates anymore.
  • The colon (:) character was not properly encoded in path parameters when doing REST operations.
  • Accessing the form API of a service directly would not refresh the user session if it was expired.
Release Notes - Digital Enterprise Suite icon February 21, 2022 (Version: 10.14.1)
  • Using the new system of engagement, the CDS Hooks endpoint was not visible anymore if the service was not published as a SMART on FHIR service.
  • Context autocompletion could not work properly inside invocations boxed expression.
  • The Visio import could produce an error using a very specific combination of stencils in a model.
  • The eLearning and more information on how to fix validation issues could become unclickable when using some security settings.
  • Event subprocess that uses conditional events as start event were prematurely completed even when having timers that should keep it active.
Release Notes - Digital Enterprise Suite icon February 12, 2022 (Version: 10.14.0)
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.
Release Notes - Digital Enterprise Suite icon January 25, 2022 (Version: 10.13.3)
Bug fixes:
  • Improved the memory and processor consumption of accessing CMMN and DMN XML models from the Public API.
  • Improved the resource consumptions of most Digital Enterprise Graph queries.
  • Validation of a workflow model using data association connected to a sequence flow could fail under certain conditions.
  • Timer events were not always properly triggered when the sub-process was started from a called activity.
  • Conditional event subprocess with non-interrupting start event cannot be triggered more than once.
  • Timer expression did not work properly on newly created models.
  • Fixed an issue with first decision tables when an error occurred after the first rule evaluated to true.
  • Deleting a folder containing multiple files could leave some models in the digital enterprise graph.
  • An error was incorrectly reported when a hyphen was present in the name of a variable after a collection accessor.
  • Cloud Data Store import could fail when the first data row does not have a value.
  • Cloud Data Store using any attribute could not be opened as excel files.
  • The management page styling could display incorrectly if the user was not an administrator.
  • Merging multiple models with extended attributes could prevent the save of that model to XML.
  • Importing an OpenAPI file with a file data type did not map correctly to the file data type.
  • Non-blocking case tasks icon should not be all black.
  • Importing a DMN 1.3 with Trisotech extensions for DMN 1.4 new boxed contexts could cause an XML format issue when exporting to DMN 1.4.
Release Notes - Digital Enterprise Suite icon December 21, 2021 (Version: 10.13.2)
Bug fixes:
  • The OpenAPI documentation of a decision service could be incorrect for some models containing multi-level data types.
  • Under some conditions, picking the same decision logic in the data mapping after clearing it would not do anything in the data mapping for tasks.
  • Fixed the visual margin of a function inside boxed context entry of a Business Knowledge Model.
Release Notes - Digital Enterprise Suite icon December 15, 2021 (Version: 10.13.1)
Bug fixes:
  • The DMN XML export (all versions) can contain an unknown attribute (isCollection) for newly created decisions which makes the XML file not DMN schema valid.
Release Notes - Digital Enterprise Suite icon December 14, 2021 (Version: 10.13.0)
New and improved features:
  • A new system of engagement is now available in beta.
    • To activate the new system of engagement locally, you will need to toggle an option in the Service Library Preferences. The new system of engagement will replace our Try it Form with the release of version 11 at the beginning of 2022.
    • The Try it option was replaced by a Form option that provides a customizable form-based user interface to interact with deployed services. This form can be customized using cascading style sheets (CSS) defined globally, at the environment, at the group or at the artifact level.
    • A new user interface is available to interact with the service with files. Supported formats are XML, JSON, PDF and Excel.
    • A developer mode for the form is also available to customize the styling in line, generate test cases, inspect the service invocations and debug execution.
    • A test bench allows to generate and reuse test data between services (test data is keyed by data type across the instance).
  • There is a new user interface to assign performers to user/manual tasks.
    • The assignation based on user, group or expression is now simpler to understand.
    • There is additional control on the email sending preferences.
    • A template can be created for the email content being sent.
  • Performers can now be defined for intermediate/start messages to limit who is allowed to send these messages.
  • DMN 1.4 is now supported.
    • Import and export using the new DMN 1.4 XML schema.
    • A collection marker was added to decisions that outputs a data type marked as collection.
    • New DMN 1.4 feel functions are now available: is, floor and ceiling with scale attribute, round up/half up/down/half down, string join.
  • The dependency side panel now displays incoming and outgoing dependencies for this model.
  • A Where used tab was added to the detail of most elements to show where this element is reused in the Digital Enterprise Graph.
  • Client Access License report can now be downloaded in CSV format from the admin CAL page.
  • The healthcare information can now be displayed on terms.
  • The detail of most elements now contains a share button to create a URL that links directly to this element in viewing or editing mode.
  • When publishing a model from the collaboration ribbon, it is now possible to publish to a different place.
  • The ribbon bar now displays the place name.
  • Attachments in an element detail can now be sorted by using drag and drop.
  • A button was added to the data types dialog to allow the sorting of the data types alphabetically.
  • When using the JSON REST API for a service execution, the null values for outputs are now provided (they were omitted before).
  • It is now possible to send emails through service tasks to anyone with an assigned license for Trisotech Hosted clients.
  • When reusing by reference a Data Object from the Digital Enterprise Graph, it can now be changed to Data Input/Output while keeping its reuse link (lock).
  • The loading time for large Knowledge Entity models was greatly improved.
  • In the data mapping, more boxed logic choices are now available to express the mapping.
  • In a boxed context, increased to 15 the number of context entry that will get automatically populated based on the expected data type (from 6). If more than 15 context entry would be created, the user is still required to create them manually with autocompletion.
Bug fixes:
  • The HTML template for a service requiring a boolean input now properly document the value that should be sent to the service (true) on a check.
  • Fixed an issue that prevented to import a BPMN XML model containing no IOSpecifications but Data Inputs/Outputs.
  • When parsing DMN TCK test cases with excessive spaces in the values, certain data types parsing would not work as expected.
  • In the generation of a Decision Service from a Decision Model, inputs and outputs of type any would be represented incrrectly in the OpenAPI as string.
  • The REST service endpoint can now parse all of the PDF content if the input of the service is of type Any.
  • The web hook emitter would not work correctly if configured without identity.
  • When failing to delete a process instance, the output schema of the REST api could not be followed in exception cases.
  • Boundary conditional events are now properly supported for embedded subprocess.
  • An issue prevent the creation of a Decision Table within a Boxed Context.
  • Data type of type Any are not always properly synched in the Digital Enterprise Graph.
  • We could get a blank page when clearing the decision logic inside a boxed function and then undoing that change.
  • Examples in the FEEL Quick Guide can now be selected with the mouse.
Release Notes - Digital Enterprise Suite icon November 6, 2021 (Version: 10.12.1)
Bug fixes:
  • When using a data object with the same name as a read-only inner data input or output of a task, the data type of that data object could become incorrectly read only as well.
  • The concurrent modification message could incorrectly be displayed if the computer clock of the client was significantly different from the server clock.
  • Output data mapping defined from a previous version could be incorrectly upgraded resulting in the data mapping not being executable anymore.
  • The trigger dialog on message events could fail if no triggers were defined in the model.
  • Deleting a process instance that was created with a previous version of a process definition could fail leaving the instance undeletable.
  • DMN node names are now indexed using their sanitized names instead of their display names in the Digital Enterprise Graph.
  • Data Store content are not serialized anymore into events for services using them as input or output.
  • The help section about the Kafka emitter was missing from the Asynchronous Events documentation topic.
  • Kommunicator links were opening in a new window instead of within the Kommunicator.
Release Notes - Digital Enterprise Suite icon October 27, 2021 (Version: 10.12.0)
New and improved features:
  • A new application tile was added to control personal settings such as Identities, Event Emitters, Data Stores and language preferences.
  • Cloud Data Stores (currently in beta and will require an additional subscription) are now available for the automation of workflow and decisions.
    • Represented in modelers as a collection of a flat complex type. In workflows, they are bound to the Data Store BPMN element . In decisions, they are bound to the Input Data DMN element .
    • Can be created by all users under their personal settings tile. They can be shared with a group.
    • Access (as the owner or shared with you) allows to directly interact with the data store in the management interface (import, export, edit) and the ability to use it in the modelers.
    • Once deployed, any user can interact with a process or decision that uses a data store even if the data store is not shared with them.
    • Can be directly opened in Microsoft Excel to edit their content through the personal settings page.
    • The FEEL functions append, concatenate, insert before, remove, reverse, sort and union were augmented to interact with data stores and modify them.
    • Two new FEEL functions were added to support additional functionality for data stores: insert after (similar to insert before) and replace (to update one or more element of a collection)
    • Their scope is instance wide which mean that the same data store can be used in multiple process and decision.
  • The place navigator files and folder columns are now sortable.
  • The place navigator offers a new action to copy and move models to a different place.
  • The place navigator can now recover deleted models to their original location.
  • New automation FEEL functions were added.
    • current user: returns the user currently calling the automation API
    • initiator: returns the service initiator (user who started the process)
    • task history(name): returns the automation history (previously completed tasks)
  • New FEEL context funtions from DMN 1.4 were added: context, context put, context merge.
  • New FEEL text function funtion was added to generate URIs: uri.
  • FEEL expressions using the automation functions can now be used in performer assignments.
  • The healthcare tab in the Knowledge Entity Modeler now allows to enter the Resource Type.
  • Service library will now refresh without having to reload the application when a new service is deployed or deleted from another session.
  • Invocation boxed expression now offer autocompletion of FEEL methods.
  • Invocation boxed expression can now be used in the data mapping.
  • Linked terms in the name of elements are now dragged when reusing from the Digital Enterprise Graph
  • When right-clicking on a case file item, a new option allows to automatically create a case input or output based on the case file item.
  • When publishing to automation, a warning message will now appear if a version of the published model exist in the environment with a greater version number.
  • The ideation application can now be installed directly from the browser instead of requiring an app store download.
  • The environment event EnvironmentArtifactPublished message now contains additional information (language, the name, description, publisher and published date).
Bug fixes:
  • Attended task for the output of a service task configured before the data mapping would not work properly.
  • It was not possible to use the public api to download an audit log that was not registered on an environment message targeting none or more than one environment.
  • Renaming an element from the translation dialog could break name uniqueness under some conditions.
  • When dragging a process from the Digital Enterprise Graph in the workflow modeler, the description, notes, tags attributes of process inputs and outputs are now properly transferred.
  • Empty invocation bindings were not properly serialized to DMN XML.
  • When publishing to automation, the last modeling version is now always transfered as the default version for publishing.
  • Data mapping containg Conditional, Iterator or Filter boxed expression could result in a deployment error.
  • Cyclic data type usage between the Workflow and Decision Modelers could result in errors at synchronization with the Digital Enterprise Graph.
  • When publishing a service that is not the latest version of that service, the dialog with the service options was not displayed.
  • When filtering the list of services in the Service Library, the count of selected artifacts could be incorrect.
  • Prevent non automation audit logs from being displayed in the audit tab.
  • When using message events (intermediate) inside subprocess that is invoked via call activity the API generated for such events does not include the data model. In addition, triggering that endpoint (even with proper data model) will not be able to parse properly.
  • When the name of a data type is changed, the datatypes overlay on shapes was not always updated correctly.

Learn how it works

Request Demo

Confirm your budget

Request Pricing

Discuss your project

Request Meeting