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.
Registration link to close after registering
After registration the link is not closing. Instead it times out and confusing people since the page is still opened.
Support for token authentication
Some of REST APIs for IBM products have token authentication implemented. I.e., call a sign in API to get a token, and then use the token in a HTTP Header for all other API calls.
IBM Sterling Secure Proxy: https://www.ibm.com/su...
Validate API for Managed SSL Cert and Managed SSH Key
The out-of-box PEM Portal activities have options for Partners to upload SSL or SSH Keys. In case of a user error, a partner may upload an incorrect file. In such a scenario, the API to store SSL Cert or SSH Key to PR fails and there is no way to ...
Extra Cols in Table on UI Dialog
Table on UI Dialogs can have a max of 10 columns. Sometimes more than 10 columns are required to collect data from sponsors/partners. Please extend the number of max columns a table can have.
Upload UI component - improve user experience
The user experience of the Upload button in UI dialogs could be improved greatly.
Currently, not counting the browser's file-selection window, it takes 5 mouse clicks and typing in a name to upload a new file:
1) Click the Upload button in the U...
Parallel Executions of a Shared Activity
In the case where a maintenance activity (ex. user account password reset) is shared to a partner account, we need the ability for multiple partner admins or users on that acccount to execute the same shared activity simultaneously. Currently, PE...
Provide a read-only role for the Partner Repository
We'd like to be able to provide sponsor users who are not admins a way to have read-only access to the items in the Partner Repository, such as Code Lists, Generic Data, etc.
Provide a way for sponsor standard users to roll out an activity
We need to have our sponsor standard users to be able to roll out activities, while still being able to control their participation in a rolled out activity based upon the custom role they have been assigned to.
Perhaps there could be a way, simi...
Dynamic show/hide UI dialog elements
When trying to make a UI dialog more dynamic, we can currently use labels mapped to XSLT output to generate appropriate text for a partner.E.g. a screen which can show Test, Prod, or both Test and Prod server details in one dialog. Or Inbound, Out...
Add the ability to administer division partners and LOB users via the PEM Portal UI
Currently, Divisions can be created via the portal UI, however, the assigning/unassigning of partners to divisions and the assigning/unassigning of LOB users can currently only be done via API calls. It would be much easier if this could be done ...