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.
-
Single Sign On for PEM
Support Single Sign On for PEM to allow integration with identity management systems. This critical to comply with security requirements and verify user/partner identity. From a user experience, this is needed to provide a more seamless client/par...
-
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 v...
-
Provide housekeeping in PEM to clean up objects no longer needed
-
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.
-
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...
-
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.
-
Increase PEM Code list / Generic data field length
-
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.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
0
Planned for future release