Struct aws_sdk_customerprofiles::types::AttributeTypesSelector

#[non_exhaustive]
pub struct AttributeTypesSelector {
    pub attribute_matching_model: AttributeMatchingModel,
    pub address: Option<Vec<String>>,
    pub phone_number: Option<Vec<String>>,
    pub email_address: Option<Vec<String>>,
}

Configuration information about the AttributeTypesSelector where the rule-based identity resolution uses to match profiles. You can choose how profiles are compared across attribute types and which attribute to use for matching from each type. There are three attribute types you can configure:

• Email type

  • You can choose from Email, BusinessEmail, and PersonalEmail

• Phone number type

  • You can choose from Phone, HomePhone, and MobilePhone

• Address type

  • You can choose from Address, BusinessAddress, MaillingAddress, and ShippingAddress

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.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

attribute_matching_model: AttributeMatchingModel

Configures the AttributeMatchingModel, you can either choose ONE_TO_ONE or MANY_TO_MANY.

address: Option<Vec<String>>

The Address type. You can choose from Address, BusinessAddress, MaillingAddress, and ShippingAddress.

You only can use the Address type in the MatchingRule. For example, if you want to match profile based on BusinessAddress.City or MaillingAddress.City, you need to choose the BusinessAddress and the MaillingAddress to represent the Address type and specify the Address.City on the matching rule.

phone_number: Option<Vec<String>>

The PhoneNumber type. You can choose from PhoneNumber, HomePhoneNumber, and MobilePhoneNumber.

You only can use the PhoneNumber type in the MatchingRule. For example, if you want to match a profile based on Phone or HomePhone, you need to choose the Phone and the HomePhone to represent the PhoneNumber type and only specify the PhoneNumber on the matching rule.

email_address: Option<Vec<String>>

The Email type. You can choose from EmailAddress, BusinessEmailAddress and PersonalEmailAddress.

You only can use the EmailAddress type in the MatchingRule. For example, if you want to match profile based on PersonalEmailAddress or BusinessEmailAddress, you need to choose the PersonalEmailAddress and the BusinessEmailAddress to represent the EmailAddress type and only specify the EmailAddress on the matching rule.

Implementations

impl AttributeTypesSelector

pub fn attribute_matching_model(&self) -> &AttributeMatchingModel

Configures the AttributeMatchingModel, you can either choose ONE_TO_ONE or MANY_TO_MANY.

pub fn address(&self) -> &[String]

The Address type. You can choose from Address, BusinessAddress, MaillingAddress, and ShippingAddress.

You only can use the Address type in the MatchingRule. For example, if you want to match profile based on BusinessAddress.City or MaillingAddress.City, you need to choose the BusinessAddress and the MaillingAddress to represent the Address type and specify the Address.City on the matching rule.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .address.is_none().

pub fn phone_number(&self) -> &[String]

The PhoneNumber type. You can choose from PhoneNumber, HomePhoneNumber, and MobilePhoneNumber.

You only can use the PhoneNumber type in the MatchingRule. For example, if you want to match a profile based on Phone or HomePhone, you need to choose the Phone and the HomePhone to represent the PhoneNumber type and only specify the PhoneNumber on the matching rule.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .phone_number.is_none().

pub fn email_address(&self) -> &[String]

The Email type. You can choose from EmailAddress, BusinessEmailAddress and PersonalEmailAddress.

You only can use the EmailAddress type in the MatchingRule. For example, if you want to match profile based on PersonalEmailAddress or BusinessEmailAddress, you need to choose the PersonalEmailAddress and the BusinessEmailAddress to represent the EmailAddress type and only specify the EmailAddress on the matching rule.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .email_address.is_none().

impl AttributeTypesSelector

pub fn builder() -> AttributeTypesSelectorBuilder

Creates a new builder-style object to manufacture AttributeTypesSelector.

Trait Implementations

impl Clone for AttributeTypesSelector

fn clone(&self) -> AttributeTypesSelector

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AttributeTypesSelector

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for AttributeTypesSelector

fn eq(&self, other: &AttributeTypesSelector) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for AttributeTypesSelector