New

OpenAPI feed brought to the next level

It is now easier than ever to connect to a Blueriq API. For all REST web services in a project, Blueriq 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:

• The title and description of the info object can now be edited in Blueriq Encore as demonstrated in the figure below.
• You can now add an OpenAPI description to fragments, arguments, and headers.
• All operations within a REST services are grouped, using tags. Additionally as demonstrated in the figure below. 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 , using the OpenAPI icon in the tree view in domin schema's. 

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 releaseBlueriq 17.5. 

Mark elements as deprecated in Encore

Elements in Encore can now be marked as deprecated. MArking an element as deprecated can be done using the built-in tag named deprecated, which will result in validation warning(s). This will make it easier to keep your models clean contributing to improved maintainability and readability of the modelImage Added
An example of the OpenAPI specification of a Blueriq service using swagger UI: old (left) vs. new (right).

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

 Improved

AQ_File_Move performance

The Content Manager performance performance of the AQ_File_Move service call has been improved by introducing a new underlying API . A direct move has been added from ContentManager to ContentManager, which should make move content perform to the Content Managers. These new adjustments should make the move of a file instantly when moving said file on the on same disk or memory connection. Furthermore we have introduced a new Channel API and deprecated the old Inputstream API of the IContentManager. More information on how to implement the a custom content manager can be found here. Look at the upgrade instructions to see which methods have been replaced.

Enhancements

Documentation

Documentation on the new features and improvements of this release is linked in the respective topics.

Changes Platform Support

Our Platform support is updated.

Changes are:

• XXX

Upgrade Instructions

Upgrade Instructions

See Release 17.4 Upgrade Instructions for the There are no specific upgrade instructions for this release.