You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
1. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
2. Upgrade Instructions
For this release there are no specific 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.
3. Artifacts
The Blueriq artifacts are available under name: 15.13.4.xxxx
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 4.1.8 |
| DCM Lists Service | 2.4.2 |
| Material Theme | 1.1.9 |
| Development tools frontend | 1.5.3 |
| DCM Maintenance App | 2.1.19 |
| Audit Consumer | 0.1.9 |
| DCM Dashboard Service | 0.1.3 |
| Gateway Service | 0.1.5 |
4. Libraries
For this release there are no specific Library updates.5. Retirement announcement
For this release there are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
6. Bug fixes
|
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
|
CSD-4809 |
Encore |
Editing the deprecated Action field of a button in a container would not be detected as change. |
Editing the Action field now correctly updates the value, allowing the change to be saved. |
|
CSD-4808 |
Fileupload |
Rendering a single File Upload container results into an error which cannot be fixed. |
Fixed a unexpected error when loading the maxFileAmountDescription from @blueriq/angular, causing an infinite loading for the single File Upload container |
|
BQ-20543 |
|
After login in with keycloak via the gateway a Null Pointer Expection is thrown |
Downgraded a dependency which caused the issue. |
|
BQ-20449 |
|
Newly created contract modules in runnable projects could not actually be used from data mappings, for example. |
Newly created contract modules were not added to the project's list of configured contract modules, making them effectively unavailable. Contract modules are now automatically added to a project's configuration to make them available. |
|
BQ-20364 |
Encore |
Creating elements within a project or module that has also been newly created would result in an error when the project or module is deleted before the changes have been saved. |
Unsaved changes for child elements are now correctly also dropped whenever its project or module is deleted. |
|
BQ-20362 |
Encore |
Deleting or renaming a project or module would not be applied to unsaved changes, possibly resulting in errors in certain situations. |
Deletions and renames of projects and modules are now reflected in unsaved changes as expected, avoiding any errors. |
|
CSD-4777 |
Encore |
The data mapping editor in Encore would report an error when the data mapping was created within a newly created module that had not yet been saved |
The data mapping editor can now be opened without errors again. |
|
CSD-4747 |
development dashboard |
Selected test paths are not expanded when using an external theme |
Test path where not supported yet in combination with external themes. The logic for expanding URLs in the developments have been adjusted to also expand test paths when using an external theme. This does however mean that you'll need to adjust the external theme configuration in the development-tools properties to include test paths. See [ https://my.blueriq.com/display/DOC/Development+Properties
] blueriq.external.themes.[name].template.flow on how to configure the test paths correctly. |
|
CSD-4736 |
JAVA Runtime |
Rendering a page or document with default properties results into and exception from Document Renderer Service |
This exception is thrown when the Document Renderer Service is not able to parse the XML. In this case the default value of the blueriq.document.renderer-client.tagsUppercase property was not picked up correctly, which caused the Runtime to generate a document XML which the Document Renderer Service could not parse using the default Ibex configuration which we deliver. We now set the tagsUppercase property not only by default properties, but also in code to true as default. |
|
CSD-4626 |
|
The "Import as" dropdown field was too small. |
Increased the size of the "Import as" dropdown field. |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools