Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps
Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
IBM Employees:
The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io
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!