You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Before you upgrade make sure to read the General Upgrade instructions as well as the Upgrade instructions for previous versions.
The changes are color coded. Orange elements have been changed, Green elements have been added and Red elements have been removed compared to the previous release.
Table of contents
Message event flow
By default, the new message event flow functionality is disabled, because the functionality affects all (existing) message events in your model. When you want to use this functionality, make sure that you have applied the changes as described in the documentation to every message event.
To enable the functionality, add the following to the application.properties of the Case Engine:
blueriq.legacy.map-message-event-data-to-process-profile=false
Note that this is temporary until release 18, where the functionality will be enabled by default.
Default response media type
When no Accept header is present in a request, several error responses used to be represented using XML instead of the JSON representation that is used for success responses. This has been adjusted such that responses are now JSON by default across the board. It is recommended to include an Accept: application/json header in each request to be explicit about the desired response media type.
Known issues
For an overview of known issue please refer to: Known issues.
Overview
Content Tools