About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Hi Christen,
Sorry for not getting back to you earlier.
So the feedback I have received from our engineering team is that making a singleton entity of a member with PO, would create a lot of unnecessary traffic for event/entity management and would severely impact downstream systems.
We do recognize that these are very valid requirements, but our approach to handle these scenarios in the current MDM SE/AE architecture may not necessarily match to the solution you expressed here .. (Full quarantine of a record with a PO status by removing the record from all entities until the PO has been resolved.).
We are currently working full steam on our Next Gen MDM and we will design and implement a better solution for this in Next Gen matching.
Thanks
Christen - we had a bit of an issue tracking down the requirement. Now that we have it we will evaluate and respond directly if setting up a call is required.
Agreed... an overlayed record should become a singleton right away
This is a much needed change. Great idea!