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.
When using a JMS provider you're able to send the notification as part of the XA transaction. For Kafka this is not possible (as per Kafka implementation).
Come with a solution so using Kafka for notifications is a usable option (currently not).
Kafka is supported by MDM, but you're not able to create and use you own Kafka resource. You now have to use one of the OOTB resources.
We want to be able to split the type of data to be send to different Kafka endpoints.
Japanese Address standardization (UCSFREQADDR) stops dividing the Japanese Kanji characters
To compare the address data written in Japanese with the AXP, we should select the UCSFREQADDR for the Address standardization function. When we derive the data including the Japanese addresses, the Kanji characters in the prov and the city weren'...
There is no doubt from the many GDPR conversations we've had with clients that there will be many different approaches to survivorship of consent, both in terms of different consents received for the same individual, and in terms of survivorship w...
Request for addition of Potential Overlay Task in MLDS over MDM SE 220.127.116.11
Our data stewards would like to resolve Potential Overlay tasks for real-time scenarios when one set of member attributes are duplicated by attributes of a different member within the same source system. This is most serious among data issue tasks...
for any user that does not belong to the "mdm admin" group. Even internal groups can see limited lists if they are not part of the "mdm admin" group. This "mdm admin" group is the one typically found in the mpi_grphead table with a grprecno 1.
At Ford we use MDM software to manage our customer base information. MDM talks to DB2 on ZOS to retrieve customer information. MDM uses DB2 triggers to maintain history data. For large UOW transactions triggers have been a performance bottle neck ...
Problem description and business impact : Using InfoSphere Master Data Management 11.6.0 on Redhat Linux, I observed in the SOAP WSDL interface, the Username and Password are passed in the SOAP Body instead of SOAP Header when doing a web service ...
Do not place IBM confidential, company confidential, or personal information into any field.