You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
1. New
1.1. Project structure in Blueriq Encore
It is now possible to view and edit the project- and modulestructure in Blueriq Encore. Based on user feedback, we made a few changes compared to Studio. The Project structure view can be accessed from the navigation panel. Unlike Blueriq Studio, there is no separate view- and edit mode.
1.1.1. Project structure
Upon opening the Project structure, the following view will be opened:
- On the left, a list of projects is shown
- In the middle, the visualization of the project structure is shown. The selection in the list on the left corresponds to the selected project in the project structure. This visualization is new in Blueriq Encore and does not exist in Blueriq Studio.
- In the detail panel in the top right, the project includes can be configured.
- On the right in the properties panel, the project properties are shown. These include:
- the common properties such as functional name, description, dependencies and history,
- module configuration,
- the option to change the project to a library and vice versa,
- language configuration.
1.1.2. Module structure
After opening the project structure, it is possible to navigate to the module structure using the tab selector in the top of the view:
- On the left, a list of modules is shown, grouped by their parent project.
- In the detail panel in the top right, the module includes can be configured.
- Similar to the project structure, the selection in the list on the left corresponds with the selection on the right. However, and contrary to Studio in which all available included modules were shown, Blueriq Encore just shows the connected graph instead of showing all modules within the project scope. This allows the user to get a scoped overview of the modules and reduces zooming out or scolling.
1.2. Library & package import and export in Blueriq Encore
You can now import and export packages an libraries in Blueriq Encore.
1.3. Data rules in Blueriq Encore
In Blueriq 15.10, we've added the resource editor. In the current release, the Data rule editor and AQ_CsvConectivityService editor have been added. That means that modeling data rules is now fully supported in Blueriq Encore.
2. Enhancements
| Enhancement | Details |
|---|---|
|
DCM 2.0: Case Creation simplified |
We've simplified case creation, the Case Engine is now responsible for making sure the case is in a usable state after with only one message event. See DCM Create Case updates for more information. |
|
DCM 2.0: Performance + IProcessEngine segregation (DCM 1.0 and DCM 2.0) |
During the performance test of DCM 2.0 we encountered deadlock issues while using the SQL Server database with a multi-node or multi-threaded setup. Instead of querying the database for tasks that we already have in memory, we now use the in-memory model to search for specific tasks. This makes sure that the database does not have to sync its state before each search resulting in less queries and decreases the chance of deadlocks. We made a lot of changes which also impact the SDK. More on that can be found in the upgrade instructions: IProcessEngine segregation. |
|
Improved syntax highlighting behavior of expressions in Blueriq Encore |
Some editors can contain many expressions (e.g. decision table, data mapping). In Encore, these expressions need to be activated before syntax highlighting is applied. We implemented this mechanism before to prevent UI freezes. Previously, we already highlighted parts of the expression before activation for which there was no performance penalty. However, this turned out to be confusing for our users. Therefore, we do not highlight parts of expressions before activation anymore. |
|
Reintroducion of WS-Security support for the UsernameToken profile. |
Blueriq 15 initially dropped support for configuring the UsernameToken WS-Security profile for outgoing SOAP messages, but support has now been reintroduced. The configuration is different compared to Blueriq 14, please refer to the WS-Security documentation for details. |
|
Usability improvements for modeling certain nodes in flow and process editor |
We've improved the usability of modeling condition nodes in flows and split nodes in processes by optimizing how the space for alternatives is used. Furthermore, it is now possible to edit a single condition alternative. |
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.
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.11.0.923
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.7 |
| Material Theme | 1.1.1 |
| Development tools frontend | 1.3.0 |
| DCM Maintenance App | 2.1.14 |
| Audit Consumer | 0.1.6 |
| DCM Dashboard Service | 0.1.0 |
| Gateway Service | 0.1.0 |
7. Aquima Libraries
The Aquima Library has been updated, see below what has changed:
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-19065 |
Runtime |
Vulnerability CVE-201230-24998 was reported for apache.commons-fileupload-1.4.jar |
Fixed the vulnerability by upgrading apache.commons-fileupload to version 1.5. |
|
BQ-19000 |
Runtime |
When a user is logged in and clicks the logout button, the user is not logged out. |
The logout action did remove the user's authentication, but this change was not correctly persisted, keeping the user logged in on following requests. This is now corrected. |
|
CSD-4587 |
Studio Client & Encore |
Deleting an element related to a merge conflict could cause an error in the client after a server restart |
The client no longer gives an error in these case, but works as expected |
|
CSD-4576 |
Encore |
Newly created processes in Encore would not have a persistency ID preconfigured for start and end node |
A persistency ID is now automatically generated for the start and end node |
|
CSD-4573 |
Studio Client |
Module element parameters, from an external module, could cause an exception in the service call or container editor if the selected external module is not included in an the entry point or an implementation module of the current project |
When such an (invalid) module is selected, the module element selector will be disabled |
|
CSD-4432 |
Encore |
In the data mapping editor in Encore, the expression fields in the match conditions would sometimes not report validations that would be logged later by the runtime. The validations on the individual expression fields are reported correctly, but the validations between the source and target are not reported. |
We added the following validations to the data mapping editor in encore:
|
|
BQ-18474 |
|
The outbox publisher can cause deadlocks when the case engine is put under load. |
Instead of the outbox publisher publishing all messages on every trigger, the publisher now only publishes the messages for a specific case. This not only makes it more efficient, but also vastly reduces the changes of a deadlock occurring (note that this change is never 0). Under significant load tests, deadlocks were no longer observed. |
|
CSD-4490 |
Encore |
Encore could show expressions in decision tables outside of the cell if the row was at minimum height |
The expressions in decision tables no longer extent into adjacent cells |
|
CSD-4546 |
Encore |
Encore could show a badge containing a counter, where the count would be truncated and unreadable. |
The counter badge now grows to accomodate larger counts. |
11. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools