Features applicable to data enrichment and validations

• •You can enrich or validate master records in business applications. However, you can't enrich or validate source records in business applications.
• •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.
• •You can't run enrichment and validation rule associations when users bulk edit records in business applications.
• •You can't enrich or validate patch records.
• •You can't run Application Integration-based validation, enrichment, and cleansing operations when you ingress or import records.
• •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.
• •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 and business entity record fields when you configure rule associations for enrichment, validations, and cleansing. You can't enrich dynamic fields and business entity record fields.
• •The workflow inbox in business applications doesn't display recommendations.
• •You can't use system fields, such as Business ID and Record State, as input fields for data enrichment.
• •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.