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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting 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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 offering manager 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 notifications 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.
oceans as inexhaustible source of hydrogen
Some years ago, I was the P.I. for a proposal to the EU with German, Spanish and Polish partners, for Autonomous Sailboats Moving Turbines to harvest hydrogen from sea water.
The key to the economics of this how much of the energy obtained from th...
introduction of query parameter or new function for exact match search
when we try to find a specific user credential using its name and the partner it belongs to , the API performas a like search and returning multiple matches. Looks like, for the profileConfigName query parameter, this API is deviating from the sta...
Ability to add custom HTTP headers for PEM application
Due to security concerns, security team likes to have custom HTTP headers in all HTTP traffic. Request you to please add a new feature is to be able to configure HTTP header for PEM application. This is required to get CA signed certificates from ...
comprehensive search facility in PR
We need a comprehensive search facility in PR compared to what is there now. There are many to search in the PEM DB via PR. We probably can use a series of API calls but that is cumbersome to use. So having more advanced search options in PR will ...
encryption of passwords in setup.cfg
There are multiple passwords mentioned in the file setup.cfg - database, truststore, test mode, etc. these passwords are expected to be encrypted as per customers security requirements. Currently these are in plaintext.
Role based access to unprovision of codelist facility
functionality where unprovision button is only available to first/primary sponsor admin.
podman support for PEM
RHEL 8 native provides podman instead of docker. While it's possible to install docker ce on RHEL, that puts the user into unsupported area with RHEL 8 support. Would like to have podman as a support container engine.
Increase concurrency in activity processing
We found out that PEM may have concurrency limit of 10 concurrent users/activity being handle in parallel. would like to have product increase that to handle higher volume implementations
change username validation
Currently in PEM while creating the users. PEM is allowing only email address as user id. As this is in IBM cloud and SaaS solution. Can you change the user id to accept any unique string ?
Sterling Integrator supports 16 characters for Connect Direct Node name and would need PEM as well to be supporting 16 characters.
when customers who are using SI wants to use PEM and they have nodes in SI with 16 characters but from PEM they are not able to. so it will help them to use pem if this is enabled in pem.
Do not place IBM confidential, company confidential, or personal information into any field.