You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
2. Enhancements
Enhancement | Details |
---|---|
Renamed AQ_TaskList container to DCM_TaskList. | We have renamed the AQ_TaskList container to Container type: DCM_TaskList, and modified it to be used in conjunction with the case engine. The TaskList container already used the DCM Lists Service as datasource. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Upgrade Instructions
You can find the upgrade instructions for this release here: Release 13.9 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)
before you start the upgrade.
5. Artifacts
The Blueriq artifacts are available under name: 13.9.0.2495
6. Aquima Libraries
The Aquima libraries are updated, see below what has changed:
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-11581 | JAVA Runtime | When a ProcessDataAccessException occurs there is no log of the exception that occurs. | The exception is now logged. |
BQ-11577 | JAVA Runtime | Runtime does not start when both the externaldatasources profile is enabled, but the scheduler-quartz and case-engine profile are not | With the profile configuration as specified, the runtime starts normally. |
CSD-3558 | JAVA Runtime | When using the | Multi value relations that where |
CSD-3535 | JAVA Runtime | When BAAS/BAARS services would report an error to the client, this error would only be logged on DEBUG level in the log file. | Errors that are reported by BAAS/BAARS services are logged on ERROR level now. |
9. Known issues
For an overview of known issue please refer to: Known issues
For 13.9 the following issue is known, which has been resolved in 13.9.1: