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. 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: 15.13.17.1978
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 4.1.13 |
DCM Lists Service | 2.4.7 |
Material Theme | 1.1.11 |
Development tools frontend | 1.5.6 |
DCM Maintenance App | 2.1.27 |
Audit Consumer | 0.1.15 |
DCM Dashboard Service | 0.1.10 |
Gateway Service | 0.1.16 |
Document Renderer | 1.1.2 |
4. Libraries
In this release, the following libraries have been updated:
ArtifactId |
GroupId |
License |
Version in 15.13.16 |
Version in 15.13.17 |
---|---|---|---|---|
com.nimbusds |
9.31 |
9.37.3 |
5. Retirement announcement
For this release there are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
6. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
CSD-5124 |
JAVA Runtime |
Project initialization could be slow with many flows |
Performance of project initialization in the presence of many flows has been improved. Some more room for improvement has been identified, this will be included in a subsequent patch version. |
CSD-5098 |
Encore |
The validation of documents and content items would not consider all content style restrictions, possibly resulting in project errors in the runtime. |
Content items and documents now validate content style restrictions similarly to the runtime, such that the error is now reported at design time |
CSD-5095 |
Encore |
Encore would not report validation errors for condition alternatives if the condition was left empty |
A condition alternative expression is now validated even if its condition is empty |
CSD-5097 |
|
Branches named 'master' could not be properly deleted in the Studio. They would appear to have been deleted, but reappear after a Studio server restart. |
The error was caused by a default repository setting in the history service which prevented branches named 'master' from being fully deleted. A fix has been implemented in the history service for newly created repositories. Existing repositories won't be fixed until the next scheduled maintenance cycle of the history service, or when restoring a repository from a backup. |
BQ-22064 |
Encore |
Cancelling the creation of a module may not close views that correspond with elements within the newly created module, resulting in errors |
The affected views are now closed, avoiding the error |
CSD-5029 |
|
Sorting was not applied correcty for the DCM_CaseList. |
We now create sorting for metadata fields which fixes the sorting. |
CSD-5026 |
|
The Studio's history data is periodically cleaned up to improve performance and disk space usage, but the resulting repository data was not verified to be complete. |
After a repository has been cleanup up, the resulting content is now checked to be complete. |
CSD-4835 |
|
In datamappings, the distinction between the first source collection and the additional source collections was not clear. |
Changed the appearance of the source collections so that it is now clear that the additional source collections are different from the main source collection, and updated the documentation to clarify the difference. |
CSD-4912, CSD-4917 |
Encore, studio |
After deleting the last branch in a repository the repository becomes unusable. |
Deleting the last branch is no longer possible (disabled). To delete the last branch in a repository, the repository needs to be deleted and recreated. |
7. Known issues
For an overview of known issue please refer to: Known issues