Document Renderer Service - Improvements/changes

• We changed the default font from Arial to Roboto and included the TrueType font files needed for that to work out of the box. Although Arial and Roboto are quite similar, your generated PDF documents might be different if you use the defaults.
• In order to improve the performance (RAM usage) of the Document Renderer Service we added a font allowList to the service configuration. If you don't rely on the default configuration you must add one or more entries to the font allowList, depending on the actual fonts you use in your documents.

Material Theme - @blueriq/dashboard

In order to connect to the new API of the DCM Dashboard Service we have introduced a new Module in the @blueriq/dashboard package which is release in version 0.18.8. The main changes for the Material theme, for version 1.4.0, can be found in this commit on github.com. With the introduction of the new `BlueriqDashboardModule` we have moved a lot of the implementation from Material Theme to the @blueriq/dashboard package. Refer to the getting started documentation, on how to use the new Module in comparison to the Legacy `DashboardBackendModule`.

DCM Dashboard Service - context path

In version 1.2.1 of the DCM Dashboard Service we have added a new default context path: /dcm-dashboard. This could have impact on your current services which connect to the DCM Dashboard Service. 

Gateway Service configuration

In the Gateway Service configuration a route is configured to connect to the DCM Dashboard Service. This route configuration needs to be updated to the following, for the legacy API of the Dashboard Service to still work.

spring:
  cloud:
    gateway:
      routes:
        - id: dashboard
          uri: http://<host>:<port>
          predicates:
            - Path=/dcm-dashboard/**
        - id: legacy-dashboard
          uri: http://<host>:<port>
          predicates:
            - Path=/dashboards/**
          filters:
            - PrefixPath=/dcm-dashboard

The legacy endpoint will still use '/dashboards' route but it will send a context path prefix of /dcm-dashboard so the DCM Dashboard Service understands what is happening.

 SDK Changes

Added classes

Modified classes

Known issues

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