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.
It would be great if the user could see a count against every grid in a tab group so they can easily identify which ones have data. This would prevent them from wasting time clicking on each grid one by one.
Disable auto scroller functionality to top of the page on toggling between tabs
On clicking on information such as related objects, eg: risks in risk registers, and then navigate back to the Risk Register tab, the screen always returns to the top of the page instead of returning you to the section that you were previously in....
Workflow bulk termination and restart enhancements
In developing GRC workflows, it's apparent that if we publish a workflow version and users begin to use it, and then we publish a newer version of the workflow later on, the users are expecting to see the newer version reflected in their existing ...
Often times when copying objects there are fields that have to be reset. One example would be updating the status field after copying an object. Another use case would be to update fields after copying templates from the library.
Fields are often created in error or are no longer in use but they can never be deleted from OpenPages. This causes a lot of confusion in the administation screens. Admins should be able to at least hide these fields from their views
Association access control by security rule on the child object
Association access control by security rule on the child object, for now, in OpenPages, it only works with parent object, it would be nice that we can restrain association access on the child object as well.
Currently the dashboard has drastically increased the requirements for more filters. These filters clutter the user's Gridviews with dozens of filters. It would be nice to be able to categorize filters as 'For Grid View' and 'For Admin/Dashboards'.
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.
Do not place IBM confidential, company confidential, or personal information into any field.