You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1. Documentation

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

2. Upgrade Instructions

For this release, there are no specific upgrade instructions.

As a best practice

  • backup your repository
  • backup your database before running scripts
  • backup your spring.config.additional-location directory ([Blueriq installation directory]\Runtime)
  • backup any config files you have altered under [Blueriq installation directory]\Services

before you start the upgrade.

3. Artifacts

The Blueriq artifacts are available under name: 16.11.14.2737

This release includes these versions of Blueriq components with a separate life cycle:

Component

Version

Customer Data Service 4.5.7
DCM Lists Service 3.1.7
Material Theme 1.3.4
Development tools frontend 1.7.0
DCM Maintenance App 4.1.11
Audit Consumer 0.5.7
DCM Dashboard Service

1.1.6

Gateway Service 0.4.10
Document Renderer 2.2.2

4. Libraries

For this release there are no specific Library updates.

5. Retirement announcement

There are no specific retirement announcements.

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

6. Bug fixes

Identifier

Component

Issue

Solution

BQ-24170

Encore

The entity editor would not restore the scroll position of the attribute and relation lists when switching between views.

The scroll position is now restored as expected.

CSD-5706

Encore

Various dropdowns could be inadvertently clipped, preventing the ability to scroll.

Some dropdowns have been updated to be positioned in front of their container, avoiding the clipping issue.

BQ-24155


The default error exchange for the DCM Lists Service RabbitMQ connection had the wrong value.

It now references the right exchange.

BQ-24138

Encore

It was possible to model service and function calls in contract modules in Encore even though this is not allowed

Removed the ability to model service and function calls from contract modules in Encore

CSD-5650

Studio

The Studio server could incorrectly detect a cycle in process type restrictions, even if the structure of process types was not actually cyclic.

The cycle detection has been improved to avoid the false positive.

CSD-5608

Encore

Various process validations were missing in Encore:

  • Nodes which are not connected to end nodes were not reported.
  • Process type which does not allow task implementation and does not contain any restrictions.
  • Subprocesses were always allowed to be placed regardless of the restrictions in the process type.
  • Tasks were always allowed to be placed in a process regardless of the allowed implementation of the process type.
All of these aspects are now validated in Encore, enabling feedback during modelling for situations that would be reported as error in the runtime

7. Known issues

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


  • No labels