You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. Enhancements
Enhancement | Details |
---|---|
Derived XML or JSON media types for JSON messages accepted |
For parsing a REST message, Blueriq did already support |
Context menu improvements in Encore |
|
Cursor automatically set in Encore |
In Blueriq 17.4, the behavior of automatically setting the cursor to fields upon opening an editor has been added so that the user can immediately start typing. This behavior has been expanded to more places thoughout Encore, specifically to editors with expression editors and display texts as first input, such as the button editor and the decision table. |
Entity information in attribute dropdown in Encore |
When adding a new attribute to a page or container, you can directly select an attribute and Encore will automatically select the corresponding entity. If there are multiple entities with the same attribute, it was previously not possible to see which entity the attribute belongs to. This information has now been added. This change also affects the sort ordering, as attributes are now grouped by their entity. |
Login improvements using the Gateway Service |
As of version 1.3.0 of the Gateway Service we now detect that when there is only one identity provided configured, we can skip the identity provider selection resulting in a smoother login procedure. |
2. Upgrade Instructions
See Release 17.8 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.
3. Artifacts
The Blueriq artifacts are available under name: 17.8.0.281
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 5.1.3 |
DCM Lists Service | 4.1.4 |
Material Theme | 1.5.0 |
Development tools frontend | 2.0.2 |
DCM Maintenance App | 5.1.2 |
Audit Consumer | 1.2.2 |
DCM Dashboard Service | 2.2.2 |
Gateway Service | 1.3.1 |
Document Renderer | 2.4.0 |
4. Blueriq Libraries
There are no specific library updates for this release.
5. 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.
6. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
7. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
BQ-24335 |
Gateway |
CVE-2024-38821 was detected on spring-security-web |
Upgraded the spring security libraries to the latest version |
CSD-5755 |
Encore |
Containers without container type could silently have parameters without them being used. Similarly for containers where its container type has disabled containment, yet containment could still be present in a container. |
These situations will now be surfaced through validation errors in Encore. Note that this does not prevent creating project exports, but it is recommended to remove the obsolete parameters and/or containments. |
BQ-24105 |
|
The Runtime would throw a generic RuntimeException when failing to start a task due to a caselock. This would result in a failed event in the maintenance app instead of a delayed event. |
The Runtime now throws a specific LockAlreadyExistsException which enables the maintenance app to actually save the resulting message as a delayed event |
CSD-5654 |
|
Automated tasks did not have an icon indicating their automated status. |
Automated task icon has been added. |
CSD-5603 |
|
The default mail connection configured via properties conflicted with mail connections when provided by another ConnectionManager. For example when you created your own AquimaConnectionManager or AquimaConnection. |
When creating a default mail connection we mark it as default, so it will not conflict anymore with unique mail connections provided from other ConnectionManagers |
8. Known issues
For an overview of known issue please refer to: Known issues