The negative rule has the same architecture as a rule but has the special behavior that if it evaluates to true, it will demote any directive of merge coming from another match group to queue for review. To be sure, most match groups across most configurations use a rule for most matching goals. But in some situations, it can be advantageous to additionally dedicate one or more match groups to supporting a negative rule to stop a merge based on usually a single condition. And when the condition is met, the negative rule prevents any other rule from merging the records. So in practice, you might have seven match groups each of which use a rule, while the eighth group uses a negative rule.
Note: A match group can have a rule or a negative rule. It cannot have bothYou can find more information on this hereThanks,
Senior Solutions Engineer
w www.reltio.com | b blog.reltio.com
Let's assume we make the configuration change so the records are reevaluated with data changes, which is probably what we would want in most cases. Is there a way out of the loop for entity A and entity B (without merging the records)? It sounds to me that the default behavior applies to all potential matches, meaning that if you say the two aren't a match, they won't be compared again.
Assemble Park City1389 Center Road, Unit 200Park City, Utah 84098USA
+1 (855) 360-DATA+1 (855) 360-3282
© 2022 Reltio. All Rights Reserved
Site by eConverse Media