1. New

1.1. DCM Widget flow in Blueriq Encore

In this version we introduce the DCM Widget flow as a new flow type specifically designed to be used with the new DCM Dashboard application. The Widget flow is the connecting piece between the DCM Dashboard application and the Blueriq implementation models.

When you select this flow type you will have a number of new options (highlighted in the screenshots below):

1. The purple highlight: all DCM Widgets flows are always set to exposed. This means they are the entry points of your Blueriq implementation models. Also you should not set this flow type for any other nested or non-DCM-Dashboard flow.
2. The blue highlight: for each entry point of the DCM Widget flow you can set request parameters in a specific tab of the property panel of the flow. In the first version of the DCM Dashboard these request parameters were handled by the AQ_RequestParameter service. Now we have made it a default feature of the flow type so your flow definition is not poluted with boiler plate defitions.
3. The green highlight: the DCM Widget flow has its own exit events. These events will communicate to the DCM Dashboard application. There are three specific events for all actions available in the DCM Dashboard. Each event requires its own parameters to be set, which then of course are linked to the entry point parameters. The exit events replace the dashboard services that were introduced earlier, for which we recommend to update the DCM library.

The new features also required us to update the DCM library and the DCM foundation to accomodate the new patterns. You find the links below in the release notes.

1.2.  Rename and update references in Blueriq Encore

It is now possible to rename any element such as a project, module, global, and moodule element in Blueriq Encore. Just before the actual rename of an element, the affected elements (the renamed element + elements in which references will be updated) are shown in the preview step. If other users are working in an affected element, they will be notified as there will be a save conflict. Encore automatically updates the browser URL that contains the location of the element for you and other users. Renaming a repository an branch is also possible, after which other users working in the same branch at that moment will lose their subscription and have to reopen the repository/branch after getting notified about the rename.

New in Encore compared to Studio is that after renaming a language, all language references will be updated as well. This makes it easier to integrate other libraries in your project.

1.3. Search in Blueriq Encore

From this version, the search is available in Blueriq Encore. 

Highlights:

• Full text search is toggled on by default
• You can filter on anything (project, module, element type, label) within your search to further specify your results.
• The number of (filtered) results are shown. 
• If a result has a description or label, it will be shown. 
• It is possible to open multiple seach views with different search queries.
• The search query is shown in the title of the view in the navigation panel.
• Encore updates the browser URL with your search query, which you can share with your colleagues.
• Last but not least: the search is superfast!

1.4.  New save mechanism in Blueriq Encore

In previous versions of Blueriq Encore, changes were autosaved implicitly after each navigation action. We have received a lot of feedback about this behavior and decided to change it by giving back full control to the Business Engineer about when a change is saved and when not. 

Blueriq Encore will track all changes for you. All changes will be visible on element level from the status bar by clicking this icon: . Here, you can save or cancel them individually or all at once. 

The save and cancel button in the status bar itself will only respond to the currently opened view. In the example below, that is both the element "MainPage" and the reusable container "AirportContainer" as this one is referred to in "MainPage" and edited from the current view.  
 

1.5. Case-Modelling can be used

In Blueriq 16.0, the new Case-Modelling concepts can be used. To get acquainted with the new architecture (formally also known as DCM 2.0), we've backported the changes to this minor of Blueriq 15. The 15.13 version is the first version which can be used in a production environment, since the software has come out of beta. For more information about the container/service changes we've made in this minor, check the Blueriq 16 space of Case-Modelling: Getting started with Case Modelling.

2. Enhancements

3. Changes Platform Support

Our Platform support is updated.

Changes are:

• Support for Microsoft SQL server 2022 has been added
• Support for Microsoft SQL server 2017 has been dropped

4. Upgrade Instructions

The upgrade instructions for this release can be found here.

5. Artifacts

 The Blueriq artifacts are available under name: 15.13.0.1287

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

6. Aquima Libraries

There are specific Library updates for the new DCM architecture including DCM Dashboards:

DCM 2.0.2 library

DCM Foundation v7.1

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

8. Retirement announcement

There are no specific retirement announcements.

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

9. Bug fixes

10. Known issues

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