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

1. Documentation

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

2. Highlights

2.1. TSL support in Encore

Support for parsing Text Substitution Language (TSL) in Blueriq Encore has been included in this release, tot allow Blueriq Encore to provide accurate insights into dependencies and validations.

This means that:

  • You will now receive real time validations on TSL while editing,
  • TSL related validations are now included in the validation report,
  • TSL will be included in the dependencies,
  • Enhancement compared to Studio: renames of elements that are used in TSL will now be updated in TSL.

3. 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.

4. Artifacts

 The Blueriq artifacts are available under name: 15.13.8.1621

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

Component

Version

Customer Data Service4.1.10
DCM Lists Service2.4.4
Material Theme1.1.11
Development tools frontend1.5.5
DCM Maintenance App2.1.21
Audit Consumer0.1.11
DCM Dashboard Service0.1.7
Gateway Service0.1.11
Document Renderer1.1.2

5. Libraries

ArtifactId

GroupId

License

Version in 1

Version in 2

JavaEWAH

com.googlecode.javaewah

Apache License 2.0

1.1.13

1.2.3

org.eclipse.jgit

org.eclipse.jgit

EDL

5.13.1.202206130422-r

6.6.1.202309021850-r

spring-security-config

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-core

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-crypto

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-ldap

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-oauth2-client

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-oauth2-core

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-oauth2-jose

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-oauth2-resource-server

org.springframework.security

Apache License 2.0

5.7.10

5.7.11

spring-security-web

org.springframework.security

Apache License 2.0

5.7.10

5.7.11


6. Retirement announcement

For this release there are no specific retirement announcements.

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

7. Bug fixes

Identifier

Component

Issue

Solution

BQ-21078

 

CVE-2023-34042 has been detected for spring-security-config 6.1.3 and 5.7.10.

Fixed by updating spring-security-config to version 6.1.4 and 5.7.11

BQ-21064

Audit Consumer, JAVA Runtime

CVE-2023-4759 was detected for Eclipse JGit lower than 6.6.1.

Fixed by updating Eclipse JGit to version 6.6.1

BQ-20743

Encore

The aggregate editor in Encore could incorrectly show relations as invalid, or may cause the browser to hang when removing relations.

The editor has been completely revamped to address these issues, as well as improving how relations are shown in the editor.

BQ-20080

JAVA Runtime

Debug logging is polluted with unrecognizable stack traces which cannot related to the an actual failure for the AbstractSessionAwareFilter

Additional logging was added to determine whether exceptions that occurred during the logic of the AbstractSessionAwareFilter were recoverable and relatable to actually errors. It seem that they were not and therefore the logging is removed.

CSD-4499

JAVA Runtime

When defining the following property connection.restservice.http.header.auth-header in a application.properties file and in a second property file which is activated by a profile. The property from the application.properties was picked up instead the one declared in the profile properties file.

Reading certain properties, for instance header properties for http connections, did not follow the property overloading mechanism which was expected.
We have fixed this behavior and properties are now loaded in their ordered precedence.

8. Known issues

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