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
Post 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,
Post an idea
Upvote ideas that matter most to you
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 product management 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 notification 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.
The views usually evolve and the name becomes obsolete. It takes a lot of steps to copy them just in order to rename them. Admins end up not doing and the names get really confusing. Having functionality to rename them would be great.
Names of mandates,submandates, and reqs coming from TRRI feed should be more meaningful
Currently a sample mandate name would look like this: N2337B6702C3811E193E9A4A10117562ABy giving it a proper name finding the right mandate would become much easier, Also the context tree maps would become much more useful. This applies to subma...
OpenPages Workflows Should Not Notify Inactive/Disabled Users
Emails being sent to disabled users is a significant security concern for the OP system. Anyone labeled as disabled or inactive should not be sent emails if a group they belong to was selected for notification in a workflow.
While capturing a Risk Event, system error appears requesting end user to refresh the page (APAR PH30431)
The system error impacts end users who may lose data captured and be required to do rework. This creates resistance to use of the system. Although the help text does guide the user to navigate this defect - it is not optimal.
Allow for Multi-select option for BE Selector Field Type
This was requested two years ago, but accidentally marked as 'Delivered'.Right now all Object types where users want to Identify (for example) Impacted Locations, admins are forced to create fields 'Impacted Location', 'Secondary Impacted Location...
Ability to Purge Application Text Records from Deleted Views and Widgets
When you create a view or widget in the TFUI, each instance becomes an Application Text record. Once deleted, the Application Text record stays and becomes an orphan. As development continues, there should be a process (or script) to purge all orp...
Include user first and last name in user selector fields that are exported from UI
When users export from FLV to create fastmap templates, user selector fields are exported with user id only, and many times the user may be an employee id/non-descript identifier, so it would be great to have an export option where the user select...
Currently, change history does not include previous comments made in the "Action Comment" field (workflow comment popup). The popup cannot be used to serve as rejection or approval if the comment (which might provide conditional approval) is not t...
By whom and when are missing in Reports for Change Users, Role Template Changes, Change in Domain and Role Assignments.
There is no report showing user creation data. This should be part of the Azure interface (user add/modify/delete, access rights add/modify/delete)Furthermore, for user inactivity, login activity summary report shows a summary of the number of log...
Do not place IBM confidential, company confidential, or personal information into any field.