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.
Retrieve Provisioner Activity details using API
The "Activity Services" APIs at /activities/ and /activityinstances/ are hardcoded to only act upon Portal activities. Attempting to use them to retrieve instance details of Provisioner activities results in 404 errors.The API needs to be able to ...
Rollout API - Feature parity with UI
Currently the Rollout API can only do a rollout to a list of 10 partners.It needs to have the same capabilities as the web UI:- Rollout to a group- Rollout based on attributes- Rollout to as many partners as needed- Add partners to existing rollou...
API for Group management
There is currently no API to create or manage Groups.There should be capability to:Create GroupEdit Group (Name, Description)Assign/Unassign Attribute Values
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 flag to the get partners API to have the partners custom fields included in the results
For the get partners API (pemws/sponsors/<sponsorContext>/partners/) add an optional flag which indicates that the partners' custom fields should be included in the results. The custom fields are currently returned when retrieving a single ...
Do Not Assume GET Responses
Currently, when using a GET API, the 'sample response' must have all values nullified, or the 'sample response' is treated as a default answer, even if the API is skipped. The purpose of the sample response is to provide data structure only - not...
Update Get Partner API to Include UserId as Input
Since you are not allowed to add emails across two accounts, it would be good if you could check if an email is associated with any partner already. The Get Partner API does not allow you to search by userid as an input. Adding userid as a input w...
Straight up HTTP calls from PEM as opposed to only REST / XML API calls
Being able to do form posts or just any basic HTTP call will allow PEM to integrate with more systems.
API for "Invite Again" functionality
If partners are bulk uploaded but not sent an invite, the only way to send the invite is to manually click "Invite Again" in the UI. An API should exist for this.
Escape Special Characters in URL for Get Request
HTTP rest client's such as Postman typically allow for special characters in the Get request, PEM HTTP requests do not.