MDM 14.5.2 Upgrade Notes
14.5.2-patch2
Matching issue
Applies to production environments. Follow these steps to ensure the data is matched correctly.
| We recommend performing this during the version change to avoid additional downtime. |
Before the patch deployment:
-
Define the reprocess operation within a valid plan, see Batch Interface, section Reprocess operation.
-
As the input for the reprocess operation, add all instance records with
eng_creation_dateon or after the date of the version 14.5.1 or 14.5.2 deployment.If your MDM solution relies on the rematch flag set in the matching plan and/or has special conditions set using rematchIfChanges, you need to extend the range of records to reprocess accordingly. Identifying such records might be complex and require analyzing the data history. -
Make sure the rematch flag in the reprocessing plan is set to
true.
After the patch deployment, run the operation. The data is now matched correctly.
| All manual exceptions applied to reprocessed records will be removed. |
Configuration changelog
| Applies to version 14.5.2-patch2 and later. |
This section provides the information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.
The following table lists the configuration files that were added, changed, or removed.
| Added files | Changed files | Removed files |
|---|---|---|
/ |
MDM Server |
/ |
The following table lists the changes in the files: added, changed, and removed properties.
| Configuration file | Added properties | Changed properties | Removed properties |
|---|---|---|---|
MDM Server application.properties |
Rate limiter configuration for MDM REST APIs:
See Rate Limiter. |
/ |
/ |
Was this page useful?