Features applicable to data enrichment and validations

• •You can enrich or validate master and source records through business applications and REST APIs.
• •Rule associations for enrichment and validation don't run when users bulk edit records in business applications.
• •You can enrich the attributes of a business entity for which you configure data enrichment. You can't trigger enrichment on the attributes of one business entity and enrich the attributes of another with the same rule association.
• •You can map business entity record fields as input and output fields in a rule association.
• •You can map system fields as input fields in a rule association.
• •When you map input fields, you can map the attributes of a business entity to the enrichment and validation service input fields. You can't map the relationship nodes of a hierarchy model to the enrichment and validation service input fields.
• •You can't map dynamic fields when you configure rule associations for enrichment, validations, and cleansing. You can't enrich dynamic fields.
• •The workflow inbox in business applications doesn't display recommendations.
• •If an objective is configured for both master and source records, rule associations that assign records to hierarchies run only on master records. They don't run on source records.
• •Objectives aren't triggered when users delete field group entries from a record in business applications.
• •You can't run Application Integration-based validation, enrichment, and cleansing operations when you ingress or import records.
• •When you import records into MDM SaaS, you can enrich or validate source records. However, you can't enrich or validate master records during the ingress or import process.