Blueriq 16.11.3 Bug Fixes

CSD-5335

Studio

Importing a WSDL or XSD could fail if multiple schemas included the same schema file.

Duplicate schema includes are now handled as expected.

CSD-5334

Java Runtime

Query parameters and path segments added to an AQ_RestServiceClient call would not always be URL encoded properly, causing an error when the parameter value would contain special characters, like {, } and ".

This has been fixed. Special characters are now properly URL encoded

BQ-23151

Encore

The domain schema editor would not show errors reported for the "Hide root element" in the editor, only in the validation report.

The editor now shows validation messages for the "Hide root element" below the checkbox,

CSD-5291

Java Runtime

When starting a project with a shortcut and using a test path as query parameter, the main branch would still be started first and subsequent calls would use the test path branch.

When starting a project with a shortcut and using a test path as a query parameter, the version of the shortcut now gets overriden with the test path version.

CSD-5257

Encore

The condition expression of a condition node in a flow was not validated to not be empty, however this would report an error in the runtime project report.

Encore now also validated that the condition expression of a condition node is not empty.

CSD-5252

Encore

Large documents could be slow to open in Encore and require significant memory usage.

The document editor has been optimized to reduce opening times and memory usage.

CSD-5246

Encore

When a page or container ends up including the same flow event with different event types, a cryptic validation error would be reported by the Studio server, but Encore only reported this error for pages, not containers.

Encore now also reports the invalid situation for containers, as well as providing details to guide you to where the flow events have been modeled such that fixing the problem becomes much easier.

CSD-5226

Encore, Studio

When determining whether a value is valid according to the values in a value list, numeric values would only match if they had the exact same text. This meant that e.g. 0.0 was not valid if the value list contained 0.00. This could result in issues with unit tests, where the expected value was required to exactly match the evaluated value.

Encore has been updated to compare value list values according to the datatype. Additionally, unit tests no longer require that the expected value is exactly as evaluated, so differences in decimal points that are 0 no longer cause a test to fail.