Matching Workflow Rule Based Properties
Constructors
Properties
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.
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.
A list of Rule objects, each of which have fields RuleName and MatchingKeys .