Configure Survivorship > Order of execution for survivorship configuration
  

Order of execution for survivorship configuration

To identify the most trusted field values from multiple source records, MDM SaaS uses the survivorship configuration. The survivorship configuration includes survivorship rules and source system ranking. MDM SaaS also uses the source last updated date and last updated date in MDM SaaS to identify the trusted values.
The following image shows the order of execution for survivorship configuration:
The image shows that the survivorship rules are executed first. The source system ranking, system last updated date, last updated record, and last created record are then considered.
The following table lists the order in which survivorship configurations are executed:
Survivorship configuration
Description
Survivorship rules
The field value that satisfies the survivorship rule survives. If fields have the same value or trust score, MDM SaaS proceeds to the next comparison. For example, when a minimum rule is applied to the availability date field, the value with the earliest time stamp survives. Consider two source records with availability date values of Jan 1, 2024, and Jan 3, 2024. The value of Jan 1, 2024, survives. However, if records share the same date or trust score, MDM SaaS can't determine which field value to survive since there isn't a single value that can be trusted. In such cases, MDM SaaS proceeds to the next comparison.
Source system ranking
If trust scores differ, the value from the highest-ranked source system survives. If trust scores are equal, MDM SaaS proceeds to the next comparison.
Source last updated date
The field value that belongs to a record with the most recent source last updated date survives. However, when records have the same source last updated date, MDM SaaS can't determine the value to survive. In such cases, MDM SaaS proceeds to the next comparison.
Last updated record in MDM SaaS
The field value that belongs to a record with the most recent update in MDM SaaS survives. However, when records have the same last updated date, MDM SaaS can't determine the value to survive. In such cases, MDM SaaS proceeds to the next comparison.
Latest created record in MDM SaaS
The field value of the record that was most recently created in MDM SaaS survives.