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.
-
Support for multiple endpoints for partners migrating from legacy MFT to SFG
When migrating partners from legacy MFT platforms to SFG, a campaign is required to inform partner about the change of systems, and any change they would have to do at their end. Partners being migrated will have a test environment and prod enviro...
-
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 ...
-
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...
-
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...
-
API for Group management
There is currently no API to create or manage Groups.There should be capability to:Create GroupEdit Group (Name, Description)Assign/Unassign Attribute Values
-
Add proxy authentication to the bulk upload utility
Without authentication, we cannot get out from behind our proxy. We use Forcepoint proxies. The script fails and we need to bypass auth or the proxy altogether to be able to get out. This causes a delay in our testing.
-
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, PE...
-
Failure Handling
It would be better if we can
-> had a failure handling option in PEM (like on fault in SI)
-> call another activity from one activity
Let us know, for more details
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
Delivered