You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. New
1.1. Retry events for automatic tasks
Handling automatic tasks could be difficult in DCM. For once, the task should succeed in the end. However, it could also fail. When this happens we want the task to be retried according to the configured retry mechanism.
In the current situation, a task could exit using a standard exit (commit), a cancel exit (rollback) and a technical exception exit. The cancel does not make sense, since it will just abort the task, and wait until some other action has taken place on the case. The technical exception triggers the retry mechanism. However, there is no proper way to make the task fail in a functional way. Also, no information is stored, so the task is always just executed again.
To handle automatic tasks properly, a new flow type named "ExecuteTask" is added to the BlueriqCaseModelling library. When this flow type is selected the flow will become an execute task flow and gets access to the retry event node.
During execution, when the execute task flow reaches the retry event node, the corresponding task will be handled by the retry mechanism. When the task is retried, the flow will be started with the event parameters specified in the retry event node. This way, for example, particular parts of the flow that succeeded before the functional error can be skipped based on the parameters.
2. Enhancements
| Enhancement | Details |
|---|---|
| Less clicks needed to rename an element in Encore |
The confirmation step has been removed from the rename stepper in Encore and all primary buttons in this stepper do now respond to the enter key as well, making renaming in Encore a quicker and smoother experience. |
|
|
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Changes Platform Support
Our Platform support is updated.
Changes are:
- XXX
5. 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.
6. Artifacts
The Blueriq artifacts are available under name: 17.x.x.xxxx
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 5.0.x |
| DCM Lists Service | 4.0.x |
| Material Theme | 1.3.x |
| Development tools frontend | 2.0.x |
| DCM Maintenance App | 5.0.x |
| Audit Consumer | 1.0.x |
| DCM Dashboard Service | 2.0.x |
| Gateway Service | 1.1.x |
| Document Renderer | 2.2.x |
7. Blueriq Libraries
There are no specific Library updates for this release.
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
Unable to render {include} The included page could not be found.
11. Known issues
For an overview of known issue please refer to: Known issues
12. Security notification
Overview
Content Tools