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.
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...
Store more than 10 data fields
Often we have scenarios where SFG Solution uses external database tables. These tables can have any number of columns. When PEM activities are customized to collect data from sponsor/partner for the table and if the number of columns is more than ...
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.
Increased character limit of Context Data
Currently, Context Data can only contain 10,281 characters. Some requirements and design require more information to be stored in Context Data. Alternate Solution is to store and retrieve from GenericData Configuration, but it complicates the acti...
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 ...
Add a utility page where telnet, ping and traceroute can be run
When trying to troubleshoot connectivity issues with API endpoints to backend applications from a PEM cloud instance, it would be very helpful if there was a way that a sponsor admin could run a telnet, ping or traceroute command. This cannot cur...
Allowing to Administrator Sponsor Users to Edit the Same Activity
We would like to request that two Sponsor administrator users have the ability to edit the same activity. Currently unless you are the one who creates or "saves" the activity it is not possible to edit. This has proven difficult for version contr...
Feature to close bulk PEM Portal and Provisioner Activities
Currently, each activity or rollout has to be manually and separately closed. During development, Unit Testing, and UAT cycles lots of activities are created. There should be a way in PEM to bulk close Portal and Provisioner activities based on fi...
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.
Allow Workflow to Continue After API has Failed
When creating an API dialog there should be an option to continue workflow even when the API fails. Preferably, it would have conditions to continue based upon what error is received.
Do not place IBM confidential, company confidential, or personal information into any field.