TOLERANT MPM Release 1.4

2019/11/14

Installations having another name of the system tenant (ID: 1) than ‚MPM‘ must reset its name to this value after the installation of the update in DB table tenant
Before updating an existing MPM installation to version 1.4, the command mpm-db-migrate.sh/bat clearCheckSums must be executed.

Tenant selection element of login page is now only displayed if there is more than one tenant to choose from.
Selection values for customer salutation, title, etc. are now configurable (see manual for details).
The version in the dialog for creating a new text block is no longer pre-filled with „1.0“.
Added an option to define a redirect URL on logout (see manual for details)
The label for the legal entity name in the legal entity tree view is no longer shows empty brackets „()“ if the related description is undefined.
An external reference can now be added to an agreed usage of customer consents.
New fields were added for creating new consent.
It is now possible to load legal entities in batches. This is automatically done at application startup and the legal entities will be cached. All views using the legal entities will now use the cache instead of loading them themself.
Updating of additional attributes of consent texts and customer blockings is now possible.

A new specific error message was added if MPM loader does not find any CSV files to load.
Added optional parameter confirmationDate to confirmPreliminaryConsent API (service) and csv files (MPM loader).
Bundled JRE was upgraded to JRE 8u232 (not applied to existing MPM installations).

Customer queries by external key are now also logged to query log.
Selection values for customer salutation, title, etc. are now configurable (see manual for details).
An external reference can now be added to an agreed usage of customer consents.
Update-API for customer blockings and customer consents and consent texts allows update of description and extra fields of published consent texts.
Customer consents on archived consent texts can now be added for a configurable period after the validTo-date of the consent text.
Limited backdating of customer consentâ€™s capture date (switched off by default).
Customer blocking’s start date can be predated now (switched off by default, see new configuration option resources:customerBlockings:maxPredatingDays).
Added optional parameter confirmationDate to confirmPreliminaryConsent API (service) and csv files (MPM loader).
Consolidation permission status of consolidated-permission-status API now has further attributes mostRelevantCustomerBlockingTypeId, lastCustomerConsentId, ef4 and ef5.

It is now possible to configure the name of the initial tenant at installation.
All MPM scripts now use a consistent EOL format.
Bundled Tomcat version was upgraded from 9.0.14 to 9.0.24 (not applied to existing MPM installations).

TPR-6967: Errormessage in case of missing tenant selection now shows properly.
TPR-7046: The text preview in consent text dialog is now cleared correctly after a change of the consent text language.
TPR-7125: The input field for legal entity type no longer displays a red border when creating legal entities.
TPR-7160: Error message for required attribute name of customer blocking type now matches label of input field.

TPR-7049: The old duplicated DB migration change command was removed.
TPR-7158: Legal entity will now be updated correctly by the service if only external fields have been changed.
TPR-7305: The capture date of the consent is now checked properly against the period of validity of the consent federation.