Upgrading 10.2 to 10.3

When migrating to a new Cadenza version:

  1. Check and update database schemas using the Database Migration Tool.

    • Backup your database before running the tool, as schema structures may change.

  2. Apply migrations sequentially for each intermediate version. Skipping versions can break functionality or cause unintended side effects.

Branding and Customizing

Configuration Changes

Removal of allow and deny export settings in core config

The settings of export type-specific restrictions defined in the elements exportAllowList and exportDenyList should be removed from your configuration as they are no longer supported.

New default language in openrouteservice config

The service > tuning > language setting now uses the Cadenza language by default instead of "de" to support a more consistent user experience.

In practice, this change will probably not require any action, but you might want to check that the routing results are displayed correctly: If not, you can revert to "de".

Breaking Changes in temporaldataanimation config

If the Gis_Temporal_Data_Animation plugin is activated, the maximumDisplayPointCount setting must be removed. The value of the previous default property must instead be set as the new maximumPointCountInTail setting that better describes its purpose.

GPX-import in plugins.xml config

If you were previously using GPX import, and you can no longer see it, you need to activate the new plugin Gpx. It used to be included in the Import_Temporal_Data plugin.

Removal of per-Secret Encoding Settings

After the introduction of a global option whether secrets are encoded, per-setting options are now removed. All of these now use the global setting secretHandling in core settings instead. If that is not configured, all secrets are considered encoded.

You must check and potentially change the following configurations:

auditlogging config

When configuring an appender with class HibernateAuditLogAppender, a param with name value passwordEncrypted is no longer supported.

mailclient config

The settings outgoingServer > authorization > login > password > encrypted and outgoingServer > authorization > plain > password > encrypted have been removed.

monitoring-publishers config

The setting authentication > password > encrypted has been removed.

userpreferences config

The setting database > password > encrypted has been removed. At this opportunity, the already-deprecated setting database > connectionIdleTimeout has been removed, too.

what3wordsweb config

The settings services > service > apiKey > encrypted and services > service > authentication > password > encrypted have been removed.

repository list

The setting databaseRepository > password > encrypted has been removed. At this opportunity, the already-deprecated settings databaseRepository > connectionIdleTimeout and databaseRepository > polling have been removed, too.

If until now your configuration had mixed secrets with some being encoded and some in plaintext, you will have to standardize on one approach.

In case all secrets were present in their encoded form already, and you are using the XML configuration approach, you should only have to remove the encrypted="true" attributes where they are present.

When using configuration using YAML or environment variables, leaf value fields must be merged on their parent. For example,

cadenzaconfig:
  userpreferences:
    database:
      password:
        encrypted: true
        value: "aabbccdd"

becomes

cadenzaconfig:
  userpreferences:
    database:
      password: "aabbccdd"