You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
1. Enhancements
Enhancement | Details |
---|---|
Button to migrate to the asynchronous service call |
We introduced the DCM_ThrowAsyncMessageEvent service call, which can be used to throw a message event asynchronously to the case engine. This has the advantage that the user does not have to wait for the result of message event. To easily migrate to this service, the AQ_ThrowMessageEvent service calls now have a migration button which when pressed migrates the service call to the new service type DCM_ThrowAsyncMessageEvent. Note that this migration button can only be used when:
Also note that you can only use this new service type when you use the case engine. The AQ_ThrowMessageEvent service type is still valid for the use case where you do need to know which cases are affected. The asynchronous version of the service call, is only applicable when the case engine is used (the new DCM setup). For now, most projects can dely on the synchronous message event service and don't need to migrate. |
2. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
3. Upgrade Instructions
You can find the upgrade instructions for this release here: Release 13.6 Upgrade Instructions.
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: 13.6.0.2000.
5. Aquima Libraries
There are no specific Library updates for this release.
6. 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.
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 |
---|---|---|---|
CSD-3374 |
Runtime |
When the Publisher Artifactory client is used sometimes the wrong version of a project is used. In contrast to the database version of the Publisher client, the list of projects from the Artifactory client was NOT sorted at all. |
Sort the published projects by ascending exportdate for the Artifactory client (same behavior as for the Database variant) |
CSD-3427 |
Studio |
The history view did not take into account non-sequential commit times on subsequent revisions. Non-sequential commit times are normally not possible, but git allows it, and in this instance it occurred due to a bug in the sdf migration tool. |
Because non-sequential commit times is explicitly allowed in git (for example for the rebase workflow), revision ordering logic for the history view has been rewritten to take this into account. |
BQ-10797 |
Runtime |
The Spring libraries used by Blueriq contain CVE-2020-5421. |
Upgraded the underlying Spring libraries to a version in which the CVE has been fixed. |
CSD-3413 |
Studio |
In the new version management system, the behaviour of tags has changed without being documented. Tags are now stricter but it's unknown how and sorting is not possible anymore. |
Due to the internal workings of the new version management system, some features are removed and or restricted regarding tags. |
CSD-3412 |
Studio |
When Studio was configured to use NTLM/Kerberos authentication, no repositories could be loaded. |
The Studio Server is now able to authenticate itself with the history server, allowing repositories to be loaded. |
CSD-3261, CSD-3409 |
Runtime |
If two AQ_InstanceLinker containers are present on the same page, linking to the same relation, it's not possible to deselect a value. |
Instead of merging the values of both AQ_InstanceLinker containers, the last updated container's value is used to set both container's value. If both are changed, the values will still merge. |
CSD-3402 |
Runtime |
When a new Portal message handler would be registered during handling a portal message, an error would occur. |
We fixed the underlying issue, allowing to register a new Portal message handler without errors when handling messages. |
CSD-3379 |
Runtime |
When the runtime creates a new session for switching between widgets and projects, attributes are copied to the newly created session, although testPath was missing at one place. |
The testPath is added to the list attributes to copy between old an newly created sessions. |
BQ-10774 | Studio | The default IIS configuration had Windows Authentication enabled for the Studio Server, which prevented Studio authentication using NTLM/Kerberos from working. | The IIS configuration is corrected such that Windows Authentication is no longer enabled by default. In earlier versions of Blueriq this can be done manually as documented here. |
9. Known issues
For an overview of known issue please refer to: Known issues