You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. New
1.1. OpenAPI import in Blueriq Encore
OpenAPI import in Blueriq Encore is now available, designed to streamline the workflow of the business engineers:
Key benefits:
- Time-saving: the import eliminates manual, repetitive steps by automatically creating elements such as the domain model, domain schemas, and REST services based on the OpenAPI specification.
- Simplified process: Blueriq does not support all features from the OpenAPI specification. Unsupported elements are flagged during the import process, after which they are ignored, allowing the import to proceed gracefully.
- Reduce human errors: automated creation reduces the risk of human errors during setup, ensuring the API structure is both consistent and reliable from the beginning.
Support:
- OpenAPI version 3.0 and 3.1
- Both YAML and JSON format is supported
- Specify a file by uploading it or providing the URL of the documentation
Read more about OpenAPI import here
1.2. Retry events for automatic tasks
Handling automatic tasks could be difficult in DCM. For once, the task should succeed in the end. However, it could also fail. When this happens we want the task to be retried according to the configured retry mechanism.
In the current situation, a task could exit using a standard exit (commit), a cancel exit (rollback) and a technical exception exit. The cancel does not make sense, since it will just abort the task, and wait until some other action has taken place on the case. The technical exception triggers the retry mechanism. However, there is no proper way to make the task fail in a functional way. Also, no information is stored, so the task is always just executed again.
To handle automatic tasks properly, a new flow type named "ExecuteTask" is added to the BlueriqCaseModelling library. When this flow type is selected the flow will become an execute task flow and gets access to the retry event node.
During execution, when the execute task flow reaches the retry event node, the corresponding task will be handled by the retry mechanism. When the task is retried, the flow will be started with the event parameters specified in the retry event node. This way, for example, particular parts of the flow that succeeded before the functional error can be skipped based on the parameters.
1.3. Separate Case engine application
Until now, the case engine could only be started using the runtime application. A new case engine application is now added to the release and stored in the artifactory. This new case engine application can be used instead of the runtime application to run the case engine. This case engine application uses the same configuration as the runtime application would. In the future, this configuration will be simplified as many case engine specific features will be available by default in the case engine application. For now, the usage of the runtime application to run the case engine will become deprecated. With Blueriq 18, the functionality for using the runtime application for the case engine will be removed.
2. Enhancements
Enhancement | Details |
---|---|
Less clicks needed to rename an element in Encore |
The confirmation step has been removed from the rename stepper in Encore and all primary buttons in this stepper do now respond to the enter key as well, making renaming in Encore a quicker and smoother experience. |
New default position of exception exits in flows in Encore |
When selecting a service call or subflow node in a flow in Encore, exception exits that did not have coordinates yet, tended to appear just below other already connected exits, making them hard to read. They therefore now appear on the center right of a subflow/service call node, matching the position that they are often eventually dragged to for optimal readability of the flow. |
Ability to expand all for parts of a tree in Encore |
Expand buttons in trees can be clicked using either ctrl or shift to expand the entire subtree starting from that point. For example, a specific container and all its contents can now be expanded at once, without having to expand all sibling containers as well. |
Use ctrl+click to evaluate an expression in the Quick test panel in Encore |
The expression evaluator in the Quick test panel will now evaluate the expression when pressing ctrl+shift, such that the cursor can remain in the expression editor. |
Change icons of flow and process nodes in Encore |
You can now change the icons of flow nodes and process nodes in Blueriq Encore, to increase readability. |
Libraries in the navigation menu show their version |
The navigation menu of projects now shows the version of a library on the right side of a library menu item. |
Feedback after a backup has been restored in Encore |
A green feedback message will now pop up after a backup has been restored successfully in Encore. |
URL and HTTP method of REST calls in runtime log |
The HTTP method and URL of a REST client call are now logged in the debug log of the runtime, making the debug process of consuming web services more transparent. |
Base URL of a REST call always ends with a slash |
The runtime now ensures that a base URL of REST requests always ends with a slash. |
Library version in navigation panel in Encore |
The version of each internal or external library is now shown as additional information in the navigation panel. |
Stability of Studio exports |
The ordering of elements in branch and project exports for the same Studio (Encore) model have been made more stable. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Upgrade Instructions
There are no specific upgrade instructions for this release.
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.
5. Artifacts
The Blueriq artifacts are available under name: 17.6.0.196
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 5.0.6 |
DCM Lists Service | 4.0.6 |
Material Theme | 1.3.5 |
Development tools frontend | 2.0.1 |
DCM Maintenance App | 5.0.8 |
Audit Consumer | 1.0.6 |
DCM Dashboard Service | 2.0.3 |
Gateway Service | 1.1.2 |
Document Renderer | 2.2.2 |
6. Blueriq Libraries
A new version of the BlueriqCaseModelling Library has been released.
7. 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.
8. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
9. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
CSD-5614 |
Encore |
End nodes in the flow and process editors could be clipped by a scrollbar |
The flow and process editors have been updated to reserve sufficient space for the end nodes |
BQ-23965 |
Java Runtime |
A custom runtime that was including a custom application.properties in the war file would not start up under certain conditions. |
This has been fixed. |
CSD-5596 |
Encore |
Dropdowns that let you select a metadata field of an aggregate did not navigate to the aggregate when ctrl/shift clicking. |
Such dropdowns will now navigate to the aggregate editor as expected. |
BQ-23913 |
Java Runtime |
With the introduction of the |
Fixed resolving the instance from which the relation attribute originates, plus added the validation message in the correct way so the frontend can signal that there are validation messages on the page. |
CSD-5536 |
Java Runtime |
Custom OpenID Connect parameters were not added to the authentication request when the application is started using a theme. |
The parameters are now added to the request to the authentication provider. |
CSD-5541 |
Encore |
Moving an attribute, relation or static instance between modules would not properly make the moved element available on the entity. |
Moves of attributes, relations and static instances are now properly reflected on the owning entity. |
BQ-23870 |
Encore |
While editing a flow, a node can be automatically resized by double clicking on the node's resize handle; which can be found in the bottom right corner of the node. When the text within the node exceeded a certain length and the node has a repeat expression set, resizing could result in a node which wasn't wide enough to display all text. This would cause it the text in the node to be broken up into two lines. |
Automatically resizing has been fixed. |
CSD-5521 |
Encore |
Clicking within disabled input fields would not cause a row to be selected, for example in the service type and container type global editors for globals within external libraries. This is a result of a change in Google Chrome 116. |
A workaround to Chrome's change in behavior has been found, such that rows can now be selected through disabled input fields again. |
BQ-23820 |
Encore |
When editing expressions, a completion menu can be shown. Attribute completions in this menu are accompanied by an icon which corresponds to the data type of the attribute. For completions with a 'percentage' data type, a square was shown instead of the icon. |
The icon is now properly shown. |
BQ-23745 |
Encore |
Missing validation for when a Blueriq validation does not have a message. |
Blueriq validation message without a message are now reported as error. |
BQ-23744 |
Encore |
In REST Services and Domain Schema's the target entity of the relation is validated covariantly which is incorrect |
Change the REST Service and Domain Schema to only allow invariant entities for the target entity of the relation |
CSD-5479 |
Java Runtime |
When formatting historic dates from a |
We introduced a new method on the |
BQ-23664 |
Encore |
Encore doesn't validate that multivalued relations don't refer to a singleton. |
A multivalued relation referring to a singleton entity is now reported as warning, corresponding with the warning that is shown in the runtime dashboard. |
BQ-23591 |
Java Runtime |
The AQ_StoreDecision service would fail if any justification text contained TSL which used a multiton instance, even if the justification text was meant for an attribute of that specific instance, |
The AQ_StoreDecision service now activates the instance before expanding the related justification texts. |
BQ-23585 |
Encore |
The tooltip of an expression editor could sometimes remain open. |
The issue has been resolved. |
BQ-23119 |
Java Runtime |
When an invalid CSRF token was received by the runtime, rendering the error page was delegated to the application server, which could leak version information if not configured restrictively. |
The runtime now sends a JSON error when an invalid CSRF token is received. |
10. Known issues
For an overview of known issue please refer to: Known issues