You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. New
1.1. Webservice debugging
In previous versions of Blueriq Encore, the data mapping simulator and quick test with integrated expression evaulator have been added. In the current version of Blueriq, debugging capabilities have been extended even further, with the possibility to retrieve the profile at any point during a webservice invocation (both SOAP and REST) using the newly introduced debug logpoints. These points can be set where the word "Profile" is used in the chart below or at any point within a flow. When calling a Blueriq as a Service provided with these logpoints in the header, the runtime will log the profile in a separate log file when it passes a logpoint. The profile can be imported into Blueriq Encore to be used with the data mapping simulator or quick test.
This means that there is no need to model debug pages to retrieve the profile, which is less time-consuming, less error-prone, and more secure.
Detailed information about logpoints can be found here.
1.2. Document import in Encore
Importing a docx file and converting it to a content item or document while mapping styles can now be done with a few steps in Blueriq Encore. This saves time and facilitates cooperation between the business and Business Engineers.
1.3. Added tools in document and page editor in Encore
In addition to the tools we've added in Blueriq 16.9, we've added more tools to offer a smoother modelling experience.
It is now posible to:
- merge an inline text item in the document and content item editor with its next sibling using the merge button: .
- group and ungroup items in the page and container editor.
1.4. External flow contract
In Blueriq 16.10, we introduced a new, versioned data contract for the External Flow functionality. By implementing a versioned contract, we resolve the former limitation that the host and the target runtimes had to have the same Blueriq version (major and minor, patch and java) until Blueriq 16.10. From Blueriq 17 onwards, we aim for External Flow to always be backwards compatible with the previous major release.
Customers that implement custom authentication or a custom IExternalFlowStore
should follow the upgrade instructions.
2. Enhancements
Enhancement | Details |
---|---|
Document renderer client Multitenancy support |
The document renderer now supports multi-tenancy for images. Different images can now be configured per tenant. You can find more information on how to configure multi-tenant images in the Document renderer client here: Multi-tenant Document Renderer Client component. |
Gateway Service Single Sign On support |
The Gateway Service now support Single Sign On. By doing so we have update the configuration of the Gateway service and created upgrade instructions to guide the transition. |
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:
- The PostgreSQL driver version has been updated from 4.6.x to 4.7.2 due to CVE-2024-1597.
- Added platform support for Oracle Database 23c.
5. Upgrade Instructions
See Release 16.10 Upgrade Instructions for the 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: 16.10.0.2118
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 4.5.1 |
DCM Lists Service | 3.1.1 |
Material Theme | 1.3.3 |
Development tools frontend | 1.7.0 |
DCM Maintenance App | 4.1.2 |
Audit Consumer | 0.5.1 |
DCM Dashboard Service | 1.1.1 |
Gateway Service | 0.4.2 |
Document Renderer | 2.1.0 |
7. Blueriq Libraries
There are no specific Library updates for this release.
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-22577 |
Java Runtime |
CVE-2024-28752 was detected on the org.apache.cxf:cxf-core-3.5.6 library |
Resolved by updating the library to version 3.5.8 |
BQ-22676 |
Java Runtime |
CVE-2024-29025 was reported for the Netty dependency in the Runtime. | The Netty dependencies have been updated to address the CVE. |
CSD-5176 |
Encore |
In the AQ_Instance_Create and AQ_Instance_Update editors, unsetting an attribute/relation assignment would not clear its expression, resulting in a validation error that the expression must be empty. |
The value expression of an attribute/relation assignment is now automatically cleared when clearing the assignment. |
BQ-22155 |
DCM Maintenance App |
When a failed message was parsed containing dates in epoch timestamp form, the DCM Maintenance App frontend would show a generic error message. |
Timestamps are now parsed to a date before showing the message. |
CSD-5156 |
Java Runtime |
In Blueriq 16.9 the date/time handling was performance optimized. As an unexpected side effect, the handling of historical dates (before the Gregorian calendar was in existence) could be incorrect because Julian and Gregorian date handling was sometimes mixed up |
As a short term fix, the changes made in Blueriq 16.9 have been reverted |
BQ-22383 |
|
CVE-2024-1597 has been detected on PostgreSQL JDBC driver 42.6.0. |
The PostgreSQL JDBC driver has been updated to version 42.7.2. If you use an external application server (JBoss for example), please make sure that the driver is up-to-date. |
CSD-5130 |
Java Runtime |
Some items inside the DRD of the runtime are partially visible |
All items in the DRD are now fully visible |
11. Known issues
For an overview of known issue please refer to: Known issues