Rules and guidelines for migrating rule associations
Consider the following rules and guidelines after you migrate your basic, advanced, and DaaS rule associations to use Enrichment and Validation Orchestrator:
•When you run ingress or file import jobs, MDM SaaS runs all migrated rule associations in the load step.
•When you import or ingress records without mapping input fields from migrated rule associations configured to run even if all input fields are empty, MDM SaaS runs these associations.
•When import or ingress records with picklist values, MDM SaaS retains the values that you import even if they aren't available in the enterprise code list.
•If you delete a business entity, Business 360 Console automatically deletes the rule associations that are automatically generated. However, if you created rule associations, ensure that you manually delete them.
Ohterwise, you can't delete the business entity because of existing dependencies.
•When you configure advanced rule associations for decimal fields with a defined scale, ensure that the decimal values that you enter don't exceed the configured scale. If the values exceed the configured scale, after migration, Enrichment and Validation Orchestrator runs the rule associations and displays an exception on the Data Quality Status tab in business applications. However, the value is still saved to the record.
•After you migrate basic rule associations that use the concatenation function with a constant value, the equivalent rule association in Enrichment and Validation Orchestrator runs even if one of the input field value is null. The rule association concatenates the field values and applies the constant value as the output.
•After you migrate rule associations that are configured to return a default value when an the input field is empty, the rule association runs to populate the empty fields with the specified default value. Subsequently, when you update records, the rule association runs only for the fields that you update.