You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
1. New
1.1. OpenAPI feed brought to the next level
For all REST web services in a project, Blueriq generates a feed using the OpenAPI standard to communicate the interface to its consumers. The result of this feed could, for example, be used in a store with public APIs that can be consumed. In order to make the consumption of Blueriq REST services a smoother experience, the feed now consists of more information:
- The title and description of the info object can now be edited in Blueriq Encore.
- You can now add an OpenAPI description to fragments, arguments, and headers.
- All operations withing a REST services are grouped, using tags. Additionally, a description can be added to these tags.
- Business Engineers are offered more insight into which for fields in a domain schema a description is present. Allowing for a better maintained
Click here for an overview of how the Blueriq model is mapped to the OpenAPI specification and stay tuned for even more OpenAPI feed improvements in the next release.
1.2. Outbox poller improvements
There are two processes ensuring that the outbox gets emptied. The first is a transactional listener that empties the outbox after an action on the Case Engine for a specific case ID. The second process is a poller that, scheduled with an interval, empties messages that are not picked up by the transactional listener.
The first poller exists for messages that were missed, so it can have a large interval. This could happen during a restart, for example. The second will ensure that messages, like the delete case messages, are picked up. This has a shorter interval by default. Those intervals are set with default values, so there is no need to change anything. The process outbox will remain almost empty under normal circumstances. When this is not the case in your situation, it is possible to configure the pollers. You can find more information on this topic at https://my.blueriq.com/x/twDv
2. Enhancements
| Enhancement | Details |
|---|---|
|
|
|
|
|
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Changes Platform Support
Our Platform support is updated.
Changes are:
- XXX
5. 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-locationdirectory ([Blueriq installation directory]\Runtime) - backup any config files you have altered under [Blueriq installation directory]\Services
before you start the upgrade.
6. Artifacts
The Blueriq artifacts are available under name: 17.x.x.xxxx
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 4.2.x |
| DCM Lists Service | 3.0.x |
| Material Theme | 1.1.x |
| Development tools frontend | 1.5.x |
| DCM Maintenance App | 3.0.x |
| Audit Consumer | 0.2.x |
| DCM Dashboard Service | 0.2.x |
| Gateway Service | 0.1.x |
| Document Renderer | 2.1.x |
7. Blueriq Libraries
There are no specific Library updates for this release.
8. 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.
9. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
10. Bug fixes
Unable to render {include} The included page could not be found.
11. Known issues
For an overview of known issue please refer to: Known issues
12. Security notification
Overview
Content Tools