You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. Highlights
Our goal is to swiftly introduce new features, prioritizing speed over waiting for major releases unless absolutely necessary. This approach ensures a gradual impact and shortens time to market. Unlike minor updates, major releases may involve breaking changes like removing outdated features or upgrading technology.
Highlights of release 17.0:
- Technology upgrades (JDK 21, OpenAPI 3.1, Keycloak 24.0, .NET 8) keeping Blueriq secure and stable.
- Removal of deprecated features, toggles, and properties marking the end of a transition period.
- Improved flexibility for secured REST connections using OAuth2
- Improved readability of logging
2. Enhancements
| Enhancement | Details |
|---|---|
| OAuth2 clients a la Spring Security | We changed the way you configure an OAuth2 client on REST connections. Now you can define OAuth2 clients separately and reference them from multiple connection if desired.
|
| Default HTTP timeouts | The default read timeout for AQ_RestServiceCall and AQ_SoapServiceCall has been changed to 5 seconds (was 15 seconds). The advantage is that a request will now fail faster if it takes long, so that the user doesn't have to wait so long. If you have service calls that take longer than 5 seconds, you can override the timeout per connection. See Connections Properties for more information. |
| Timeouts for CMIS | We introduced properties to set the connection timeout and the read timeout for CMIS. Both default to 5 seconds. See CMIS Properties on how to change them. |
| Improved readability of logging | Logging for flows, processes, and certain service calls throughout Blueriq applications has been improved by improving the consistency of log levels and actual log statements. |
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:
- Blueriq Java components now require Java 21 to run.
- Oracle 21C (Innovation Release)
4.1. Discontinued
- Java 17 support is stopped, from Blueriq 17 onwards Java 21 or higher is mandatory.
5. Upgrade Instructions
OAuth2 token support on REST connections
In order to use your REST connections that use a OAuth2 token to authenticate correctly, after the upgrade you will need to migrate all the properties to the new structure as described in the "OAuth2 clients a la Spring Security" enhancement.
Please review the Release 17.0 Upgrade Instructions.
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: 17.0.0.33
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 5.0.1 |
| DCM Lists Service | 4.0.0 |
| Material Theme | 1.3.3 |
| Development tools frontend | 2.0.0 |
| DCM Maintenance App | 5.0.1 |
| Audit Consumer | 1.0.1 |
| DCM Dashboard Service | 2.0.1 |
| Gateway Service | 1.0.1 |
| Document Renderer | 2.2.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.
ArtifactId | GroupId | License | Version in 16.11 | Version in 17.0 |
|---|---|---|---|---|
org.glassfish | 4.0.2 |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty.incubator | 0.0.62.Final |
| ||
io.netty.incubator | 0.0.62.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.netty | 4.1.108.Final |
| ||
io.projectreactor.netty | 1.1.18 |
| ||
io.projectreactor.netty | 1.1.18 |
| ||
io.projectreactor.netty | 1.1.18 |
| ||
io.projectreactor.netty.incubator | 0.1.18 |
| ||
org.springframework | 6.1.6 |
| ||
com.fasterxml | 1.3.1 | 1.3.2 | ||
org.jfrog.artifactory.client | 2.13.1 | 2.17.0 | ||
org.jfrog.artifactory.client | 2.13.1 | 2.17.0 | ||
org.jfrog.artifactory.client | 2.13.1 | 2.17.0 | ||
org.apache.commons | 3.13.0 | 3.14.0 | ||
com.google.zxing | 3.5.1 | 3.5.3 | ||
org.apache.cxf | 3.5.8 | 4.0.4 | ||
com.fasterxml.jackson.core | 2.15.4 | 2.17.0 | ||
com.fasterxml.jackson.core | 2.15.4 | 2.17.0 | ||
com.fasterxml.jackson.core | 2.15.4 | 2.17.0 | ||
com.fasterxml.jackson.dataformat | 2.15.4 | 2.17.0 | ||
com.fasterxml.jackson.dataformat | 2.15.4 | 2.17.0 | ||
com.fasterxml.jackson.datatype | 2.15.4 | 2.17.0 | ||
com.google.zxing | 3.5.1 | 3.5.3 | ||
org.bitbucket.b_c | 0.9.4 | 0.9.6 | ||
org.jsoup | 1.16.1 | 1.17.2 | ||
org.apache.olingo | 4.9.0 | 5.0.0 | ||
org.apache.olingo | 4.9.0 | 5.0.0 | ||
org.apache.olingo | 4.9.0 | 5.0.0 | ||
org.apache.olingo | 4.9.0 | 5.0.0 | ||
io.projectreactor | 3.6.5 | 3.6.4 | ||
net.sf.saxon | 11.6 | 12.4 | ||
org.springdoc | 2.1.0 | 2.4.0 | ||
org.springdoc | 2.1.0 | 2.4.0 | ||
org.codehaus.woodstox | 4.2.1 | 4.2.2 | ||
io.swagger.core.v3 | 2.2.9 | 2.2.21 | ||
io.swagger.core.v3 | 2.2.9 | 2.2.21 | ||
io.swagger.core.v3 | 2.2.9 | 2.2.21 | ||
com.fasterxml.woodstox | 6.5.1 | 6.6.1 | ||
org.xmlresolver | 5.2.1 | 5.2.2 |
9. Retirement announcement
For a full list of deprecated features, go to Deprecated features.
Removed legacy properties can be found in the Release 17.0 Upgrade Instructions.
10. Bug fixes
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
BQ-22611 |
|
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 |
Starting in Blueriq 17.0, historic dates (before 15-10-1582 Gregorian) are interpreted and formatted using the (proleptic) Gregorian calendar rules instead of the Julian calendar rules. |
11. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools