The about dialog in Encore now shows information about the currently active license.

(or for macOS) can now be used to save all changes in Encore

Consistency improvements in Encore:

• Newly added target entities in a data mapping now appear at the bottom of the list.
• Dropdowns that are required should not be clearable

In the pending changes view in Encore, projects and modules have two checkboxes: one for selection of the project/module and its children, and one for changes in the project/module itself. In this release, the sentence "Interaction module [module name] was updated" has been added to clarify the distinction between the two checkboxes: 

In merge conflicts in Blueriq Encore, the names of the current and source branch are now provided, making it easier for the Business Engineer to choose the right solution. 

In the Runtime devtools when connecting to the Studio, it is now possible to use OIDC authentication (using client credentials) instead of Basic. Basic authentication for the Studio is deprecated and will be no longer be supported in a future version.
For new Blueriq installations that are installed using the installer, OIDC will be configured by default.
For upgrades from an earlier 17.x version to 17.10, see Configure Studio server connection for instructions on how to configure the Runtime to use OIDC instead of Basic.

To minimize the efforts for a business engineer to handle message events, we developed the message event flow. This is a new flow type, which allows to register a flow to handle a message event directly. This saves the business engineer time and reduces the complexity of the model by taking away the need to define mappings to pass on message event data to an automatic task to actually process the message event data.

A detailed guide on how to use the new message event flow is provided here: Handling Message Events pre Blueriq 17.10.

Note that this functionality works with Case-Modelling (DCM2) only. Also, because this new way of handling message events applies to all message events in your model, this functionality for now needs to be enabled using a property. That way customers can ensure that they are ready for this functionality before switching it on. We plan to enable this feature by default in R18.

Exposed REST services support Content Negotiation, an HTTP convention to specify the content representation of requests and desired response types using Content-Type  and Accept  headers. This release improves the response format when content negotiation cannot be satisfied, sending a response with 406 or 415 status code instead of a 500 Internal Server Error.