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.
Currently in a Grid View, the object instances are sorted by default by the Name field in an ascending order. In an embedded Grid, the default sorting can be configured to meet ones needs. This is not possible in a Grid View. Users have to apply t...
Add options END_USER_PROFILE / IN_PROFILE in workflow Applicability criteria.
Some workflows need to be started depending on the Profile of the user. Currently it is not possible to validate the profile of the user in the Applicability section of Workflows. The validation of Profile is a common feature in other functional...
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.
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.
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
Migration Failures: When migrating a datastore with a structural change between destination and source environments the migration tool does not throw an error, rather the migration fails with a generic message. The migration tool should throw a conflict or invalid message as it does with tables.
New UI - Criticality to allow for 'Not Defined' or 'Not Applicable'
On some objects it is meaningless to define criticality, or at least meaningless when only having fields on that object available for the rule
e.g. Action object may not have a RAG, because the RAG is defined on the parent issue
e.g. Test Pla...
Would like the ability to search on the Name field when on the Workflow Instances view. At times we need to terminate a workflow and there may be thousands of active workflows, so paging through the list attempting to find which object workflow t...
Objectmanager export dependencies similar to UI configuration export
When you export profiles or other artifacts from the UI (Administration/Export Configuration), the tool export all the required dependent objects automatically.Allow similar dependency export via Object Manager Few options.1) The UI already has th...
Do not place IBM confidential, company confidential, or personal information into any field.