Erin, and anyone else who wondered how this works under the covers....
You'll see this in the training video mentioned. For the simple goal of entity consolidation*, the short explanation is that each candidate pair of entities (determined through tokenization) is evaluated by all of your
match rules and they collectively send a
set of directives to the decisioning engine. The engine then performs a single, resulting action (1, 2, or 3 below) on the candidate pair:
1. Merge the pair
2. Queue the pair for review
3. Do nothing
More Detailed Explanation:All rules in your config will evaluate the candidate-pair in parallel and
there is no sequence. Your match config can use any combination of the four rule types shown in the video. Each rule in your config is tasked with delivering a binary directive of True or False to the decisioning engine as regards asking it to perform a 'queue for review' on the pair or a 'merge' on the pair. Let's focus on the suspect and auto rules since those are by far the most widely used across all Reltio tenants.
- Each 'suspect' rule evaluates to False (aka "Do nothing") or to True (aka "Queue the pair for review")
- Each 'auto' rule evaluates to False (aka "Do nothing") or to True (aka "Merge the pair")
The decisioning engine waits until all rules have delivered their directives for the pair. It then, as
@Gino Fortunato mentioned, uses simple logic to determine what it will ultimately do with the pair. If one or more 'auto' rules evaluated to True, the engine will merge the pair; Else, if one or more 'suspect' rules evaluated to True, it will queue the pair for review; Else it will do nothing with the pair.
Even if you include relevance-based matching or invent a custom match rule which provide you additional flexibility, they operate within the same framework and deliver binary directives to the decisioning engine, no different than what is described above and can be included in your config along with the traditional rules.
There is one add'l point related to the engine's logic. If your match config includes a 'Negative Match Rule' and that rule evaluates to True, then the engine demotes all merge directives it has received from the 'auto' rules and treats them as "queue for review" thus preventing any possibility of a merge from your rules. This is explained thoroughly with a good example here,
https://docs.reltio.com/matchmerge/negativerule.htmlHope this helps.
*For now let's ignore the adjacent capability of asking the engine to create entity-to-entity relationships which is a different matter.