You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
1. Artifacts
The Blueriq artifacts are available under name: 15.10.1.872
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 4.1.5 |
| DCM Lists Service | 2.2.7 |
| Material Theme | 1.1.0 |
| Development tools frontend | 1.3.0 |
| DCM Maintenance App | 2.1.13 |
| Audit Consumer | 0.1.6 |
| DCM Dashboard Service | 0.1.0 |
| Gateway Service | 0.1.0 |
2. Aquima Libraries
The Aquima Library has been updated, see below what has changed:
3. 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 1 |
Version in 2 |
|---|---|---|---|---|
|
redis.clients |
3.8.0 |
|
||
|
io.lettuce |
|
6.1.10.RELEASE |
4. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
5. Bug fixes
|
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
|
BQ-18843 |
Encore |
When editing a domain schema in Encore, the "Is root element hidden" checkbox would reset to be disabled |
The "Is root element hidden" checkbox is now properly saved after editing a domain schema |
|
CSD-4484 |
Runtime |
Log became polluted in some cases when creating a session with the ExternalFlow profile active. |
Lowered the log message to level Debug, and included the exception so the cause can be identified. |
|
CSD-4510 |
Audit Consumer |
Using encrypted properties in the Audit Consumer is not possible. |
Added the feature the set encrypted properties using the already available Property Encryption method. |
|
CSD-4527 |
Document Renderer |
Images provided with the DPI styling were not always rendered correctly. |
An issues was found in our document rendering library, which has been fixed in a later version that is now included. |
6. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools