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 Watson Assistant
Created by Guest
Created on Sep 17, 2018

Ability to Archive or De-activate a Node in Dialog

If I'm missing current functionality, please forgive me, but I find this ability very helpful in other systems I've used.  It would be  nice if there was an option for each dialog node (where current functions like "move", "duplicate", "delete" are located) to deactivate/archive it.  Maybe it would then show up in a separate "Inactive Nodes" section at the bottom.   Maybe it would be less work (and easier to turn back on) if it just changed color/faded/shrunk to show that it was inactive.

For instance, Zendesk uses triggers which fire sequentially, and the ability to deactivate/archive a trigger allows me to easily test a new trigger knowing that even if it does not work I a) can easily turn it off, b) won't lose my work, and c) can turn it on again easily.  It also makes it easier to develop triggers well ahead of when I need them (e.g. a holiday).

  • Guest
    Oct 17, 2018

    I've been de-activating nodes by adding "&& false" to the condition of the node.