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.
Simultaneously modifying and deleting governance artifacts and asset
On IGC (11.x) -WKC (4.x) migration projects.
Clients developed lots of query that they use to search (with many filters) governance artifacts and asset.
They also use this feature to bulk modify and delete the searched data.
The search phase could...
IBM DataStage 11.7 support PostgreSQL 13.x under Red Hat Enterprise Linux 7.x
The "official document or information for IBM DataStage 11.7 support PostgreSQL 13.x under Red Hat Enterprise Linux 7.x" could not get now. Same situaation as PostgreSQL 14.x. Would there be the road map for supporting the Postgre SQL?
DataStage Kafka Connector should support schema compatibility set to FULL
Kafka Connector job failed with schema compatibility mode set to FULL. We got error "Schema being registered is incompatible with an earlier schema; error code: 409". Currently user has to change the Kafka schema compatibility mode to NONE from Po...
188.8.131.52.3 Information Analyzer ODFEngine queue issue on multiple datastage conductor nodes
RBC users are running more than 3000 Information Analyzer rules per day and the count will increase going forward. To manage IA rules load on Engine, we have installed two datastage Engines. What I have observed is, even we have multiple datastage...
The SAP OData Connector works only with S/4 HANA systems. We have to integrate some OData Custom Services from SAP C4C (SAP Cloud for Customer). Do to this we have to call the OData Service with curl/wget and free the result from the OData header ...
TLS/SSL connection between metadata repository and service tier
As per recent communication with IBM via case TS007746794, TLS/SSL connection not possible between metadata repository and service tier. Hence we would like to know when this feature will come into picture. We need this to be available as early as...
The current Kafka Connector (184.108.40.206 SP1) does not allow us to configure Avro Schema name used for either serialization or deserialization. In all cases, it is currently fixed to "KafkaConnectorSchema" which does not comply with our current schem...
Do not place IBM confidential, company confidential, or personal information into any field.