Reltio Connect

Hi Everyone,

I have a question on match rules related to handling attributes with null conditions.

Scenario:

For one attribute in the rule say suffix, the requirement is that it should allow:

• match If values are equal
• match if one side is empty
• match if both sides are empty

To cover this, We ended up creating two separate match rules:

1. One using ExactOrNull
2. Another using ExactOrAllNull

My question: Is there a way to design a single rule that combines both conditions (EON+EOAN) for that attribute, instead of maintaining two separate rules?

Has anyone implemented this pattern in a single JSON condition, or is the standard approach keep them as two rules?

Thanks in advance for any suggestions!

------------------------------
Rushyendar Akula
Concord NC
------------------------------

Hi Rushyendar Akula,

Yes, you can combine ExactOrNull and ExactOrAllNull into a single match rule using the or operator.

I have created a rule for the Individual entity that does the following:

• Matches exactly on the Name attribute

• Matches on Suffix using:

  • ExactOrNull – allows match if values are the same or one side is empty

  • ExactOrAllNull – allows match if values are the same or both sides are empty

We used an and block to require both conditions, and inside that, an or block to combine the two suffix rules.

This avoids the need for two separate rules and makes the logic easier to manage in one place.

It's set as a suspect match rule, with scope = ALL, and only uses operational values (useOvOnly = true).

{
  "uri": "configuration/entityTypes/Individual/matchGroups/NameAndSuffixMatch",
  "label": "Exact(Name) AND (EON or EOAN on Suffix)",
  "type": "suspect",
  "scope": "ALL",
  "useOvOnly": true,
  "rule": {
    "and": {
      "exact": [
        "configuration/entityTypes/Individual/attributes/Name"
      ],
      "or": {
        "exactOrNull": [
          "configuration/entityTypes/Individual/attributes/Suffix"
        ],
        "exactOrAllNull": [
          "configuration/entityTypes/Individual/attributes/Suffix"
        ]
      }
    },
    "matchTokenClasses": {
      "mapping": [
        {
          "attribute": "configuration/entityTypes/Individual/attributes/Name",
          "class": "com.reltio.match.token.ExactMatchToken"
        },
        {
          "attribute": "configuration/entityTypes/Individual/attributes/Suffix",
          "class": "com.reltio.match.token.ExactMatchToken"
        }
      ]
    },
    "comparatorClasses": {
      "mapping": [
        {
          "attribute": "configuration/entityTypes/Individual/attributes/Name",
          "class": "com.reltio.match.comparator.BasicStringComparator"
        },
        {
          "attribute": "configuration/entityTypes/Individual/attributes/Suffix",
          "class": "com.reltio.match.comparator.BasicStringComparator"
        }
      ]
    }
  },
  "scoreStandalone": 0,
  "scoreIncremental": 0
}

Here is an example for the same:


------------------------------
Vibha Mahesh
Technical Consultant
Reltio

Original Message:
Sent: 09-11-2025 22:39
From: Rushyendar Akula
Subject: Best practice for attributes with both EON and EOAN requirement.

Hi Everyone,

I have a question on match rules related to handling attributes with null conditions.

Scenario:

For one attribute in the rule say suffix, the requirement is that it should allow:

• match If values are equal
• match if one side is empty
• match if both sides are empty

To cover this, We ended up creating two separate match rules:

1. One using ExactOrNull
2. Another using ExactOrAllNull

My question: Is there a way to design a single rule that combines both conditions (EON+EOAN) for that attribute, instead of maintaining two separate rules?

Has anyone implemented this pattern in a single JSON condition, or is the standard approach keep them as two rules?

Thanks in advance for any suggestions!

------------------------------
Rushyendar Akula
Concord NC
------------------------------