You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. New
1.1. PostgreSQL 16 support
Support has been added for PostgreSQL 16, the latest PostgreSQL major version. This is added next to version 15 which already is supported. For a complete overview of our supported (database) platforms, please see Platform support
1.2. JBoss EAP 8 support
Support has been added for JBoss EAP 8. For a complete overview of our supported platforms, please see Platform support.
1.3. Multi select in Blueriq Encore
1.3.1. Multi open and delete from the navigation panel
Opening and removing multiple items at once from the navigation panel is now possible, which potentially saves many clicks. Other actions, such as moving multiple items at once are planned to be implemented at a later stage.
1.3.2. Multi delete from the page and container editor
Removing multiple items from a page or container can now be done easily in Blueriq Encore:
Other actions will follow later.
1.4. Autosuggest and highlighting for Text Substitution Language (TSL) in Blueriq Encore
We have added support for autosuggest, ctrl+click navigation, and syntax highlighting for Text Substitution Language (TSL) in Blueriq Encore.
Feature | Studio client | Encore >= 16.4 AND < 16.9 | Encore >= 16.9 |
---|---|---|---|
Model validations | |||
Update references after a rename | |||
Autosuggest | * | ||
Ctrl+click navigation | * | ||
Syntax highlighting | * |
1.5. Transactional indicator for subflows in Blueriq Encore
Subflows that are transactional are now indicated as such:
2. Enhancements
Enhancement | Details |
---|---|
DCM Maintenance App Multitenancy support |
The DCM Maintenance App now supports multi-tenancy. You can find more information on how to configure multi-tenancy for the DCM Maintenance App here: Multi-tenancy for the DCM Maintenance App. If you use the DCM Maintenance App you can find the configuration changes in the upgrade instructions for this release. |
Retrieve Tenant ID from JWT token |
Using Multitenancy configuration, now it's possible to configure OpenID Connect, so that it will retrieve Tenant ID from JWT Token. More information in OpenID Connect - Multi-tenancy |
RabbitMQ Clustering implemented |
It is now possible to set up a RabbitMQ Cluster which enables failover. Use the property |
Improved ordering in affected element list in Encore |
Elements are now ordered alphabetically by element type, then action (deletes before creates) and then by element name. |
Added user confirmation creating a branch from the history view in Encore |
A confirmation message is now shown after a new branch has been created from the history showing that the branch has successfully been created. |
Added toolbar in document, content item, and domain schema editor |
A toolbar has been added to the document, content item, and domain schema editor which is now used for the expand/collapse all nodes in tree action. We also added the possibility to convert inline text items to reusable text items or content items. The toolbar, which is also used in the container and page editor, offers a recognizable place in which more tools can be added in a later stage. |
Automatic selection of target entities in the data mapping editor in Encore |
After selecting a data mapping rule of type direct or join, the target entity will now be selected automatically, saving a user click. |
Moved data mapping test panel to bottom drawer in Encore |
The test panel of the data mapping editor has been moved to the bottom drawer for a more consistent user experience. |
Bottom drawer is not automatically collapsed when returning to a view |
When the bottom drawer has been expanded in a particular view, navigating away from that view and then returning will now show the bottom drawer in its expanded state, instead of having been collapsed automatically. |
Dcm Maintenance app: button to schedule the oldest open automatic task of a case |
It is now possible to schedule the oldest open automatic task of case in the maintenance app. This is useful when you don't want to wait on the case engine to schedule it after an action. |
Date/time handling was performance optimized in the Runtime |
Improved the performance of most Blueriq date and time functions. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Upgrade Instructions
See Release 16.9 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.
5. Artifacts
The Blueriq artifacts are available under name: 16.9.0.2013
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 4.4.2 |
DCM Lists Service | 3.0.15 |
Material Theme | 1.3.3 |
Development tools frontend | 1.6.0 |
DCM Maintenance App | 4.0.4 |
Audit Consumer | 0.4.4 |
DCM Dashboard Service | 1.0.4 |
Gateway Service | 0.3.3 |
Document Renderer | 2.1.0 |
6. Blueriq Libraries
There are no specific Library updates for this release.
7. Changes Platform Support
Our Platform support is updated.
Changes are:
- Support added for PostgreSQL 16 (more info under "new" chapter)
- Support added for JBoss EAP 16 (more info under "new" chapter)
- Dropped support for Windows Server 2019
- Dropped support for .NET framework 4.7.2 (every supported OS has a higher version .NET version by default)
8. 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.
9. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
10. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
BQ-22351 |
|
A CVE was detected on the spring framework library for version lower than 6.1.3, 6.0.16 and 5.3.31. See [CVE-2024-22243: Spring Framework URL Parsing with Host Validation |
We've updated our latest components to spring-boot 3.1.9, which contains spring framework 6.0.17. Older components are updated to spring framework 5.3.32 |
BQ-22258 |
|
When a lock is created in the database (manually) and you try to remove this, an error occurs |
Operations on the maintenance API that change data also update the DCM lists. To do this, the outbox is used which requires an existing transaction. In this case the operation to remove a lock was not transactional, leading to an error with the outbox. The method is now made transactional to fix this. |
BQ-22256 |
Material |
Nested external flows are started on the incorrect runtime when no base url is configured in the connection properties. |
Nested external flows are now started on the correct runtime. |
BQ-22247 |
Material |
External flows that do not have a base url configured in the connection properties are not closed, resulting in unnecessary leftover sessions |
External flow sessions are now correctly closed even when there is not base url configured. |
CSD-5124 |
JAVA Runtime |
Project initialization could be slow with many flows |
In addition to the improvements that were released in the previous patch, further optimizations have been identified and applied |
CSD-5094 |
JAVA Runtime |
The Esapi dependency that was packaged with Blueriq was not jakarta namespace compatible. |
We moved to the recently release jakarta namespace compatible version of the Esapi dependency. |
BQ-22108 |
|
In some circumstances, it is possible that a startTask lock is left in the database. This is a problem as it prevents that task from being started again. |
As startTask locks only exist to prevent automatic tasks from being started twice, it is ensured that they are always deleted directly after that check. |
CSD-5081 |
|
There are two issues here. When switching pages in the case locks tab, the requests to the backend in the maintenance app are not created properly, which causes duplication in the requests. This did not influence the behavior. The other issue was that case locks occurred on different pages. This only happens when the column that was used to sort the locks would contain duplicates. (then the sorting would show unexpected behavior). |
The first issue is solved by removing the duplication from requests when switching pages. The second issue was solved by adding a second sorting option to always sort on the unique identifier such that the default sorting can fallback when the default sorting row contains duplicates. Other pages in the maintenance app contained the same issues and are also solved. |
CSD-5048 |
|
When the case engine completes a task and fails during that transaction everything except the case locks action will be rolled back as they are outside this transaction. |
Added a custom rollback mechanism that rollbacks the release of case locks at the end of the transaction should it fail. |
CSD-4835 |
Encore |
In datamappings, the distinction between the first source collection and the additional source collections was not clear. |
Changed the appearance of the source collections so that it is now clear that the additional source collections are different from the main source collection, and updated the documentation to clarify the difference. |
BQ-19477 |
JAVA Runtime |
When using external flows with an in-memory store, it was impossible to set the session timeout, even when following the instructions in the related warning in the log. |
It is now possible to set the session timeout for external flows when using an in-memory store, by using the server.servlet.session.timeout property. |
BQ-19471 |
JAVA Runtime |
When using the external flow with an in-memory store, stored data could in very rare cases disappear under high load. |
We fixed the underlying issue that caused the data to disappear. |
11. Known issues
For an overview of known issue please refer to: Known issues