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 Future consideration
Workspace OpenPages Ideas
Components End User UI
Created by Guest
Created on Apr 14, 2020

Include/exclude fields from bulk update in TFUI & do not force update of controller fields

  1. Please allow for configuration of which fields within an object can be bulk updated. This way, bulk update can honor the fields that are editable in a task view.

  2. Please do not force update/selection of controller fields. I understand why you would be forced to update dependent fields if you are bulk updating controller fields, but it does not make sense that when bulk updating a dependent field, you need to update a controller field. For example, on risks, our users need to select an Action, "Accept", "Mitigate", "Transfer" or "Avoid". The actions they have available are dependent on the Risk Ranking on the risk. For example, Accept is not available if the Risk Ranking is High. It makes sense that if you bulk updated the Risk Ranking, you would need to clear out or bulk update the Actions, since they might not be valid for the updated controller Risk Ranking field. However, if you are bulk updating the Action to mark risks as "Mitigate", you should not need to update the Controller Risk Ranking field (which, like many Controller fields, is a read only field in the Risk Task View and users should not be able to update via bulk update, per point 1.)

  • Admin
    JOHN Lundgren
    Aug 13, 2020

    Thank you again for submitting this Idea!

    This request will not be delivered within the release currently under development, but the theme is aligned with our multi-year strategy. IBM is soliciting RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • Guest
    May 7, 2020

    I think this is partially a bug. If you are trying to clear a field using bulk update, but it has a blank controller field, this is impossible. If you select "clear" on the controller field, then you lose the ability to make any updates to the dependent field.

  • Admin
    JOHN Lundgren
    Apr 21, 2020

    Thank you for submitting this Idea!

    The IBM team is evaluating this enhancement request. A decision or request for more information will be provided within 90 days.