You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
1. New
1.1. Manual data mapping selection in task mapping in Blueriq Encore
A task mapping is used to define what should be done when a user starts and ends a task. More specifically, a task in the process module is mapped to a flow in the (task) implementation module and flow events could be mapped to process events as well. When starting and ending this flow, the runtime also executes a data mapping. Previously, this mapping was selected automatically. This can become problematic when there are multiple matching data mappings modeled. We therefore added the possibility to select a matching data mapping manually. This can only be done in Blueriq Encore for each task mapping entry.
If there are multiple matching data mappings available, a validation warning will appear in the project validation report to warn for ambiguity:
1.2. Process editors in Blueriq Encore
In the past minor releases we've already added several editors that are needed to model processes. We've now completed the list by adding the remaining custom containers (AQ_Dashboard_ThrowPortalMessage, AQ_ThrowMessageEvent, DCM_ThrowMessageEvent, DCM_ThrowAsyncMessageEvent, AQ_GetCaseInfo, AQ_GetTaskInfo) and custom service calls (AQ_Timeline, AQ_Dashboard_FlowWidget, AQ_Worklist, DCM_Worklist, DCM_Tasklist, AQ_Caselist, DCM_Caselist).
2. Enhancements
| Enhancement | Details |
|---|---|
| Tooltip for truncated texts in dropdowns in Blueriq Encore | Truncated texts in dropdowns were previously only fully readable after opening the dropdown. Now, these texts is also readable after hovering over the truncated text: |
| Additional information in dropdowns in Blueriq Encore | We've added additional information to options in several dropdowns. For example to dropdowns for data type (showing explanation), presentation styles (showing the description) and masks (showing an example and the description):
|
| Improved error messages in the frontend | For example the error: "The element reference [InlineReference definition=[FieldDefinition name=Person.Name]] failed composition due to error. call stack: Person.Name (field)" has been rewritten to: "Failed to compose field 'Person.Name' due to an error: No active instance of type 'Person'" |
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.
- Removed support for Windows 10 Enterprise version 1909 (64-bit)
5. Upgrade Instructions
The upgrade instructions for this release can be found here.
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: 15.8.0.700
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 4.1.5 |
| DCM Lists Service | 2.2.6 |
| Material Theme | 1.0.55 |
| Development tools frontend | 1.2.3 |
| DCM Maintenance App | 2.1.13 |
7. Aquima 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.
ArtifactId | GroupId | License | Version in 4.1.4 | Version in 4.1.5 |
|---|---|---|---|---|
org.bouncycastle |
| 1.69 | ||
org.bouncycastle | 1.68 | 1.69 | ||
org.bouncycastle | 1.68 | 1.69 | ||
net.bytebuddy | 1.12.9 | 1.12.19 | ||
org.codehaus.janino | 3.1.7 | 3.1.9 | ||
com.fasterxml.jackson.core | 2.13.4.1 | 2.13.4.2 | ||
org.codehaus.janino | 3.1.7 | 3.1.9 | ||
org.glassfish.jaxb | 2.3.6 | 2.3.7 | ||
org.springframework.amqp | 2.4.6 | 2.4.8 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.boot | 2.7.1 | 2.7.6 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework.cloud | 3.1.3 | 3.1.5 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework.data | 2.7.1 | 2.7.6 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework.amqp | 2.4.6 | 2.4.8 | ||
org.springframework.retry | 1.3.3 | 1.3.4 | ||
org.springframework.security | 5.7.2 | 5.7.5 | ||
org.springframework.security | 5.7.2 | 5.7.5 | ||
org.springframework.security | 5.7.2 | 5.7.5 | ||
org.springframework.security | 1.0.10.RELEASE | 1.0.11.RELEASE | ||
org.springframework.security | 5.7.2 | 5.7.5 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.springframework | 5.3.21 | 5.3.24 | ||
org.glassfish.jaxb | 2.3.6 | 2.3.7 |
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-18248 | JAVA Runtime | Those using Woodstox to parse XML data may be vulnerable to Denial of Service attacks (DOS) if DTD support is enabled. | Updated internal fasterxml woodstox version to 6.4.0 |
BQ-18132 | The Case Engine would not start when the timeline-event-publisher-amqp and trace-event-publisher-amqp profiles where disabled because the outbox wich is shipped with the case engine needs the publishers. | The timeline and trace outbox is now only available in the case engine when the profiles timeline-event-publisher-amqp and trace-event-publisher-amqp are enabled. | |
BQ-18040 | Reopening a task is the same as aborting a task. When a task is aborted, first the lock is checked if it corresponds with the task AND the user that requested the lock => the user who started the task. The reopen task is called by the maintenance user, which is different from the lock requester, so you get an exception | Specifically for reopening a task, the lock requester is neglected in checking the task lock. Note that a task lock still needs to exist. | |
BQ-18032 | For publishing messages from the outbox, we use a listener and a poller. This can lead to a situation in which a message is removed from the outbox by the poller, while it is already removed by the listener. This is an expected situation, but still a large stacktrace is printed in the log. This should be prevented. | Instead of removing a message, it is now first looked up and then when it exists, it is removed. This was actually already done by the repository, but the difference is that now when a message no longer exists we do nothing, as opposed to throwing an exception. | |
CSD-4308 | studio | The metamodel generator Maven plugin could reach a timeout for large projects | The timeout has been increased from 1 minute to 10 minutes |
11. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools