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.
Implement compression of REST request and reply data
We're using the REST interface. But sometimes we get a lot of data back. E.g. when we retreive a contract with a high inquiry level. Sending this data can be speed up by using gzip (or an other format) as a lot of REST API's already do.
The MDM data model has you extend entities and the implementation of extensions is done via extending the Java classes. For instance if you extend the Person entity then your generated extension class extends "TCRMPersonBObj", however the Java ext...
on 11.4 workbench, we had a way to enable extension by overriding "extendableInline=true" as indicated bellow. In 11.6 workbench, we tried the same but were not able to get around the restriction.We are in upgrade process and this has become a sti...
Oracle Native Network Encryption in MDM 11.6 Advaced Edition
PMR: TS000948369MDM Version: MDM V11.6DB Version: Oracle 12 COracle Parameter: SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=SHA256 We are using Oracle Native Network EncryptionWhen we enable OAS at DB level with â€˜SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=â€˜ a...
DB2U ( DB2 Universal) containers on DB2 V11.5 went live late last year and currently MDM is not shipping with a production-ready version of DB2 containers and hence we need to evaluate if we can use and start providing Db2 11.5 containers as an en...
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.
Provide the ability for MDM Workbench to support extension attributes of type XML
Both DB2 and Oracle support the XML datatype. MDM Workbench does not support creating extension attributes of type XML. Supporting attributes of type XML provides more flexibility in extensions. Currently the only supported XML extensions are o...
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'...
Do not place IBM confidential, company confidential, or personal information into any field.