Brian,
So there is no OOTB way to restrict the publish of an object just because it has a suspect match. We follow the paradigm that we want to alert downstream systems to updates of records regardless of the ability to resolve the manual match. Often times customers or partners will have limited resources to review all manual matches, or they may do it at the end of every month. When two entities are listed as a potential match, they are treated as 2 distinct entities for all Reltio processing. It isn't until the match is approved that we have any real processing connection.
If you would like to do this though, there is a way, but in a general sense we would not recommend trying to do this as you will run into data synchronization issues where Reltio data is not the same as the data in your consuming systems. It can be accomplished however by utilizing the following:
We publish all events to our event queue, but most customers and partners read this SQS queue and republish messages to various other topics / queues / Kafka streams for their consumers. They do this because some consuming systems may only care about a specific entity type, or a certain geography for customer data. They do this by having a middleware process that reads the OOTB SQS queue and then can republish it to the end state queues for systems to consume. You could read the main events on the OOTB queue and look to see if any potential matches exist for the entity, and if any do exist, simply not rebroadcast the message to the final queues. You can look up potential matches programmatically via our potential matches API.
https://docs.reltio.com/matchesapi/matchesapi.html?hl=potential,matches,api
You can also filter based on certain attribute values within the object, but I do not believe this would really solve your request. You can see the documentation around filtering based on objects (entity, attribute, create time, etc) about halfway down on this page.
https://docs.reltio.com/events/eventsapi.html
------------------------------
Mike Frasca
------------------------------
Original Message:
Sent: 04-27-2021 16:36
From: Brian Beil
Subject: Reltio Publishing Criteria and Suspect Status
Mike,
Thank you for the insights. I was aware how to search for the records in the suspect queue via the UI but more concerned about how to prevent records in the suspect queue from being published. With that said, if I can search for suspects via the UI, Reltio must store the status of the record somewhere, and that it what I am looking for.
While I did read the documentation you sent I am having trouble finding specifically how I would restrict records from being published that are in the suspect queue. Can you tell me specifically how to identify records in the suspect queue? What is the attribute and where is it stored?
And if you could specifically mention what logic is needed to prevent records from being published utilizing that "status" attribute I would really appreciate it.
Thanks again,
Brian Beil
------------------------------
Brian Beil
Senior Manager, Provider MDM Operations
Evernorth
Original Message:
Sent: 04-27-2021 14:19
From: Mike Frasca
Subject: Reltio Publishing Criteria and Suspect Status
Brian,
I believe you are talking about the potential match queue. If you have an entity selected and look on the left side of the screen, You can select the highlighted icon to view all potential matches for that entity. You can also resolve the potential matches there.
You can also identify all objects that have a potential match via our search screen! On the search screen select the entity type you are interested in, and then under attributes option you can add the Potential Match facet that searches based on the number of potential matches, or you can add the Match Rule facet and select the rule.
These can be combined with other search criteria to drill down to the exact entity that you are interested in.
I am not quite sure if I understand the last question, but I think you are talking about the SQS queue. You can filter what events are published to the SQS queue. Here is a link to our documentation which highlights all of the event types that you can filter or publish.
https://docs.reltio.com/events/eventsapi.html?hl=sqs,filter
You can also manage your external queues via our Reltio Console.
https://docs.reltio.com/tenantmanagement/manageexternalqueue.html?hl=sqs is a link that shows how to configure as well as enable / disable publishing to that queue.
------------------------------
Mike Frasca
Original Message:
Sent: 04-27-2021 12:44
From: Brian Beil
Subject: Reltio Publishing Criteria and Suspect Status
Does anyone know how to determine if a record is in the suspect queue or not in Reltio? What attributes is the status stored in?
Also, does anyone know how to restrict records that are in the suspect queue from being published?
Thanks in advance!
------------------------------
Brian Beil
Evernorth
------------------------------