/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include An object which defines the list of matching rules to run and has a field
* Rules
, which is a list of rule objects.See Also:
* AWS
* API Reference
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
You can either choose ONE_TO_ONE
or MANY_TO_MANY
as
* the AttributeMatchingModel. When choosing MANY_TO_MANY
, the system
* can match attribute across the sub-types of an attribute type. For example, if
* the value of the Email field of Profile A and the value of BusinessEmail field
* of Profile B matches, the two profiles are matched on the Email type. When
* choosing ONE_TO_ONE
the system can only match if the sub-types are
* exact matches. For example, only when the value of the Email field of Profile A
* and the value of the Email field of Profile B matches, the two profiles are
* matched on the Email type.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.
A list of Rule objects, each of which have fields RuleName
and
* MatchingKeys
.