DCM case data properties

The property for removing aggregates when a case gets closed has been changed.

blueriq.case.engine.data.remove-aggregates-on-case-close = false

blueriq.case.engine.data.general.remove-aggregates-on-case-close = false

JsonPath expressions for mapping JWT claims

With this release, we introduced JsonPath expressions for expressing paths to JWT claims to allow our customers more flexibility. The JsonPath expressions replace the old, comma-separated list of path elements. To move from the old format to a JsonPath expression, one would typically prepend the legacy expression with $. and replace all commas with dots. For example, the legacy expression realm_access,roles should be replaced by $.realm_access.roles, and the legacy expression preferred_username should be replaced by $.preferred_username.

The following properties should be migrated to the new JsonPath format:

Runtime:

• blueriq.security.jwt-claims.username-path
• blueriq.security.jwt-claims.roles-path
• blueriq.security.jwt-claims.teams-path
• blueriq.security.jwt-claims.claim-mapping.*

Please note that for the Runtime, we introduced a legacy toggle to enable the old comma-separated expression format. Please refer to Legacy Properties for more information.

DCM Maintenance App:

• blueriq.jwt.roles-path
• blueriq.jwt.username-path

DCM Dashboard Service:

• blueriq.jwt.roles-path
• blueriq.jwt.username-path

DCM Dashboard Service exports

With the release of the DCM Dashboard modelling in Encore we have removed the JSON export format from the 1.0.0 of the DCM Dashboard Service. The JSON format can still be used in the 0.4.0 version which will be latest version that contains both exports formats to allow a transition period from between JSON exports and modelled exports. See DCM Dashboard overview on how to create a dashboard in Encore.

Customer data service event publisher properties

To be able to publish event messages, the event channel needs to be configured in blueriq-customerdata-odata-service-v1-entity-event-publisher-amqp.yml. This file can be found at <Blueriq installation folder>\Services\blueriq-customerdata\conf. The properties to configure the event publisher have been changed.

# RabbitMQ configuration
spring:
  rabbitmq:
    host: localhost
    port: 5672
    virtualHost: /
    username: guest
    password: guest
    dynamic: false
    ssl:
      enabled: false

# Aggregate event channel configuration
blueriq:
  customerdata:
    aggregate-event:
      channel:
        amqp:
          exchangeName: CustomerDataService

blueriq:
  customerdata:
    aggregate-event:
      channel:
        amqp:
          rabbitmq:
            host: localhost
            port: 5672
            virtualHost: /
            username: guest
            password: guest
            ssl:
              enabled: false
            exchangeName: customerDataService
 

Known issues

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