You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. New
1.1. DCM Dashboard release
In this Blueriq release the DCM Dashboard feature for Case Modelling is unveiled as being ready for use. Since the first beta versions started coming out in Release 15, slowly it has been worked up to being ready for production.
DCM Dashboards boast some completely new features, both technically and functionally:
- Technically is failover ready, which means that if you run your Blueriq Case Modelling solution in a failover setup you can benefit from no session losses for your end users.
- Functionally it provides in new native concepts that aim to provide Blueriq platform users more out of the box capabilities and ease of modelling and lower maintenance effort
- DCM Dashboards are not executed in the Runtime, which lowers the Blueriq infrastructural footprint.
- A new Security gateway is introduced supporting OIDC using JWT and Keycloak
- New implementation components (dcmwidget flow, events, task execution services) make the life of the Business Engineer much easier by making a lot of 'plumbing code' obsolete.
- New dashboard configuration in Encore
Next up for DCM Dashboarding: automated development time dashboard reloading for the Business Engineer. This will help the Business Engineer by elimination the manual step of exporting the DCM Dashboard project xml and placing it in the Dashboard backend.
1.2. DCM Dashboard modelling
1.2.1. Model your DCM dashboards in Encore
It has been long coming. After we first released the DCM Dashboard backend to execute the dashboard application, back then the application had to made by writing the json file. Now we have created the configuration pages in Encore. And the application can be easily exported in the regular xml format that is also used for normal project exports. The DCM Dashboard in the projects overview in Encore as a new project type.
1.3. DCM Dashboard changes
1.3.1. New Export format
The DCM Dashboard Service used to support a JSON export format, this was the only way to create a dashboard. With Blueriq 16.7 we are releasing the functionality to model a dashboard by using Encore. By introducing dashboard modelling in Encore we have also added a new export format that be downloaded the same way as you export your projects right now.
The Encore export format will be only supported format from now on and is available in the 0.4.0 and 1.0.0 of the DCM Dashboard Service.
1.4. Runtime changes
1.4.1. Last updated field is now a filterable column in the CaseList
The Case List is extended with a last updated field which can be shown in the list and also filtered on. The last updated field is updated whenever the case is updated, which currently means after completing a task for the case.
1.5. Quick test in Blueriq Encore
You are now able to get insight into how an attribute is sourced by the rule engine, given a profile and the business rules in your model. This will help you, as a business engineer, to:
- understand backward chaining
- quickly test and debug logic
- debug a unit test
- quickly create profiles for unit tests (see video below)
2. Enhancements
| Enhancement | Details |
|---|---|
| The Case Engine outbox poller supports multitenancy. |
It's now possible to use the Case Engine outbox poller in a multitenant environment. It's also possible to change the interval in which the outbox poller publishes messages from the outbox(es) to the message broker. For more information see: Outbox poller |
| JsonPath expressions for JWT claim paths |
Until Blueriq 16.7, paths to JWT claims would be expressed by comma-separated path elements in configuration files. In Blueriq 16.7, we replaced these expressions by JsonPath expressions to allow more flexibility. We applied this change in the Runtime, the DCM Maintenance app and the DCM Dashboard service. For more information, please refer to the upgrade instructions. |
| Added exit events for error handling in AQ_RestServiceClient service call |
Two new exit events have been added to AQ_RestServiceClient that simplify error handling:
Make sure to use BlueriqBasicModelling Library 1.0.2 to use thes exit events. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics
4. Upgrade Instructions
See Release 16.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: 16.7.0.1843
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 4.3.6 |
| DCM Lists Service | 3.0.12 |
| Material Theme | 1.3.0 |
| Development tools frontend | 1.6.0 |
| DCM Maintenance App | 3.1.0 |
| Audit Consumer | 0.3.4 |
| DCM Dashboard Service |
1.0.0 |
| Gateway Service | 0.2.4 |
| Document Renderer | 2.0.1 |
6. Blueriq Libraries
There are updates in two libraries:
BlueriqBasicModelling Library 1.0.2
BlueriqDocumentModelling Library 1.1.0
The package can be downloaded here:
BlueriqCompleteLibraryPackage.package.zip
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
8.1. DCM Dashboard JSON export format removal
With the introduction of the Encore export format, we have removed the JSON export format from the 1.0.0 version of the DCM Dashboard Service. To support a transition period the 0.4.0 version of DCM Dashboard Service will contain both export formats.
For a full list of deprecated features, go to Deprecated features.
9. Bug fixes
|
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
|
CSD-5034 |
flow |
Adding nodes, inserting waypoints and moving connectors in the flow, process and ERD editors would work incorrectly when a scroll offset was applied |
The scroll offset no longer results in incorrect positions |
|
BQ-21733 |
|
CVE-2023-6378 has been detected on the logback-core dependency. |
Updated logback-core to the latest version. |
|
BQ-21719 |
|
|
Reaching the final page will show the actual validation status and will no longer include disabled pages nor will disabled pages be reachable when pressing the previous button |
|
CSD-5018 |
Encore |
Disabling restrictions for a content style did not clear existing restrictions, possibly reporting an error that could only be fixed by enabling restrictions again, then manually removing the restrictions. A similar problem existed for AQ_Instance_Update service calls, where disabling the instance selection did not clear the instance selection expression. |
The restrictions are now cleared when disabling restrictions and the editor will now show the list of restrictions if an error is reported for them, even when restrictions are disabled. Likewise for the AQ_Instance_Update editor |
|
BQ-21432 |
JAVA Runtime |
In a multitenant environment, when a AMQP message listener or publisher throws an exception it does not publish the message correctly to the DCM Maintenance App. |
The tenant id has been added to the message and the tenant aware message recoverer uses this header to determine the exchange to publish the message to. |
|
CSD-4960 |
|
Working with large lists (for example as a result of a expression) was slower then expected in certain specific situations |
Improved the speed of adding values to a single list by grouping them together and adding them all at once |
|
BQ-20919 |
development dashboard |
It's not always clear (in development mode) from which files the shortcuts for the applications are read from and written to by the Runtime Development Dashboard. |
It is more clearly stated in the Runtime Development Dashboard that the 'shortcuts' profile needs to be enabled or else shortcuts from the application-shortcuts.properties file will not be loaded by the Runtime and thus not be shown inside the shortcuts widget on the dashboard. |
|
PUB-404 |
Java Runtime |
When using the 'pgsql.sql' script to create the tables for the Publisher client and setting 'blueriq.hibernate.publisher-client.hbm2ddl.auto' to 'validate', the Runtime does not start complaining about column types that should be 'oid' instead of 'bytea'. |
Changed the mapping so that it matches the Database schema |
10. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools