You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
2. Upgrade Instructions
Migrating from the integrated Document Renderer to Document Renderer Service
As a best practice
- backup your repository
- backup your database before running scripts
- backup your
spring.config.additional-locationdirectory ([Blueriq installation directory]\Runtime) - backup any config files you have altered under [Blueriq installation directory]\Services
before you start the upgrade.
3. Artifacts
The Blueriq artifacts are available under name: 14.10.0.4636
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 3.4.9 |
| DCM Lists Service | 1.4.7 |
| Material Theme | 1.0.42 |
| Development tools | 1.1.1 |
| Document Renderer Service | 0.1.0 |
4. Libraries
In this release, only the set of third party libraries that is used by Blueriq Material was updated. See Material theme frontend libraries - Blueriq Latest - Blueriq Community for the current libraries used in Blueriq Material. 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.
5. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
6. Bug fixes
|
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
|
BQ-15252 |
|
In DCM 2, a message would not be returned to RabbitMQ when an exception occurred while processing the message and when the log level was set to ERROR or FATAL. |
This has been fixed. |
| BQ-15159 | Some audit logging failed to be stored due to missing fields. | The required fields are now included in the log. | |
|
BQ-15125 |
|
When a model containing a DCM_ExecuteTask service call was loaded by the Runtime, the Runtime validation would wrongly show an error mentioning that no service implementation exists for DCM_ExecuteTask. |
This error is no longer shown. |
|
BQ-15124 |
|
When a task has no user, team or role assigned, the DCM_GetTaskInfo service call threw an exception. |
The DCM_GetTaskInfo service no longer throws an exception in this case. |
|
BQ-15093 |
|
When using the timeline publisher, the event for a created document lacks the caseid although specified |
The wrong parameter was read for the caseid, corrected this. |
|
BQ-14885 |
|
When DCM_ThrowAsyncMessageEvent does not have a value for the send to specific case ids parameter, it throws an exception, while it should broadcast the message event to all cases. |
This case has been fixed so broadcasting works again. |
|
CSD-4025 |
Studio |
A change in preview mode could inadvertently persist even if the preview was cancelled. |
A shared element cache was incorrectly mutated during a preview operation, this has been fixed. |
|
CSD-3983 |
Runtime |
Test Paths would not be passed when executing automatic tasks. |
Test Paths are now preserved when starting an automatic task as the result of completing another task or starting an automatic task as the result of a message event. |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools