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.
Upload UI component - improve user experience
The user experience of the Upload button in UI dialogs could be improved greatly.
Currently, not counting the browser's file-selection window, it takes 5 mouse clicks and typing in a name to upload a new file:
1) Click the Upload button in the U...
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...
track duplicate email ID, while sending out registration invite
When we invite an email id which is already registered in PEM, it throws no warning, but mentions as invite sent and that person can click the link and register, but while approving in PEM it throws as Email ID already exists.It would be better, ...
Mapping Array values to dynamic table as drop down
In the PEM Table UI, when we map it dynamically it doesn't allow drop downs. It would be better if we enable this feature.e.g If we give Y|N to a static tables drop down column, then it will give drop down with Y and N, but the same thing, if we d...
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.
Add ability to configure which button in an approval task is highlighted/defaulted
When using an approval task, it would be a nice feature to be able to configure whether the Approve button or the Reject button is the one highlighted/defaulted when the activity is executed. Currently it is always the Approve button. If not con...
Systems and System-related objects should be visible in the Portal UI.
There should be a way to view a system, its extensions, and profile references in the PEM Portal. This would provide users with easy access to this information as a reference when a campaign is not currently open for that system. It would also giv...
Support for Entry Validation Reordering
The order of entry validation determines how entries are evaluated, however entries cannot be moved up or down the list in the UI. In order to create successfully create entry validation criteria, the ability to either insert entries at any place ...
Add an Undo Button with Control+Z functionality
Undo (Ctrl+z) should undo the last few actions. The UI designer makes it especially easy to accidentally move an item and there is no way to move it back. Simple mistakes like this should be undo-able.
E-mail Template Variables Standardized
The numbers used to identify variables within e-mail templates should be consistent across all templates.
Do not place IBM confidential, company confidential, or personal information into any field.