DCR - External Match Configuration

Overview

This section describes how to enable DCR External Match.

Process

To Enable External Match

  1. Create (or modify) a DCR Global Configuration to include External Match parameters.

  2. Insert (or update) a record in the DCR_STREAMING_CONFIGURATION table to have a new DCR Global Configuration.

  3. POST a new enrichment stream using POSTMan.

Update DCR Global Configuration table to include External Match Parameters

The DCR Global Configuration is contained in the DCR_STREAMING_CONFIGURATION table. It contains all the global parameters used for DCR processing in enrichment. Below is an example of a DCR Global Configuration containing only External Match attributes.

Copy

Sample DCR Global Configuration

{
  "createDcrSubmitExternalMatchEnable": true,
  "createDcrSubmitExternalMatchEntityTypeFilter": [
    "configuration/entityTypes/HCO",
    "configuration/entityTypes/HCP",
    "configuration/entityTypes/Location"
  ]
}

The following table explains the External Match attributes in the DCR Global Configuration.

Attribute

Description

createDcrSubmitExternalMatchEnable

true to enable externa match.  Default value is false

createDcrSubmitExternalMatchEntityTypeFilter

Array of Reltio Types valid for external match

Important:  If this attribute is not set, then no entity filter is applied for External Match.

Example:

Copy 
"createDcrSubmitExternalMatchEntityTypeFilter": [
      "configuration/entityTypes/HCO",
      "configuration/entityTypes/HCP",
      "configuration/entityTypes/Location"
    ]

POST new enrichment stream using POSTMan

To complete the deployment process, you have to create a new enrichment stream using POSTMan. Before POSTing the new stream, the DCRGlobalConfigName parameter in the POSTMan environment variables can need to be updated to contain the name of the DCR Enrichment Configuration in the DCR_STREAMING_CONFIGURATION table. The screenshot below shows an example of how the POSTMan environment parameter DCRGlobalConfigName links to the DCR Global Configuration in the DCR_STREAMING_CONFIGURATION table.  Note that the link is completed using the config_name attribute in the DCR_STREAMING_CONFIGURATION table. The corresponding config_json attribute can contain the actual DCR Global Configuration.

After the enrich stream inserts records qualified for external match, the monitor stream picks them from table ODP_CORE_STREAM.DCR_EXTERNAL_MATCH and checks against Reltio. The response is updated in the table and external info of the DCR. The data and match rules in reltio are expected to be re-indexed and rebuilt, respectively.

Records with the status 'PENDING' are picked by the monitor stream from the table and updated to MATCHED upon completion. Also, in externalInfo of DCR, isExternalMatchComplete is marked as true and PreRouteStatus as complete.

Above statements applies irrespective of external match is found or not.

On any failure while processing, the Error column of the table is populated with the status as 'ERROR' and retried 2 times by default.

Reltio API used to match:

{{tenantURL}}/entities/_scoredmatches?options=ovOnly-return&select=uri

Sample records in table  ODP_CORE_STREAM.DCR_EXTERNAL_MATCH. EXTERNAL_MATCH_ID 1 and 2 are processed with no match found where MATCHED_RESULT is empty array. 3 and 4 are processed with match found.

Sample external info of a DCR having suspect match:

{{tenantURL}}/changeRequests/4Rr6UPq8

Copy

Routing Config

{

    "Name": "HCO",

    "Vendor": "Reject",

    "RouteTo": "Reject",

    "AndCondition": [

      {

        "nodePath": "externalInfo.json.match.automaticByUri|*",

        "nodeValueField": "<count>",

         "matchRegularExp": true,

        "matchValue": [ "^[1-9][0-9]*$" ]

      }

    ]

  }