@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class IdMappingRuleBasedProperties extends Object implements Serializable, Cloneable, StructuredPojo
An object that defines the list of matching rules to run in an ID mapping workflow.
| Constructor and Description |
|---|
IdMappingRuleBasedProperties() |
| Modifier and Type | Method and Description |
|---|---|
IdMappingRuleBasedProperties |
clone() |
boolean |
equals(Object obj) |
String |
getAttributeMatchingModel()
The comparison type.
|
String |
getRecordMatchingModel()
The type of matching record that is allowed to be used in an ID mapping workflow.
|
String |
getRuleDefinitionType()
The set of rules you can use in an ID mapping workflow.
|
List<Rule> |
getRules()
The rules that can be used for ID mapping.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller. |
void |
setAttributeMatchingModel(String attributeMatchingModel)
The comparison type.
|
void |
setRecordMatchingModel(String recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
void |
setRuleDefinitionType(String ruleDefinitionType)
The set of rules you can use in an ID mapping workflow.
|
void |
setRules(Collection<Rule> rules)
The rules that can be used for ID mapping.
|
String |
toString()
Returns a string representation of this object.
|
IdMappingRuleBasedProperties |
withAttributeMatchingModel(AttributeMatchingModel attributeMatchingModel)
The comparison type.
|
IdMappingRuleBasedProperties |
withAttributeMatchingModel(String attributeMatchingModel)
The comparison type.
|
IdMappingRuleBasedProperties |
withRecordMatchingModel(RecordMatchingModel recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
IdMappingRuleBasedProperties |
withRecordMatchingModel(String recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
IdMappingRuleBasedProperties |
withRuleDefinitionType(IdMappingWorkflowRuleDefinitionType ruleDefinitionType)
The set of rules you can use in an ID mapping workflow.
|
IdMappingRuleBasedProperties |
withRuleDefinitionType(String ruleDefinitionType)
The set of rules you can use in an ID mapping workflow.
|
IdMappingRuleBasedProperties |
withRules(Collection<Rule> rules)
The rules that can be used for ID mapping.
|
IdMappingRuleBasedProperties |
withRules(Rule... rules)
The rules that can be used for ID mapping.
|
public void setAttributeMatchingModel(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 matches the value of the
BusinessEmail field of Profile B, 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.
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 matches the value
of the BusinessEmail field of Profile B, 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.
AttributeMatchingModelpublic String getAttributeMatchingModel()
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 matches the value of the
BusinessEmail field of Profile B, 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.
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 matches the value
of the BusinessEmail field of Profile B, 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.
AttributeMatchingModelpublic IdMappingRuleBasedProperties withAttributeMatchingModel(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 matches the value of the
BusinessEmail field of Profile B, 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.
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 matches the value
of the BusinessEmail field of Profile B, 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.
AttributeMatchingModelpublic IdMappingRuleBasedProperties withAttributeMatchingModel(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 matches the value of the
BusinessEmail field of Profile B, 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.
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 matches the value
of the BusinessEmail field of Profile B, 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.
AttributeMatchingModelpublic void setRecordMatchingModel(String recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched to the
same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be matched to
one record in the target.
recordMatchingModel - The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched
to the same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be
matched to one record in the target.
RecordMatchingModelpublic String getRecordMatchingModel()
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched to the
same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be matched to
one record in the target.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be
matched to the same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be
matched to one record in the target.
RecordMatchingModelpublic IdMappingRuleBasedProperties withRecordMatchingModel(String recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched to the
same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be matched to
one record in the target.
recordMatchingModel - The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched
to the same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be
matched to one record in the target.
RecordMatchingModelpublic IdMappingRuleBasedProperties withRecordMatchingModel(RecordMatchingModel recordMatchingModel)
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched to the
same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be matched to
one record in the target.
recordMatchingModel - The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source can be matched
to the same record in the target.
If the value is set to MANY_SOURCE_TO_ONE_TARGET, multiple records in the source can be
matched to one record in the target.
RecordMatchingModelpublic void setRuleDefinitionType(String ruleDefinitionType)
The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target to define the match rules must be compatible.
ruleDefinitionType - The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target
to define the match rules must be compatible.IdMappingWorkflowRuleDefinitionTypepublic String getRuleDefinitionType()
The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target to define the match rules must be compatible.
IdMappingWorkflowRuleDefinitionTypepublic IdMappingRuleBasedProperties withRuleDefinitionType(String ruleDefinitionType)
The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target to define the match rules must be compatible.
ruleDefinitionType - The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target
to define the match rules must be compatible.IdMappingWorkflowRuleDefinitionTypepublic IdMappingRuleBasedProperties withRuleDefinitionType(IdMappingWorkflowRuleDefinitionType ruleDefinitionType)
The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target to define the match rules must be compatible.
ruleDefinitionType - The set of rules you can use in an ID mapping workflow. The limitations specified for the source or target
to define the match rules must be compatible.IdMappingWorkflowRuleDefinitionTypepublic List<Rule> getRules()
The rules that can be used for ID mapping.
public void setRules(Collection<Rule> rules)
The rules that can be used for ID mapping.
rules - The rules that can be used for ID mapping.public IdMappingRuleBasedProperties withRules(Rule... rules)
The rules that can be used for ID mapping.
NOTE: This method appends the values to the existing list (if any). Use
setRules(java.util.Collection) or withRules(java.util.Collection) if you want to override the
existing values.
rules - The rules that can be used for ID mapping.public IdMappingRuleBasedProperties withRules(Collection<Rule> rules)
The rules that can be used for ID mapping.
rules - The rules that can be used for ID mapping.public String toString()
toString in class ObjectObject.toString()public IdMappingRuleBasedProperties clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojoProtocolMarshaller.marshall in interface StructuredPojoprotocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.