Page History
Numbered Headings | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NewOpenAPI feed brought to the next levelIt is now easier than ever to connect to a Blueriq API. For all REST web services in a project, Blueriq generates already generated 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:
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. Outbox poller improvementsThere 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 Enhancements
DocumentationDocumentation on the new features and improvements of this release is linked in the respective topics. Changes Platform SupportOur Platform support is updated. Changes are:
Upgrade InstructionsThere are no specific upgrade instructions for this release.
ArtifactsThe Blueriq artifacts are available under name: 17.x.x.xxxx This release includes these versions of Blueriq components with a separate life cycle:
Blueriq LibrariesThere are no specific Library updates for this release. LibrariesIn 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.
Retirement announcementThere are no specific retirement announcements. For a full list of deprecated features, go to Deprecated features. Bug fixes
Known issuesFor an overview of known issue please refer to: Known issues Security notification |