Interface RuleBasedProperties.Builder

All Superinterfaces:
Buildable, CopyableBuilder<RuleBasedProperties.Builder,RuleBasedProperties>, SdkBuilder<RuleBasedProperties.Builder,RuleBasedProperties>, SdkPojo
Enclosing class:
RuleBasedProperties

public static interface RuleBasedProperties.Builder extends SdkPojo, CopyableBuilder<RuleBasedProperties.Builder,RuleBasedProperties>
  • Method Details

    • attributeMatchingModel

      RuleBasedProperties.Builder attributeMatchingModel(String attributeMatchingModel)

      The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When choosing MANY_TO_MANY, the system can match attributes 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.

      Parameters:
      attributeMatchingModel - The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When choosing MANY_TO_MANY, the system can match attributes 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.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • attributeMatchingModel

      RuleBasedProperties.Builder attributeMatchingModel(AttributeMatchingModel attributeMatchingModel)

      The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When choosing MANY_TO_MANY, the system can match attributes 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.

      Parameters:
      attributeMatchingModel - The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When choosing MANY_TO_MANY, the system can match attributes 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.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • rules

      A list of Rule objects, each of which have fields RuleName and MatchingKeys.

      Parameters:
      rules - A list of Rule objects, each of which have fields RuleName and MatchingKeys.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • rules

      A list of Rule objects, each of which have fields RuleName and MatchingKeys.

      Parameters:
      rules - A list of Rule objects, each of which have fields RuleName and MatchingKeys.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • rules

      A list of Rule objects, each of which have fields RuleName and MatchingKeys.

      This is a convenience method that creates an instance of the Rule.Builder avoiding the need to create one manually via Rule.builder().

      When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to rules(List<Rule>).

      Parameters:
      rules - a consumer that will call methods on Rule.Builder
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also: