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.
Looping Functionality for Dialogs (UI, API, XSLT)
Many times it is not possible to know the number of times that you need an API to execute. Looping would allow the execution of an API or UI dialog to be dynamic. This could be utilized in a great number of use cases, one of which I outlined below.
Validation failure message box
Currently it is possible to add validation to dialogs in tasks. When a partner does not complete/answer accurately there is no way to specifically tell them what to fix. There is a red X next to the field which is in violation, but not what they a...
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...
Support a context specific CSS file to control the look and feel of UI dialog components
Add the ability for there to be a PEM context specific CSS file which could be updated by Sponsor Admins and would control the look and feel of UI dialog components within activities. This would require that the dialog components support the abil...
Add a snap-to-grid mode that can be turned on and off to make objects easier to align.
Copy/Paste Entire Objects/Dialogs/Tasks (keeping mappings, etc. exactly the same)
Need to be able to copy and paste within PEM.
Feature of Looping to be incorporated on Tasks/Dialogs/API calls etc
Feature of Looping needs to be added on Tasks/Dialogs/API calls etc. Instead of stretching the current flows statically, it is always advisable to have dynamic looping feature, which would make the flows scalable. It not only makes the flow scalab...
Notify Sponsor an error has occured for a Partner's activity
When a partner is completing an activity an error can occur. In order for the partner to continue the activity the sponsor must investigate the error, resolve, and notify the partner to continue the activity. Currently, there is no way for the Spo...
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/...
Do not place IBM confidential, company confidential, or personal information into any field.