You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. New
1.1. Unsaved changes warning when leaving Encore
The probability of accidentally losing unsaved changes in Encore have now reduced significantly. If there are unsaved changes and the user wants to close the browser tab or switch to another repository or branch, the user will be notified after which it is possible to proceed or cancel the action.
1.2. Multi-move in Encore
Elements can now be moved from one module to another in bulk, making refactoring cheaper. Compared to a one-by-one move, the multi-move saves the business engineer (n*5)-7 clicks, where n = the number of elements to be moved to the same target module. So, for 10 elements, the multi-move saves 43 clicks. For 50 elements, the multi-move saves a whopping 243 clicks!
2. Enhancements
| Enhancement | Details |
|---|---|
| Move-button in title bar in Encore |
It is now possible to move an element to another module from the element itself using the move-button in the titlebar. |
| Inserting containments, document nodes and domain schema properties from the toolbar |
The page & container editor, the document & content item editor and the domain schema editor have been updated to enable easier insertion of new items. Previously in Encore, the insertion button was hidden within each individual row, only becoming visible upon hover. For each row you had to reselect the desired item type to add, and it wasn't possible to insert an item before. These pain points have been addressed by adopting the UI from the old Studio client: item insertions are back in the toolbar, with only a single dropdown to select the type and the ability to insert before and after the selected item. |
| Extended value list validation in expressions |
Encore now verifies that literal values within a set are compatible with the value they are compared against, if that value has a value list. This surfaces potentially inaccurate logic, typos or outdated logic. Furthermore, Encore now suggests value list values within a set literal. |
| Authorization for backup and restore in Encore |
Creating and restoring backups can now only be done when a user has administrator rights. Creating backups of single repositories from the navigation panel, for example for support purposes, can still be done for each repository if the user has repository management rights and access to the repository. |
| Ability to import a quick test profile from clipboard |
The quick test panel now enables you to import a profile XML directly from your clipboard, intended to help inspect profiles that have be copied from the debugger log that was introduced in the 16.10. This avoids you from having to save the profile to a separate file yourself to then import into Encore, this can now be done without the intermediary file. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Upgrade Instructions
There are no specific 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.
5. Artifacts
The Blueriq artifacts are available under name: 16.11.0.2217
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 4.5.2 |
| DCM Lists Service | 3.1.2 |
| Material Theme | 1.3.3 |
| Development tools frontend | 1.7.0 |
| DCM Maintenance App | 4.1.4 |
| Audit Consumer | 0.5.3 |
| DCM Dashboard Service | 1.1.3 |
| Gateway Service | 0.4.5 |
| Document Renderer | 2.2.0 |
6. Blueriq Libraries
There are no specific Library updates for this release.
7. 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.
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-5222 |
Java Runtime |
Creating a custom API renderer causes an exception when the Runtime is started stating that there are multiple API renderer factories where only one is expected. |
We made sure that the composite API renderer factory is injected at startup. The composite API renderer will then look up the custom renderers. |
|
BQ-22898 |
Studio |
If a migration change exists for a removed element, committing changes would fail if the delete itself was not included in the commit. |
The migration change can now be committed without having to select the user change as well. |
|
BQ-22868 |
Java Runtime |
CVE-2024-22262 has been detected on the Runtime and services. |
For 16, it's addressed by upgrading spring-framework to 6.16. For 15 and 14 it's addressed it by upgrading spring framework to 5.3.34. |
|
BQ-22867 |
Java Runtime |
CVE-2024-29857, |
Addressed by upgrading bouncy castle to 1.78. |
|
CSD-5229 |
Encore |
Encore would incorrectly inherit a value list association from the first value in the set. |
The type of a set is still determined by the first item, but its value list is not inherited. |
|
CSD-5213 |
Java Runtime |
The AQ_Timeline container would search and retrieve all timeline entries in the database if the case id or user id parameter resulted in an empty list. This could lead to possible memory and security issues. |
The AQ_Timeline container will now not perform a search at all when the case id or user id paramater results in an empty list and will show an empty timeline. The reason why a timeline container is empty will now be logged. |
|
CSD-5202 |
Studio |
Restoring a backup would only report an error in the log when a repository could not be restored, while the restore request would succeed without indicating that the backup hadn't been fully restored. |
An error response with status 500 is now returned to indicate that the backup could not be fully restored. |
|
BQ-22359 |
Java Runtime |
The Runtime was not propagating b3 multi headers properly to other services which made the log correlation not work. |
Fixed the Runtime to properly propagate the b3-multi headers by enabling spring to automatically add instrumentation to requests that are made to other services. |
10. Known issues
The AQ_DocumentLink container does not work in this version. We're aware of the issue and working on a solution.
For an overview of known issue please refer to: Known issues
Overview
Content Tools