You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
2. Development Tools
We have renewed the development tools that have been the centre of the day to day operations for the Business Engineer for the last couple of years. Ever since they were introduced many years ago nothing much has changed significantly other than some configuration options that have been added.
With the new development tools we have made two big changes:
- better usability of the debug bar
- less options for configuration via the dashboard
Better usability of the debug bar
The debug bar was not up to our spec any more with the pop-up windows that were big, clunky and therefor not very user friendly. We have focused on providing different ways of working with the debug bar. As a first step we moved the debug bar (by default) to the side of the window as wide screens are the standard now. On startup of the session the debug bar is in a minimalistic state were only some basic features are shown. When the business engineer wants to debug their session the debug bar can be opened to find the toolset to either inspect the profile or the page.
The profile editor provides easy navigation through all the instances and attributes and of course the expression editor to debug the logic.
The page element explorer is completely renewed. We have gone from a static overview to an interactive explorer. It is inspired by the browser page explorer and provides easy selection of an element on the page and then shows all its details. And of course easy navigation from element to element, from parent to children or vice versa.
Less configuration via the dashboard
We believe that the configuration of the Runtime, which becomes more extensive ever so more, doesn't need be supported by the Dashboard. It's better to just edit the files themselves. Configuration is not day to day business and editing a specific file is just as effective. Even more, you can better trace who made what changes when you use this in combination with a version management system.
Business Engineers told us that some options are still very useful to have within reach in the Dashboard, those are the shortcuts and the runtime user settings. These functions can be found in the settings tab of the Dashboard.
Front-end interoperability
The new development tools are made in Angular and integrate with the Blueriq frontend framework. If you have a custom front-end theme based on Angular, a small change needs to be made to integrate the new development toolbar. Please refer to this commit that shows what changes are needed.
3. Blueriq Design System
The new development tools is the first componenent we're releasing that uses our new design system. This design system is basically a library consisting of UI components (such as an input field or a toggle), with its constraints and guidelines on how to use it.
The design system increases consistency for the Business Engineer and efficiency for the development process of Blueriq.
This design system is also used for Blueriq Encore, the successor of Blueriq Studio, which will be released later.
We felt that the landing page of Blueriq also deserved a makeover, so we've turned the look and feel into the one of our design system:
4. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
5. Changes Platform Support
Our Platform support is updated with the following changes:
5.1. Removals
- Internet Explorer 11 support for Blueriq Runtime and Blueriq Publisher
6. Upgrade Instructions
You can find the upgrade instructions for this release here: Release 14.0 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.
7. Artifacts
The Blueriq artifacts are available under name: 14.0.0.3158
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 3.3.0 |
DCM Lists Service | 1.3.0 |
Material Theme | 1.0.x |
8. Aquima Libraries
- There are no specific Library updates for this release.
9. Libraries
In this release, the set of third party libraries that is used by Blueriq was updated. When your installation of Blueriq includes custom components (artifacts that do not ship with Blueriq, such as proprietary plugins), those components should be tested for compatibility with these changes.
10. Retirement announcement
10.1. Legacy property encryption has been removed
In Blueriq 12.10 we have introduced a new property encryption algorithm. The legacy property encryption will not work anymore starting from this release. You can read more about it in the upgrade instructions.
10.2. Removed legacy toggles and deprecations
We removed several legacy toggles, deprecated methods and deprecated features, like deprecated blueriq.legacy.rollback-unknown-relation-to-empty-list
and blueriq.legacy.execute-datamapping-on-cancel-task
. You can read more about it in the upgrade instructions.
Exception is the blueriq.legacy.create-empty-elements-for-unknowns
, this is changed to a feature toggle and is now available as blueriq.webservices.create-empty-elements-for-unknowns
.
10.3. Removed development tools properties
The following property settings should be removed as they no longer have any function for the development tools:
blueriq.development.settingsExternallyManaged
blueriq.development.sessionstore.dir
blueriq.development.showToolbar
blueriq.studio.port
blueriq.studio.hostname
For a full list of deprecated features, go to Deprecated features.
11. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
BQ-12371 |
|
When retrieving all cases or tasks, first the ids are retrieved and then corresponding cases/tasks. This is unnecessary and leads to more database interactions. |
The cases and tasks are now retrieved directly, reducing the number of queries/database interactions. |
BQ-12364 |
|
The process engine sends updates to the DCM list application. For every update the case is retrieved from the database. This also happened if the DCM list client was disabled leading to unnecessary database calls. |
Updated the process engine to only retrieve the case if the DCM list client is enabled. |
CSD-3693 |
|
The OpenAPI feed of a REST operation could be missing the "responses" field, which is required by the specification. |
The "responses" field is now always present to satisfy the OpenAPI specifcation. |
CSD-3689 |
JAVA Runtime |
When using Redis with Blueriq, the memory used keeps increasing, even if no actions on the runtime are performed. This ultimately leads to slower or even no response from the runtime over time. |
The Redis implemenation of Blueriq kept sessions in memory, even if they were no longer relevant. This caused the memory to grow over time. This has been fixed so the memory is freed again when sessions are no longer relevant. |
CSD-3685 |
|
When the Process Engine tried to get a lock on a case that has already been locked, a message is written to the log on ERROR level. This should be an INFO message because it does not interrupt the normal program flow. |
Changed the log statement from ERROR level to INFO. |
CSD-3682 |
|
When creating or restoring a backup of studio repositories which is larger than 2GB, an error would occur. |
Studio backups which are larger than 2GB can now be backed up and restored using the backup tool. |
CSD-3665 |
|
When installing Blueriq on a device which doesn't use UTF8 as its default encoding the installation of postgres fails. |
We improved the installer to not look at the default encoding used by the device but to enforce UTF8 when initializing postgres |
BQ-12087 |
|
The DCM_WorkList definition has a 'Show all tasks' checkbox. When this is checked, no tasks are displayed, while it should display all tasks |
The show all tasks checkbox was not correctly processed by the DCM lists application, which made it return no results. This has been corrected to return the correct results |
BQ-12341 | Runtime | Acquiring a case lock could cause the entire case, including the case profile to be read from the database, which could result in a lot of unnecessary queries, giving a performance penalty. | We removed the need to read the case from the database after acquiring the lock and in this way we improved the performance of starting a task that has case locking enabled. |
12. Known issues
This version contains a newer version of the Spring Framework that in some cases causes an error when the Runtime is deployed on JBoss EAP. A workaround is described in Known issues.
For an overview of all known issues, please refer to: Known issues