IBM Watson™ Ideas

Welcome to the IBM Watson™ Ideas Portal

We welcome and appreciate your feedback on IBM Watson™ Products to help make them even better than they are today!

If you are looking for troubleshooting help or wondering how to use our products and services, please check the IBM Watson™ documentation. Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.

If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.

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

  • Mark W
  • Sep 17 2018
  • Will not implement
Why is it useful?
Who would benefit from this IDEA? Developers and even non-technical users could benefit.
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
    October 17, 2018 01:56

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

  • Mark W commented
    October 18, 2018 17:06

    Thank you for this tip, Jaysen!