Versions Compared

Old Version 11

changes.mady.by.user Timo Schrijvers

Saved on

compared with

New Version 12

changes.mady.by.user Randy Anft

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Release Date

 

ContentRelease 17.6
Download

UI Button
colorpurple
icondownload
titleDownload Blueriq
urlhttps://my.blueriq.com/display/CUS/Customers+Home

Panel

On this page:

Table of Contents
maxLevel1
stylenone
Numbered Headings
start-numbering-with1

New

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 are supported
  • Specify a file by uploading it or providing the URL of the documentation

Read more about OpenAPI import here

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. 

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 Blueriq 18, the functionality for using the runtime application for the case engine will be removed.

Enhancements

EnhancementDetails
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.

Feedback after a backup restore in Encore

A green feedback message will now pop up after a backup has been restored successfully in Encore.

URL and HTTP method or REST calls in runtime log

The HTTP method and URL of a rest 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 now always ends with a slash

The runtime now ensures that a base URL of REST request always ends with a slash.

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

There are no specific upgrade instructions for this release.

Tip

As a best practice

  • backup your repository
  • backup your database before running scripts
  • backup your 
    Include Page
    _HomeFolder
    _HomeFolder
     directory ([Blueriq installation directory]\Runtime)
  • backup any config files you have altered under [Blueriq installation directory]\Services

before you start the upgrade.

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 Service5.0.x
DCM Lists Service4.0.x
Material Theme1.3.x
Development tools frontend2.0.x
DCM Maintenance App5.0.x
Audit Consumer1.0.x
DCM Dashboard Service2.0.x
Gateway Service1.1.x
Document Renderer2.2.x

Blueriq Libraries

There are no specific Library updates for this release.

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.

UI Expand
titleThird-party libraries Java Runtime
ArtifactIdGroupIdLicenseVersion in 17.x.xVersion in 17.x.x
UI Expand
titleThird-party libraries Persistence API for customer data
ArtifactIdGroupIdLicenseVersion in 4.2.x (Blueriq 17.x.x)

Version in 4.2.x (Blueriq 17.x.x)

Retirement announcement

There are no specific retirement announcements.

For a full list of deprecated features, go to Deprecated features.

Bug fixes

Include Page
Blueriq 17.x Bug Fixes
Blueriq 17.x Bug Fixes

Known issues

For an overview of known issue please refer to: Known issues

Security notification