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.
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...
Allow Workflow to Continue After API has Failed
When creating an API dialog there should be an option to continue workflow even when the API fails. Preferably, it would have conditions to continue based upon what error is received.
Email notification when API task is failed in Activity
Whenever activity failed due to any reason an email should get triggered. So that current search manual work will be reduced and also this functionality will increase the sponsor user experience.
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...
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 ...
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...
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.
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...
Do not place IBM confidential, company confidential, or personal information into any field.