On this page:

1. Documentation

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

2. Upgrade Instructions

For this release there are no specific upgrade instructions.

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.

The Blueriq artifacts are available under name: 15.13.6.1547

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

For this release there are no specific Library updates.

For this release there are no specific retirement announcements.

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

Identifier	Component	Issue	Solution
BQ-20806	Encore	An inline container could be converted to a reusable container even if it had an invalid name.	An inline container is now required to have a valid name before it can be converted to a reusable container.
BQ-20788	Encore	The AQ_AggregateCount and AQ_AggregateSearch services could have a horizontal scrollbar when there were no search criteria.	The error message that reports that at least one criteria is required no longer causes undesirable scrollbars.
BQ-20591	Encore	An error would be shown after opening the history tab for an unsaved element, which would try to retrieve a history for the element, which did not exist.	History tab will no longer try to get the history for an unsaved element.
BQ-20568	Encore	When logging out, cancellation of the workspace subscription would be attempted. This was however not possible due to the user already being logged out.	Logging out the user is now performed after the cancellation of the workspace subscription.
CSD-4751	JAVA Runtime	A session would sometimes not be written to Redis yet while retrieving it after a redirect. This happens if the legacy endpoints /server/start/* are used in combination with Redis and JBoss EAP. This only happens in JBoss due to a difference in the order of marking the request response as complete between Tomcat and JBoss.	We now manually flush the session after session creation to make sure that the flush happens before the marking the request as finished.

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