You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

1. New

1.1. Undo & redo in Blueriq Encore

It is now possible to undo (CTRL + Z) or redo (CTRL + SHIFT + Z or CTRL + Y) changes within element level giving the Business Engineer more control and freeedom while modeling.

Changes that can be undone / redone include:

  • recovering rows that you just have removed,
  • reordering rows,
  • undo a convert action from inline to reusable,
  • retrieve cancelled changes,
  • and many more.

1.2. Easily transfer profiles in Blueriq Encore

You can now easily transfer profiles between unit tests, quick test, data mapping simulator and from the webservice debug log by copying to and pasting from your clipboard. This unlocks full potential of the aforementioned features by increasing the freedom of the business Engineer and removing the need of the cumbersome process of manually composing profiles for some use cases. 

1.3. Element comments in Blueriq Encore

Comments are back! You can find them conveniently in the properties panel of each element to describe your design decisions. You can now also edit and delete the comments you authored, and administrator users can edit and delete any comment.

1.4. Keyboard shortcuts in Blueriq Encore

Boost your productivity using keyboard shortcuts in Blueriq Encore! Among others, the good old ALT + D to open the dependencies has made its return. Click here to see a list of currently available keyboard shortcuts. More combinations will follow later.

2. Enhancements

REST connection OAuth2 request parameters

We introduced properties to send along custom OAuth2 access token request parameters when authentication on a REST connection is set to 'oauth2'

Improved dependency navigation in Blueriq Encore

The dependency tab in the properties panel will now be automatically opened when navigating from the dependency tab itself, allowing the Business Engineer to navigate through dependencies more easily.

Use middle mouse button to close views in Blueriq Encore

Views can now be closed using the middle mouse button (scroll wheel) from the sidebar. Using the middle mouse button to click the Save or Cancel buttons will also close the view after the action has completed. This is in replacement of the Save and Close button that used to be available in the old Studio client.

3. Documentation

Documentation on the new features and improvements of this release is linked in the respective topics.

4. Changes Platform Support

Our Platform support is updated.

Changes are:

  • Added support for RabbitMQ 3.13.3
  • Removed support for RabbitMQ 3.11.11

5. Upgrade Instructions

There are no specific upgrade instructions for this release.

As a best practice

  • backup your repository
  • backup your database before running scripts
  • backup your spring.config.additional-location directory ([Blueriq installation directory]\Runtime)
  • backup any config files you have altered under [Blueriq installation directory]\Services

before you start the upgrade.

6. Artifacts

 The Blueriq artifacts are available under name:

This release includes these versions of Blueriq components with a separate life cycle:



Customer Data Service5.0.3
DCM Lists Service4.0.2
Material Theme1.3.3
Development tools frontend2.0.1
DCM Maintenance App5.0.3
Audit Consumer1.0.3
DCM Dashboard Service2.0.2
Gateway Service1.0.2
Document Renderer2.2.0

7. Blueriq Libraries

There are no specific Library updates for this release.

8. Libraries

For this release there are no specific Library updates.

9. Retirement announcement

There are no specific retirement announcements.

For a full list of deprecated features, go to Deprecated features.

10. Bug fixes






Java Runtime

Executing a SOAP request without an active tracing context would fail with a NullPointerException.

The tracing context is not incorrectly propagated when none is active.



Copy to clipboard from quick test would not copy date and datetime values correctly.

Date and datetime values are now formatted using ISO-8601 notation.



The scroll position of navigation menus was not remembered once the navigation menu had been closed.

Opening the navigation menu now restores the scroll position according to the previous time the navigation menu was open.


Java Runtime

The mapping for the external flow contract that was introduced in Blueriq 16.10 would not properly detect of an attribute was single valued or multi valued, which would case problems when the mapping contained multi valued date or date time attribute containing a single value.

The external flow mapping now properly detects the multivalued state of the attribute



The REST editor did not provide body elements or custom schema elements for the request body when using an XSD schemaset.

The available elements can now be selected again from the dropdown.



The OutboxTraceDao would log a warning on every case action about not being able to trace an aggregate event becasue of a missing case id.

When the OutboxTraceDao receives a Aggregate event it is now dropped immediately and logging it on DEBUG level instead of WARNING level.



The mapping for the external flow contract that was introduced in Blueriq 16.10 would populate instances before all instances have been created, which would cause problems when the mapping would contain relations.

The external flow mapping now creates all instances before starting to populate them.



An expression editor that is not initially visible, e.g. when it is shown in a tab that isn't open when opening an editor, and has validation errors/warnings would remain invisible until the window is resized. This occurred only when using Chrome, using Firefox behaved as expected.

The expression editor now properly resizes itself when becoming visible, such that the expression is shown without needing to resize the window.



Importing a WSDL or XSD could fail if multiple schemas included the same schema file.

Duplicate schema includes are now handled as expected.


Java Runtime

Query parameters and path segments added to an AQ_RestServiceClient call would not always be URL encoded properly, causing an error when the parameter value would contain special characters, like {, } and ".

This has been fixed. Special characters are now properly URL encoded


rest service client

Using a rest service call within an automatic task and configured to authenticate via oauth2 is no longer possible due to exceptions being thrown about missing a request servlet

The oauth2 authentication implementation of rest service call no longer requires a request or response servlet to be present.


Java Runtime

Using external flows with in memory session management is not possible and results into errors when trying to start a session

Due to a spring boot upgrade external flows and the key-value redis store components where tightly coupled. This has been decoupled and should work independently again.



Hibernate would use camelCased column names by default when interacting with the database whilst the delivered database scripts would create column names in lowercase. which can lead to errors when using a database that is not case insensitive.

Fixed this making the column names of entities lowercased.


Java Runtime

When using blueriq.legacy.legacy-rest-validation, an exception is thrown if a value is invalid according to the field validations.

The REST service client will now fail with the field validation's message instead of failing with an unexpected exception. To fully disable including field validations for REST responses, the new legacy toggle blueriq.legacy.legacy-rest-response-validation has been introduced that needs to be enabled in addition to .blueriq.legacy.legacy-rest-validation



When getting hibernate properties for the sql stores, we would iterate multiple times over all available properties to filter out hibernate properties.

Fixed this by checking if a property is relevant and immediatelly processing it.

11. Known issues

For an overview of known issue please refer to: Known issues