You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
| Release Date | |
|---|---|
| Content | Release 14.6 |
| Download |
1. New
1.1. DCM Lists Component
DCM-Lists is part of the new DCM (Case-Modelling) solution, and only available in Blueriq 15.13 and up. For more information, please check the Blueriq latest spaces.
To accommodate DCM 2.0 and improve separation of concerns, the DCM Lists Component has been split into two modules: The DCM Lists Client Component and the DCM Lists Publisher component. The DCM Lists Client Component is responsible for retrieving list data and presenting it to the user while the DCM Lists Publisher Component is responsible for updating the DCM Lists Service with case or task changes.
1.2. Timeline SQL Store Component
Until this release, the Trace SQL Store component was needed to provide SQL storage for both Trace information and Timeline information. This tight coupling could lead to some unwanted side effects:
- It was not possible to store either Trace information or Timeline information. Both had to be enabled, which would cause unnecessary data to be stored.
- When Trace information was traced using the Trace Event Publisher Component, it would not be possible to store and retrieve Timeline information in a database.
In this release, we separated the timeline data storage from the Trace SQL Store component to the Timeline SQL Store component, to provide a greater flexibility in configuring trace and timeline separately.
Check the linked pages and the Release 14.6 Upgrade Instructions for more information on how to configure the timeline separately from the trace.
Note that there are some backwards compatibility measures in place, so if you have a project that doesn't contain custom code, the trace and timeline storage will behave like they did before.
1.3. Blueriq Development Dashboard - New widget
In this blueriq version we added a new widget to the Runtime Development Dashboard; the Exposed Blueriq functions. It works equal to the Exposed Blueriq webservices widget. The new function widget helps you get the url and parameters for the functions that you explicitly want to expose 'as a webservice' for testing purposes. More information about Functions can be in this section: Functions and function calls.
On this page:
2. Enhancements
| Enhancement | Details |
|---|---|
| DCM_ExecuteTask service type for DCM 2.0 | For use in DCM 2.0, we have introduced the Service call type: DCM_ExecuteTask service call. In the near future the behavior shall be changed, but at this moment the behavior is identical to the AQ_ExecuteTask service call. |
Running external themes from the development dashboard | We have introduced the option to run applications from the development dashboard via custom themes, which are not prepackaged with the Blueriq Runtime. More information regarding this topic can be found in the documentation about the new development dashboard. |
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 with the following changes:
4.1. Additions
- Oracle JRE 17 (21.9)
- Azul Zulu OpenJDK 17
4.2. Removals
- Oracle JRE 16 (21.3)
- Azul Zulu OpenJDK 16
5. Upgrade Instructions
There are upgrade instructions for this release.
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: 14.6.0.4115
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 3.4.1 |
| DCM Lists Service | 1.4.1 |
| Material Theme | 1.0.40 |
| Development tools v2 | 1.1.0 |
7. Aquima Libraries
The Aquima libraries are updated, see below what has changed:
8. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
9. Bug fixes
Identifier | Component | Issue | Solution |
|---|---|---|---|
CSD-3910, CSD-3901 | JAVA Runtime | When the development-tools profile was enabled, but no studio connection was configured, a NullPointerException would show in the log. | The NullPointerException will not occur anymore when no studio connection has been configured. |
BQ-13973 | When using DCM 2.0 and when throwing a message event with a parameter with type date or datetime, the date value would not be interpreted as a correct value. | This has been fixed. | |
CSD-3900 | JAVA Runtime | Validations added to a header, fragment or argument of a REST message were ignored. | When a REST message has no body, the validation of headers was skipped. It is now checked that if the message has no body, headers, fragments and arguments are still validated. |
BQ-12525 | When the External Flow profile was enabled, but the license didn't allow the usage of External Flow, Blueriq would not start. | Blueriq is now always able to start with the External Flow profile enabled, but will report a fatal error for applications that actually contain External Flows. |
10. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools