New

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. The next time When the task is executedretried, the flow will be started containing with the event parameters specified in the retry event node. This way, for example, particular parts of the flow that have already succeeded before the functional error can be skipped based on the parameters. 

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

There are no specific upgrade instructions for this release.

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:

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.

Retirement announcement

There are no specific retirement announcements.

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

Bug fixes

Known issues

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

Security notification