You are viewing the documentation for Blueriq 13. 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 5 Next »



1.  New

1.1.  Additional logging

Identifier Component Issue Solution
CSD-3897 DCM Logging about tasks was not sufficient to be able to analyze what happened in case of an error. Added log entries at INFO level for task operations, including Case Id and Task Id.









On this page:

2. Enhancements

Enhancement Details






3. Usability Improvements

Several usability improvements were made to the studio. These originate from the votes that our users have given here: Vote for usability improvements. A new list is posted, so please vote for fresh usability improvements.

Improvement Details





4. Documentation

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

5. Changes Platform Support

Our Platform support is updated.

Changes are:

  • XXX

6. Upgrade Instructions

There are no specific 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.

7. Artifacts

 The Blueriq artifacts are available under name: 13.x.xxx

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

Component

Version

Customer Data Service 3.4.1
DCM Lists Service 1.4.1
Material Theme 1.0.40
Development tools 1.1.0

8. Aquima Libraries

There are no specific Library updates for this release.

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

ArtifactId

GroupId

License

Version in 14.6.0

Version in 14.6.1

jboss-rmi-api_1.0_spec

org.jboss.spec.javax.rmi

LGPL 2.1

1.0.6.Final

(error)

asm

org.ow2.asm

3-clause BSD License

9.1

9.2

cxf-core

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-bindings-soap

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-bindings-xml

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-databinding-jaxb

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-frontend-jaxws

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-frontend-simple

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-transports-http

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-ws-addr

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-ws-policy

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

cxf-rt-wsdl

org.apache.cxf

Apache License 2.0

3.4.4

3.4.5

ArtifactId GroupId License Version in 3.1.x (Blueriq 13.x.x)

Version in 3.1.x (Blueriq 13.x.x)







ArtifactId

GroupId

License

Version in 1.1.x (Blueriq 13.x.x)

Version in 1.1.x (Blueriq 13.x.x)


10. Retirement announcement

There are no specific retirement announcements.

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

11. Bug fixes

Identifier

Component

Issue

Solution

CSD-3947

JAVA Runtime

When starting a child session via the AQ_StartProject service with a configured test path. The service calls in the started project's flow, which are before the first page, are not affected by the propagated test path.

We have resolved the issue by copying the test configured test path onto the child's session before the flow is started.

CSD-3943

JAVA Runtime

The development dashboard won't display projects when two published models have the same export date.

When two published models contain the same branch name and export date but different revision the new development dashboard was not able to distinguish them and it resulted into an error when loading the projects. This has been resolved.

CSD-3946


A domain schema preview in Studio would fail if the target entity of a relation did not have the same capitalization as the entity's definition name.

The target entity name of a relation is now used in a case-insensitive way.

CSD-3941

JAVA Runtime

Fields did not properly supported domains with invalid domain options

Corrected the code to handle invalid domain options in the correct way

CSD-3923

JAVA Runtime

When reloading a project where the flow contains an active instance of a singleton entity, an instance id mismatch error is thrown.

When reloading a project the previous state of the active sessions is transferred onto the newly created sessions. While transferring the profile, new singletons instances were created. Resulting in new instance ids for which causes the mismatch. This is resolved by reusing the old instance id, which was already the case for multiton instances.

CSD-3890, CSD-543

JAVA Runtime

The file upload container allowed file type validation was case sensitive in material theme

Updated the validation algorithm to case insensitive

BQ-13195


For BAA(R)S endpoints that have a shortcut, the test path would always be read from the HTTP request, even in production mode. Test Paths are a development only feature.
If test path properties were present for the shortcut of the BAA(R)S, an attacker could provide a X-Blueriq-TestPath header and a different branch than the intended branch would be used to execute the BAA(R)S service.

Test path properties will now be ignored when running Blueriq Runtime in Production Mode.

12. Known issues

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

13. Security notification



  • No labels