You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. New
2. Enhancements
| Enhancement | Details |
|---|---|
| Display task name on action button |
In a worklist it is possible to add an action button to start a task. Besides a button with a fixed name, there is now an option to use the display name of the task as well. When this option is toggled in encore, the display name of the task is used as button caption in the worklist. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Upgrade Instructions
See Release 17.7 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-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: 17.7.0.???
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 5.0.6 |
| DCM Lists Service | 4.0.6 |
| Material Theme | 1.3.5 |
| Development tools frontend | 2.0.1 |
| DCM Maintenance App | 5.0.8 |
| Audit Consumer | 1.0.6 |
| DCM Dashboard Service | 2.0.3 |
| Gateway Service | 1.1.2 |
| Document Renderer | 2.2.2 |
6. Blueriq Libraries
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 |
|---|---|---|---|
|
BQ-24170 |
Encore |
The entity editor would not restore the scroll position of the attribute and relation lists when switching between views. |
The scroll position is now restored as expected. |
|
CSD-5706 |
Encore |
Various dropdowns could be inadvertently clipped, preventing the ability to scroll. |
Some dropdowns have been updated to be positioned in front of their container, avoiding the clipping issue. |
|
BQ-24155 |
|
The default error exchange for the DCM Lists Service RabbitMQ connection had the wrong value. |
It now references the right exchange. |
|
BQ-24138 |
Encore |
It was possible to model service and function calls in contract modules in Encore even though this is not allowed |
Removed the ability to model service and function calls from contract modules in Encore |
|
BQ-24084 |
Studio |
An error could occur when importing certain Word documents. |
The error has been addressed. |
|
BQ-24079 |
|
When a retry event node is taken, the task lock is also removed. |
The task lock is now kept so the retry can happen using the same task lock and happens immediately. |
|
CSD-5650 |
Studio |
The Studio server could incorrectly detect a cycle in process type restrictions, even if the structure of process types was not actually cyclic. |
The cycle detection has been improved to avoid the false positive. |
|
BQ-24064 |
|
In some setups, the AQ_MailService service call would always fail when trying to send an email because of missing runtime dependencies due to changes in third party libraries. |
The AQ_MailService has been fixed by providing the right dependencies. |
|
BQ-24056 |
Studio Backup Tool |
CVE-2024-47554 was reported on a dependency (commons-io) of the Studio Backup Tool |
The dependency has been updated to the latest version, which contains a fix for the CVE |
|
CSD-5608 |
Encore |
Various process validations were missing in Encore:
|
All of these aspects are now validated in Encore, enabling feedback during modelling for situations that would be reported as error in the runtime |
|
BQ-23739 |
Java Runtime |
When using external flows the target runtime didn't get any notification upon closing the host session. This meant that when a session on the host runtime is closed, the target runtime external sessions weren't closed |
Implemented a Listener which sends a notification to the target runtime when a host sessions gets closed |
10. Known issues
For an overview of known issue please refer to: Known issues
11. Security notification
Overview
Content Tools