You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
2. Enhancements
| Enhancement | Details |
|---|---|
| Started tasks in AQ_TaskList | Before this release, containers of type Container type: AQ_TaskList would always show started tasks. Analogous to the AQ_WorkList, this behavior is now configurable in Studio. |
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.
4.1.1. Additions
- Redis 6.0
- Websphere Liberty Core 20.0
4.1.2. Removal
- Redis 3.2
- Redis 4.0
- Websphere Liberty Core 19.0
5. Upgrade Instructions
The upgrade instructions for release 13.3 can be found here.
As a best practice
- backup your repository
- backup your database before running scripts
- backup your
spring.config.additional-locationdirectory ([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: 13.3.0.1596
7. Aquima Libraries
For release 13.3 there are no specific Library updates.
8. Libraries
In this release, the set of third party libraries that is used by Blueriq was updated. When your installation of Blueriq includes custom components (artifacts that do not ship with Blueriq, such as proprietary plugins), those components should be tested for compatibility with these changes.
9. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
10. Bug fixes
Identifier | Component | Issue | Solution |
|---|---|---|---|
BQ-10430 | Runtime | When using a container of type AQ_TaskList, newly created tasks that would be sent to the task list as a server sent event update could not be started. | This problem has been fixed. |
| BQ-10429 | Runtime | CVE-2019-14900 | Resolved by upgrading Hibernate dependency. |
BQ-10368 | Runtime | In the Development Tools V2, an error would occur when there was a project present that has a branch name starting with a digit. | This has been resolved. |
BQ-10343 | Installer | When upgrading Blueriq with the installer, the installation would end prematurely when the Mongo and/or Qpid services were still running. Running the installer a second time or manually stopping all blueriq related services would get Blueriq installed anyway. | This has been fixed, but the problem is expected to still occur when upgrading to 13.3, because the upgrade process partly relies on data that is left behind by the older installer. If you upgrade from 13.3 to a later Blueriq version (13.3.1+), the problem should be solved. |
BQ-10318 | Development dashboard, Runtime | The HATEOAS Rest endpoints for the Development Tools V2 API and the Backend Rest API would contain a local hostname in the links they provide when the Runtime would be behind a reverse proxy. | The endpoints now provide links with the hostname, port and protocol from the reverse proxy server. |
CSD-3351 | Installer | When upgrading Blueriq a message occurred that the Application Pool of Blueriq already existed, after a skip or rollback an invalid Blueriq installation was left. | When the installer now finds that the Application Pool of Blueriq already exists. The user is provided with the option to overwrite the old Application Pool of Blueriq. Doing so will result in a newly configured Application Pool and a valid Blueriq installation. When performing a rollback the installation will be cancelled, but the old installation is already deleted |
| CSD-3344 | Runtime | New target instances would not be created by a mapping, even if the 'no matching target instance'-action was set to 'Create new instance', this occurred when 'Do nothing' was chosen for the 'source matches target instance'-action. | The behavior has been changed such that a new instance is created when no matching target instance exists. |
CSD-3331 | Runtime | In the Material theme, selecting/deselecting a radio button could require the user to first click somewhere else to trigger a refresh. | A refresh is now triggered immediately upon selecting/deselecting a radio button. |
| BQ-7365 | Runtime | Studio has the concept of a persistency id, which allows replacing tasks within a process. There are places in the runtime where this concept is not used, which can cause problems if a task has been renamed. | Use the persistency id (= task node id) rather than the task name to retrieve task definitions, so even if the task was renamed the definition can still be retrieved. |
11. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools