You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Identifier | Component | Issue | Solution |
|---|---|---|---|
BQ-21121 | DCM Dashboard | The DCM Dashboard war fails to startup throwing a stack trace about security configuration | The DCM Dashboard actuator security endpoint configuration was inconclusive resulting into a stack trace when running the DCM Dashboard inside an application server. This is fixed. |
BQ-21078 | Runtime | 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, 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-20873 | Encore, Studio | A project validation would be reported when exporting a project when a global field type had presentation styles and was used in a container or on a page. | Using presentation styles in a global field that is used on a page or in a container will no longer result in a failed project export. |
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. |
CSD-4860 | Studio | Deleting elements that are part of merge conflicts would not properly update those conflicts | The Studio Server now properly updates relevant merge conflicts when elements are removed |
CSD-4842 | Runtime | ||
BQ-20080 | 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 | 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. |
Overview
Content Tools