Interface RuleBasedProperties.Builder

All Superinterfaces:
Buildable, CopyableBuilder<RuleBasedProperties.Builder,RuleBasedProperties>, SdkBuilder<RuleBasedProperties.Builder,RuleBasedProperties>, SdkPojo
Enclosing class:
RuleBasedProperties
@Mutable @NotThreadSafe public static interface RuleBasedProperties.Builder extends SdkPojo, CopyableBuilder<RuleBasedProperties.Builder,RuleBasedProperties>

  • Method Details

    • rules

      RuleBasedProperties.Builder rules(Collection<Rule> 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

      RuleBasedProperties.Builder rules(Rule... 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

      RuleBasedProperties.Builder rules(Consumer<Rule.Builder>... 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:

    • attributeMatchingModel

      RuleBasedProperties.Builder attributeMatchingModel(String attributeMatchingModel)

      The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

      If you choose 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 attribute type.

      If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

      Parameters:
      attributeMatchingModel - The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

      If you choose 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 attribute type.

      If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

      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.

      If you choose 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 attribute type.

      If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

      Parameters:
      attributeMatchingModel - The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

      If you choose 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 attribute type.

      If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • matchPurpose

      RuleBasedProperties.Builder matchPurpose(String matchPurpose)

      An indicator of whether to generate IDs and index the data or not.

      If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

      If you choose INDEXING, the process indexes the data without generating IDs.

      Parameters:
      matchPurpose - An indicator of whether to generate IDs and index the data or not.

      If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

      If you choose INDEXING, the process indexes the data without generating IDs.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • matchPurpose

      RuleBasedProperties.Builder matchPurpose(MatchPurpose matchPurpose)

      An indicator of whether to generate IDs and index the data or not.

      If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

      If you choose INDEXING, the process indexes the data without generating IDs.

      Parameters:
      matchPurpose - An indicator of whether to generate IDs and index the data or not.

      If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

      If you choose INDEXING, the process indexes the data without generating IDs.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also: