Reltio Connect

Hello everyone,  we have an MDM usecase for one of our clients, where they would like to break the match & merge into a 3 step process.  Let me explain one of the simplest version of this usecase:

1) Do the match

2) Assess the impact of this match and then 

3) Decide whether the job should proceed with the Merge

For eg lets say this MDM match and merge job could impact the sales territory alignment.   Assume the job had a 1000 records.   The requirement is that a) we do the match,- let us say this leads to about 100 of the 1000 having a match

b) assess the impact of these 100 matches collectively on the territory alignment eg "job will lead to x% alignment changes" or "job will lead to $Y changes between territories", and then

c) decide if "x%" or "$Y" is acceptable and move forward with the merge of all the 100 matches or  allow a DS to review the list of matches and decide which of the merges for the 100 matches are ok and allow for a subset of the matches to merge or ofcourse completely stop the merge.

We have not implemented a solution like this in Reltio and wanted to see if the Reltio experts here have had to deal with this scenario and have any elegant solutions that we could consider.  Our objective is to minimize the amount of manual DS work to complete this ie implement some business rules that could assess the impact and if it meets the criteria go ahead with the merge.  We would like to implement such business rules/checks for the impact assessment both at the entire job level and at the individual match level if possible.

Thanks much in advance!

-Haranath

------------------------------
Haranath Gnana
Blumetra
------------------------------

Hi Haranath,

Intereseting use case!

I would recommend looking at Custom match rules to solve this. The custom rules allow you to send a specific event in the queue when the match happens. You can read those events using a message processor (possibly RIH or a lambda function) to evaluate the additional logic that you mentioned. This would work perfectly for individual matches.

Hello everyone,  we have an MDM usecase for one of our clients, where they would like to break the match & merge into a 3 step process.  Let me explain one of the simplest version of this usecase:

1) Do the match

2) Assess the impact of this match and then 

3) Decide whether the job should proceed with the Merge

For eg lets say this MDM match and merge job could impact the sales territory alignment.   Assume the job had a 1000 records.   The requirement is that a) we do the match,- let us say this leads to about 100 of the 1000 having a match

b) assess the impact of these 100 matches collectively on the territory alignment eg "job will lead to x% alignment changes" or "job will lead to $Y changes between territories", and then

c) decide if "x%" or "$Y" is acceptable and move forward with the merge of all the 100 matches or  allow a DS to review the list of matches and decide which of the merges for the 100 matches are ok and allow for a subset of the matches to merge or ofcourse completely stop the merge.

We have not implemented a solution like this in Reltio and wanted to see if the Reltio experts here have had to deal with this scenario and have any elegant solutions that we could consider.  Our objective is to minimize the amount of manual DS work to complete this ie implement some business rules that could assess the impact and if it meets the criteria go ahead with the merge.  We would like to implement such business rules/checks for the impact assessment both at the entire job level and at the individual match level if possible.

Thanks much in advance!

-Haranath

------------------------------
Haranath Gnana
Blumetra
------------------------------