Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

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,

  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 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Product Master
Created by Guest
Created on Mar 1, 2020

Run Value Rules and Validation Rules on Tab Out instead of after Saving

Since Value Rules and Validation Rules are only executed on saving, end users do not receive immediate feedback when there is a data issue which can be inefficient and confusing for someone trying to resolve the issue. The expected behaviour is that any errors or issues are flagged immediately on tab out of a field, rather than waiting for a user to click Save. This scenario also applies for fields which are populated based on the value in another field. eg. a description field which is populated based on a code field. If a user then changes the code, the description field does not change until it is saved which is potentially confusing to users.

If tab out changes were occurring, then end users would receive immediate feedback on any errors and would also always be working with the most up to date data rather than potentially stale data as they have not saved yet.

Allowing the option to do either 'tab out' or 'on save' validation would allow Workflows to be designed with much greater flexibility and to be tailored to end users.

Needed by Date Mar 31, 2020
  • Guest
    Mar 11, 2020

    Not in immediate roadmap