You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
2. Blueriq Encore
From this release, you will be able to unleash the power of Blueriq from our brand new modeling environment. Although the Blueriq concepts are not different compared to Blueriq Studio, Blueriq Encore offers a new and enhanced modeling experience. We were able to achieve this by listening to your feedback. Blueriq Encore is installed automatically with Blueriq Studio.
Highlights of Blueriq Encore are:
- 100% browser based, full support for chromium based browsers such as Google Chrome and Microsoft Edge.
- Lightning fast modeling experience due to improved performance.
- Simplified creation, debugging, and maintaining APIs using the new data mapping editor with simulation and unit test capabilities.
- Stay between the guardrails with real time model validations.
- Creating neat flows using snap to grid in the flow editor.
- Refactor pages and containers up to 5 times faster by dragging and dropping elements even to other parents without losing preconditions, presentation styles and other configuration.
- Enhanced navigation between elements that are defined in different modules.
Blueriq Encore is still in development (have a look at the progress here), but you are already able to use it because it is compatible with Blueriq Studio. That is: edits in Studio will appear in Encore and vice versa.
Can't wait? Send an email to support@blueriq.com and gain acces to https://meet-encore.blueriq.com after watching the transition videos.
We're continuously improving Blueriq Encore so don't hesitate to share your thoughts with us by using the customer portal or sending an email to support@blueriq.com.
An example of a flow in Blueriq Encore:
3. DCM architecture beta
For a better Dynamic Case Management experience, a number of architectural changes have been made. We have been working on a new architecture, which is event-driven. The benefits are that the DCM solution is split in multiple smaller functions, that can be configured (and optimized) separately, using technologies best suited for the job, and end-users do not have to wait for processing times where it is not necessary. The new architecture also includes a first approach on reactive components, by adding a reactive Task list for the end-users. The software is in a beta stage, and can be tried on a development environment. The current way of building DCM applications and processes will remain intact, so any project can safely upgrade to the latest Blueriq version without using the new architecture. For more information trying the new beta architecture, please check DCM architecture beta release for more information.
4. Document rendering service
In release 15.0 the new Document rendering service that has been introduced in Blueriq 14.9 has become mandatory.
We migrated from an integrated Ibex Java renderer in the Blueriq Runtime to a stand-alone .Net Ibex rendering service. This provides the option for customers to create 1:n deployment model where one Document renderer services multiple Runtimes.
To help our customers in the migration we documented the steps here. We focused on having as little differences in the pdf output as possible, in which we succeeded. Some minor differences have been noticed and have been documentend on the migration page.
Installation and configuration can also be found here on my.blueriq.
5. Keycloak as identity provider in the Studio
The Studio has supported a wide range of authentication schemes for some time already, and the selection is now extended by leveraging Keycloak as identity provider using the OpenId Connect protocol. This enables more extensive authentication configurations than were possible before, such as federated user authentication. Please refer to the Keycloak configuration page for information on how to configure the Studio to start using Keycloak.
6. Enhancements
| Enhancement | Details |
|---|---|
| For DCM 2, the system instance now has a taskId and processId when a task is active. | The DCM_GetTaskInfo relies on the and task id being present as a paremeter, however, this id is not always known when a task is executed. A set of attributes are added to the System entity: system.taskId and system.processId. When a task is started in a DCM 2 context, the attributes will be set with the corresponding values. If no task is active the value is unknown. |
| A default webservice timeout setting has been introduced. | For better stability and user experience we introduced a default webservice timeout setting. Detailed properties setting can be found here. The default setting is 15 seconds. You can set a override timeout for each connection. |
7. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
8. Changes Platform Support
Our Platform support is updated. Changes are:
- Java 17 (or higher) is mandatory for the runtime
8.1. Discontinued
- Java 11 support is stopped, from Blueriq 15 on Java 17 or higher is mandatory.
- Websphere Liberty Core support is discontinued. As alternative we recommend to use Tomcat.
9. Upgrade Instructions
Please review the Release 15.0 Upgrade Instructions.
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.
10. Artifacts
The Blueriq artifacts are available under name: 15.0.0.105
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 4.0.1 |
| DCM Lists Service | 2.1.3 |
| Material Theme | 1.0.44 |
11. Aquima Libraries
The DCM library has been updated, see below what has changed:
12. 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 14.11.1 | Version in 15.0.0 |
|---|---|---|---|---|
ibex | 4.9.0.15 |
| ||
org.springframework.security | 1.1.1.RELEASE |
| ||
org.springframework.security.oauth | 2.5.2.RELEASE |
| ||
org.springframework.security.oauth.boot | 2.6.6 |
| ||
com.fasterxml.jackson.core | 2.13.2.2 | 2.13.2.1 |
ArtifactId | GroupId | License | Version in 3.4.12 | Version in 4.0.1 |
|---|---|---|---|---|
com.google.code.findbugs |
| 3.0.1 | ||
net.jcip |
| 1.0 | ||
com.google.code.findbugs |
| 3.0.2 |
13. Retirement announcement
For a full list of deprecated features, go to Deprecated features.
13.1. Dropped support for reading and publishing R8-R11 export
In release 12 we introduced a new export format and to maintain backwards compatibility we added an extra set of properties to still be able to read the R8 exports. In release 15 we have removed the deprecated R8 exports altogether, when using an R8 export the Runtime will log an error stating that exports older than version 12 cannot be read anymore.
For a migration path for old exports please go to Release 15.0 Upgrade Instructions
13.2. Dropped support for DateValue.parseDate and DateValue.valueOf with time component
In Blueriq 13.2 the use of DateValue.parseDate with a time component as argument and DateValue.valueOf with a time component as return value became deprecated.
Starting from this release the warning has been removed and doing this results in an exception. You can read more about it in the Deprecated features.
13.3. Dropped support for Trace Event V1
In Blueriq 14.10 the use of Trace Event V1 became deprecated. In this release the Trace Event V1 has been removed in favour of the Trace Event V2. You can read more about it in the Release 15.0 Upgrade Instructions.
14. Bug fixes
Identifier | Component | Issue | Solution |
|---|---|---|---|
BQ-15778 | Runtime | CVE-2022-22968 | Upgraded Spring Framework to the version where this issue is fixed. |
BQ-15698 | Runtime | The Spring configuration in Blueriq contained a circular reference when the blueriq.session.session-manager property would be set to external. | The circular reference has been removed. |
BQ-15646 | Development dashboard | Selection inputs don't show any values to select anymore except for one empty value. In the case of a multivalue slection input selecting this empty entry will add an empty pill. | The selction input works as intended again. |
BQ-15369 | Runtime | When a log level on root is set higher than INFO the audit logging isn't working anymore. | Audit logging will always work regardless of log level on root, when activated in bootstrap.properties |
BQ-15359 | Runtime | The AQ_GetHeaders service did not support multi valued headers. It would store the first value of a multi valued header, regardless of whether is was stored to a single valued or multi valued attribute. | We added support for multi valued headers to the AQ_GetHeaders. When a multi valued header is stored to a single valued attribute, the last value will be stored. |
CSD-4063 | Development dashboard | When opening the h2 console an error screen is shown instead of the h2 console | The IIS proxy in the installer sets a header which is not properly understood by tomcat serving the h2 console, resulting in the error. By setting extra headers in IIS, tomcat can properly understand the request and serve the h2 console. |
CSD-3889 | Runtime | Blueriq didn't offer a security property to enable session fixation protection | Blueriq now offers a property to enable session fixation protection: |
15. Known issues
For an overview of known issue please refer to: Known issues
16. Security notification
To improve the default security configuration of the Runtime this release has changed various configuration defaults to enable best practices by default.
Details can be found in the upgrade instructions.
Overview
Content Tools