You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Identifier | Component | Issue | Solution |
---|---|---|---|
CSD-5124 | 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 release. |
CSD-5108 | Metamodel generator | generate-metamodel goal was no longer available | generate-metamodel goal is available again |
BQ-22156 | Runtime | Max clock skew and max TTL values were not configurable for REST security, and the max clock skew value was set to 0, which is an unrealistic value. | Made the max clock skew and max TTL values configurable, and set the default value for max clock skew to 5 minutes. |
BQ-22140 | Encore | The login button would continue to spin if the Studio server is unavailable | The login button stops showing a loading indicator when an error occurs, as well as reporting this error to the user |
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 | Studio | 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 |
BQ-22024 | Runtime | When running the runtime as a war in in a Tomcat server, the SameSite Cookies would not be set. | When running the runtime as a war on a server the SameSite cookies will now be set if they are correctly configured. |
CSD-5026 | Studio | 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. |