Versions Compared

Old Version 13

changes.mady.by.user Felix Janssen

Saved on

compared with

New Version 14

changes.mady.by.user Tijmen Daatselaar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Release Date

 

ContentRelease 17.5
Download

UI Button
colorpurple
icondownload
titleDownload Blueriq
urlhttps://my.blueriq.com/display/CUS/Customers+Home

Panel

On this page:

Table of Contents
maxLevel1
stylenone
Numbered Headings
start-numbering-with1

New

Deprecate elements in Encore

It is now possible to manage the evolution of a model by deprecating elements in Blueriq Encore using the built-in label called "Deprecated". A deprecation will generate a validation warning for each usage of the deprecated element. This signal can be used by business engineers to other business engineers to communicate that an element will be removed in a future version. 

OpenAPI feed improvements part 2

Continuing on Blueriq 17.4, more the OpenAPI feed improvements that have been added to the current release in order made in the Blueriq release 17.4 to provide standardized and clear documentation on Blueriq web services and thereby improve collaboration with consuming parties.

From this release:

, the Blueriq 17.5 contains two more improvements:

  • You can now exclude It is possible to exclude specific operations from the OpenAPI documentation if you do not want to disclose this information.
  • Validations on fields and parameters are communicated automatically and as clearly as possible ( using JSON schema semantics ) in the OpenAPI feed.

 Process messages for a deleted case in DCM Lists

Sometimes a message is processed in the DCM Lists for a case that has just been deleted. The reason for this is that messages can be processed out of order, especially when using multiple consumers. This used to lead to an exception, which would cause the message to be retried until it fails definitively in the maintenance app. There it would then have to be manually removed. To address this, cases are now no longer directly removed from the case engine, but instead get a flag that they are marked for removal. These cases are then ignored by the DCM Lists application, unless a message is processed that relates to that specific case. The DCM Lists application can then process that message by discarding it with a corresponding log entry instead of the exception.

Due to these changes, cases are no longer removed from the database causing the database to grow and negatively affect performance. To prevent such degradation, a cleanup mechanism runs at a specified interval to clean up cases marked for deletion before a specific time. For more information, see Case deletion in DCM Lists [editor].

Enhancements

EnhancementDetails
Displaying all attributes and relations within an entity in Encore

An entity that is defined in, and opened from a lower level module scope now displays attributes and relations that are defined in a higher level module. Such attributes are preceded with an upward arrow indicating their higher level of definition. In such cases an eye-icon is present near the entity name as well that can be clicked on to toggle the scoped view.

Validation rules with invalid parameters may now be reported in the project initialization report.

Parameters of a validation type are now supplied to the validation type implementation during project initialization, such that failures during creation of the validation rule (e.g. because the parameters are invalid) are now included in the project validation report as error.

OpenID Connect has been consolidated into a separate component

The OpenID Connect feature has been consolidated into a separate component. See OpenID Connect Component [editor] for details, and read the upgrade instructions for this release to enable it if you need it.

Documentation

Documentation on the new features and improvements of this release is linked in the respective topics.

Changes Platform Support

Our Platform support is updated.

Changes are:

  • Added support for Oracle JRE 22 and Azul Zulu OpenJDK 22

Upgrade Instructions

The Upgrade Instructions for this release can be found here: Release 17.5 Upgrade Instructions [editor].

UI Text Box
typetip

As a best practice

  • backup your repository
  • backup your database before running scripts
  • backup your 
    Include Page
    _HomeFolder
    _HomeFolder
     directory ([Blueriq installation directory]\Runtime)
  • backup any config files you have altered under [Blueriq installation directory]\Services

before you start the upgrade.

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 Service5.0.x
DCM Lists Service4.0.x
Material Theme1.3.x
Development tools frontend2.0.x
DCM Maintenance App5.0.x
Audit Consumer1.0.x
DCM Dashboard Service2.0.x
Gateway Service1.1.x
Document Renderer2.2.x

Blueriq Libraries

There are no specific Library updates for this release.

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.

UI Expand
titleThird-party libraries Java Runtime
ArtifactIdGroupIdLicenseVersion in 17.x.xVersion in 17.x.x
UI Expand
titleThird-party libraries Persistence API for customer data
ArtifactIdGroupIdLicenseVersion in 4.2.x (Blueriq 17.x.x)

Version in 4.2.x (Blueriq 17.x.x)

Retirement announcement

There are no specific retirement announcements.

For a full list of deprecated features, go to Deprecated features.

Bug fixes

Include Page
Blueriq 17.x Bug Fixes
Blueriq 17.x Bug Fixes

Known issues

For an overview of known issue please refer to: Known issues

Security notification