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

1. Enhancements

Enhancement Details
Directly open the project view from the navigation menu in Encore

You can now ctrl + click or shift + click on the project or module in the navigation menu in Blueriq Encore to open the project structure or module structure view.


Selected module scope taken into account during navigation in Encore

Previously, it could happen that in Encore, you would get a slightly different view on an element when opening it from the navigation panel compared to opening it from an overview such as the search or validation report. Encore now takes the module scope into account when opening elements from overviews so that the view would be the same as when the element is opened from the navigation panel. This avoids losing access to specializations and prevents opening a separate module group when the module is in scope of the module that is open.

Warning for element names that correspond with expression keywords removed from Encore

Blueriq Encore would report a validation warning for various domain elements (e.g. entities and attributes) with the same name as a Blueriq expression keyword. This validation has been removed as expression keywords are case-sensitive, so elements using the same names as a keyword can be used in expressions with different capitalization.

Composing documents

Added a property to indicate whether failed elements in documents should throw an error or wrap the elements and continue. See Compose document properties for more information.

Ability to start sessions directly on the backend, then redirecting to an arbitrary URL.

The UI REST API has gained new the endpoint GET /api/v2/session/init which mirrors the existing POST /api/v2/start endpoint, with the distinction that it doesn't return JSON but it initiates a redirect using an HTTP 302 See Other response. The target URL to redirect to has to be specified using the redirectUrl  query parameter.

This endpoint has been designed to support the use-case of directly starting a Blueriq session, e.g. from a login operation where the authentication details and/or query parameters are directly made available to the Blueriq Runtime. This is in contrast to the POST /api/v2/start  endpoint which is typically called from a browser frontend. However, that also means that the frontend has to make an effort to forward any query paramaters to the Runtime as desired, and it is limited in the sense that HTTP headers cannot be forwarded at all. The new endpoint allows for inverting the sequence of events: first arriving at the Runtime and only then forwarding to a frontend application.

2. Documentation

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

3. Upgrade Instructions

See Release 17.9 Upgrade Instructions 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.

4. Artifacts

 The Blueriq artifacts are available under name: 17.9.0.332

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

Component

Version

Customer Data Service 5.1.4
DCM Lists Service 4.1.5
Material Theme 1.5.0
Development tools frontend 2.0.2
DCM Maintenance App 5.1.3
Audit Consumer 1.2.3
DCM Dashboard Service 2.2.4
Gateway Service 1.3.2
Document Renderer 2.4.1

5. Blueriq Libraries

There are no specific Library updates for this release.

6. Libraries

For this release there are no specific Library updates.

7. Retirement announcement

There are no specific retirement announcements.

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

8. Bug fixes

Identifier

Component

Issue

Solution

BQ-24541

 

The DCM installation was missing essential files during the release.

The build scripts have been fixed and the files are included again.

CSD-5833

 

In a CSV Resource Connection, multiple empty lines within a quoted value would be merged into a single new line.

This has been fixed. Multiple newlines within quoted values are preserved. Empty lines outside of quoted values are still ignored.

BQ-24505

Java Runtime

When adding a header to an action worklist column and enabling the usage of task names as action name, sorting would be added to that column resulting in a crash of the frontend.

Removed the sorting from these kinds of columns.

BQ-24498

Encore

The OpenAPI import would process top-level arrays incorrectly, where the domain schema had a singlevalued relation. Additionally, it generated an additional inline domain schema (and corresponding domain elements) where another domain schema could be reused.

The OpenAPI generator has been corrected for this scenario.

BQ-24476

Studio

Using Encore to create repository backups could fail if the backup was larger than 2GB.

Backup files larger than 2GB can now be downloaded using Encore.

BQ-24437

 

Whenever the 'display task name' is enabled in a work list in your model, an error occurs when the runtime tries to construct the work list.

The 'display task name' toggle no longer causes the work list to break.

CSD-5765

 

Image metadata can contain "EXIF Orientation" this however was not taken into account in the Document Renderer

When a image has a "EXIF Orientation" it is resampled during the rendering of the PDF, which results in an image which is rotated according to the "EXIF Orientation".

CSD-5802

 

When using External Flows, the target runtime would not inherit the language from the host runtime.

The language in the target runtime will now be inherited from the host runtime, provided that the language is also available in the target runtime.

CSD-5794

 

In a data mapping, no error was reported for an empty context expression of an instance mapping, whereas it is required in the runtime.

Empty context expressions are now reported as an error in Encore.

BQ-24178

 

In IIS the regex used to determine the protocol for rewriting a URL is wrong when the URL contains another URL as argument.

The regex to determine the protocol has been made more specific so it only matches the protocol, regardless of the URL contains another URL as argument or not.

9. Known issues

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



  • No labels