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.
API for Group management
There is currently no API to create or manage Groups. There should be capability to: Create Group Edit Group (Name, Description) Assign/Unassign Attribute Values
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, PEM...
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 p...
Increase length of Activity Roll Out Name
Allow more characters in the name of activity roll outs. Increase the limit to 300 characters.
REST API hostname 50 chars restriction
IBM Partner Engagement Manager does not accept hostname for REST APIs more than 50 chars but there are REST API hostnames more than 50 chars even in IBM Cloud (bluemix) CloudantDB REST API with guid-id.bluemix.cloudant.com and hostnames can be up ...
Rejected partners can never be Accepted
Once a partner or user has been rejected they can never then be accepted using the same e-mail address. The product assumes that if someone is rejected they will forever be rejected. Also can not edit profile.
Enable UI dialog table rows to be expanded dynamic for data entry
For tables used for collecting input, provide a setting that would allow a new row to be added after the last row has been used.
Provide the ability to create custom sponsor user types
Provide a way for a sponsor admin to define custom sponsor user types, beyond the current sponsor admin, LOB and standard users. For the various permissions, there should be a way to indicate what that role can do with each one (nothing, read only...
Track Internal Users on PEM When PEM Registration Invite Sent to partner
Currently many users (MFT BA's & Engineers) are utilizing PEM, the number of users utilizing PEM may increase in the future. So there is a need to define a process or mechanism within PEM to track which internal EFX user is sending out new reg...
About email notifications and body
Issue 1: For Example there is a partner called ABCBank and we have three child accounts(ABCBank-1, ABCBank-2, ABCBank3) in Sterling Integrator as well as PEM. And we have to rollout a activity for ABCBank and we would like to reset a password for ...
Do not place IBM confidential, company confidential, or personal information into any field.