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 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 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Allow for Export/Migration of TFUI Dashboard Configuration
Currently, all dashboard information comes with profile exports. For capturing OOTB enhancements, pre-made dashboards from partners, and partial profile migrations. Also, being able to migrate user created wigdets individually.
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.
Using the workflow instances view to terminate workflow instances is not user-friendly. suggest the following improvements: Allow for search/filter and sort by Object Name and Workflow Version. If a user selects objects using the checkboxes, then ...
We're finding grid views / embedded grid views have disproportionate column widths (in terms of reader usability/readability). This often impacts us on fields such as Name and Description. If we had the ability to define the column widths ourselve...
System Administrator option to prevent user login, disconnect existing users and display notification message.
When an administrator needs to perform some system maintenance operations we may need to keep users out of the system - but the system has to remain up. Eg. Large hierarchy change with data moves and security access changes. Or an upgrade where we...
Create ability to add "delete" and "Disassociate" buttons on embedded Gridviews
Currently in the new OpenPages UI you can create Add Object buttons and Associate Object buttons on the embedded Grid views. For example, you are in a Test Plan and want to add a Test Result object. You can add a button right on the grid view to a...
TFUI - Enable Workflow Validations and Operations on SAVE
Many of the data quality rules span objects - Eg. Impact booking date must be GT Event Occurrence Date. Form rules only allow for rules on a single object so cannot be used. Workflow rules for validations and operations only run on workflow transi...
Associate or a Copy an object using Workflow or Calculations Engine.
I have a scenario. In OP there is a Data type of Business Entity selector. Let's Suppose A process is a child of BusEnt. There is a process that is associated with a primary BusEnt. Now If the User wants to add a secondary BusEnt using the Busines...
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...
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
Do not place IBM confidential, company confidential, or personal information into any field.