You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

1. New

1.1.  Start DCM Dashboard projects from Encore in the Material Theme in development mode

It is now possible to directly start a dcm dashboard from Encore in Material Theme. With the introduction of the loading dashboard projects from encore we have added a new API to DCM Dashboard service, which deprecates the old API. To take full advantage of this new feature it is mandatory to use the DCM Dashboard Service v1.2.1 and update your Material Theme version to 1.4.1 or update you @blueriq packages to 0.18.7 in you custom frontend project. 

It is not only possible to start dcm dashboard from Encore, but we now also support multiple version of the same dashboard projects when running from exports. More information on how to connect the DCM Dashboard Service to Encore can be found here: Blueriq DCM Dashboard Service.

Please visit the upgrade instructions on how to connect the new DCM Dashboard Service API in your own custom theme. 

1.2.  Configurable null value allowance in REST connectivity

As a Business Engineer, you can now control if the value of an item in the interface for REST connectivity (a domain schema) can be null or not. This feature enhances data validation by letting the Business Engineer specify which fields must contain data, ensuring better data integrity. This setting affects both incoming and outgoing messages and can simply be toggled for each item (attribute or relation) and is included in the OpenAPI feed and import as well.

2. Enhancements

Enhancement Details

DCM Dashboard Service behind a context path

By the default the DCM Dashboard Service now runs behind the /dcm-dashboard context path, meaning that every request to the DCM Dashboard Service should start with /dcm-dashboard. Please visit the upgrade instructions to determine the impact.

Blueriq Runtime Development Dashboard:

Runtime Configuration Sanitization

In the Blueriq Runtime Development Dashboard, OS Environment Variables and Java System Properties will now be sanitized. The values for keys that might be might contain sensitive data will be replaced by a placeholder (******). Keys that should be sanitized are configurable through Development Properties.

Display task name on action button in worklist

In a worklist it is possible to add an action button to start a task. Besides a button with a fixed name, there is now an option to use the display name of the task as well. When this option is toggled in encore, the display name of the task is used as button caption in the worklist.

Added Reply-To parameter to AQ_MailService

The optional reply-to-addresses-expr parameter has been added to the AQ_MailService service type. The parameter can be set in Encore when using the latest BlueriqBasicModelling Library and can be overridden through Connections Properties.

FlowType "ExecuteTask"

FlowType "ExecuteTask" has been renamed to "AutomaticTask". For more information Flow type: Execute task

TAB to select an item from a dropdown in Encore

When tabbing away from a dropdown in Encore, the highlighted value will now be selected.

Context menu improvements in Encore
  • Items in different context menus across Encore now have the same ordering.
  • From this release, all context menus can be opened using a right mouse click.
  • Icons are used for items to improve recognizability.
Import options in the navigation menu in Encore
The import of a WSDL, XSD, OpenAPI file, or .docx document in Encore can now also be initiated via the navigation menu of the corresponding output element where this as previously only possible using the context menu of the branch. 

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 has been updated.

Changes are:

  • Added support for RabbitMQ 4.0
  • Added support for MongoDB 8.0
  • Removed support for RabbitMQ 3.12
  • Removed support for MongoDB 6.0

5. Upgrade Instructions

See Release 17.7 Upgrade Instructions [Editor] for the upgrade instructions for this release.

As a best practice

  • backup your repository
  • backup your database before running scripts
  • backup your spring.config.additional-location directory ([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.7.0.242

This release includes these versions of Blueriq components with a separate life cycle:

Component

Version

Customer Data Service 5.1.2
DCM Lists Service 4.1.3
Material Theme 1.5.0
Development tools frontend 2.0.2
DCM Maintenance App 5.1.1
Audit Consumer 1.2.1
DCM Dashboard Service 2.2.1
Gateway Service 1.2.0
Document Renderer 2.2.2

7. Blueriq Libraries

For this release, the BlueriqBasicModelling Library 1.4.0 has been updated. Please upgrade to the latest BlueriqCompleteLibraries Package.

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.

TODO

9. Retirement announcement

There are no specific retirement announcements.

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

10. Bug fixes

Identifier

Component

Issue

Solution

BQ-24170

Encore

The entity editor would not restore the scroll position of the attribute and relation lists when switching between views.

The scroll position is now restored as expected.

CSD-5706

Encore

Various dropdowns could be inadvertently clipped, preventing the ability to scroll.

Some dropdowns have been updated to be positioned in front of their container, avoiding the clipping issue.

BQ-24155


The default error exchange for the DCM Lists Service RabbitMQ connection had the wrong value.

It now references the right exchange.

BQ-24138

Encore

It was possible to model service and function calls in contract modules in Encore even though this is not allowed

Removed the ability to model service and function calls from contract modules in Encore

BQ-24084

Studio

An error could occur when importing certain Word documents.

The error has been addressed.

BQ-24079


When a retry event node is taken, the task lock is also removed.

The task lock is now kept so the retry can happen using the same task lock and happens immediately.

CSD-5650

Studio

The Studio server could incorrectly detect a cycle in process type restrictions, even if the structure of process types was not actually cyclic.

The cycle detection has been improved to avoid the false positive.

BQ-24064

Java Runtime

In some setups, the AQ_MailService service call would always fail when trying to send an email because of missing runtime dependencies due to changes in third party libraries.

The AQ_MailService has been fixed by providing the right dependencies.

BQ-24056

Studio Backup Tool

CVE-2024-47554 was reported on a dependency (commons-io) of the Studio Backup Tool

The dependency has been updated to the latest version, which contains a fix for the CVE

CSD-5608

Encore

Various process validations were missing in Encore:

  • Nodes which are not connected to end nodes were not reported.
  • Process type which does not allow task implementation and does not contain any restrictions.
  • Subprocesses were always allowed to be placed regardless of the restrictions in the process type.
  • Tasks were always allowed to be placed in a process regardless of the allowed implementation of the process type.

All of these aspects are now validated in Encore, enabling feedback during modelling for situations that would be reported as error in the runtime

BQ-23739

Java Runtime

When using external flows the target runtime didn't get any notification upon closing the host session. This meant that when a session on the host runtime is closed, the target runtime external sessions weren't closed

Implemented a Listener which sends a notification to the target runtime when a host sessions gets closed

11. Known issues

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

12. Security notification



  • No labels