RuleBasedMatchingResponse
¶
Source code in docs_src/capo_customer_profiles/types/rule_based_matching_response.py
attribute_types_selector
instance-attribute
¶
attribute_types_selector: NotRequired[AttributeTypesSelector]
Configures information about the AttributeTypesSelector where the rule-based identity resolution uses to match profiles.
enabled
instance-attribute
¶
enabled: NotRequired[optionalBoolean]
The flag that enables the rule-based matching process of duplicate profiles.
matching_rules
instance-attribute
¶
matching_rules: NotRequired[MatchingRules]
Configures how the rule-based matching process should match profiles. You can have up to 15 MatchingRule in the MatchingRules.
max_allowed_rule_level_for_matching
instance-attribute
¶
max_allowed_rule_level_for_matching: NotRequired[MaxAllowedRuleLevelForMatching]
Indicates the maximum allowed rule level.
max_allowed_rule_level_for_merging
instance-attribute
¶
max_allowed_rule_level_for_merging: NotRequired[MaxAllowedRuleLevelForMerging]
status
instance-attribute
¶
status: NotRequired[RuleBasedMatchingStatus]
PENDING
-
The first status after configuration a rule-based matching rule. If it is an existing domain, the rule-based Identity Resolution waits one hour before creating the matching rule. If it is a new domain, the system will skip the
PENDINGstage.
IN_PROGRESS
-
The system is creating the rule-based matching rule. Under this status, the system is evaluating the existing data and you can no longer change the Rule-based matching configuration.
ACTIVE
-
The rule is ready to use. You can change the rule a day after the status is in
ACTIVE.