Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on May 7, 2025

Ability to flag nodes in dialog

Why is it useful

  • Highlights nodes that need attention for content, testing or validation purposes
  • Prevents accidental release of unfinished content
  • Allows people working on separate content in the same skill to make it clear that they have unfinished business
  • Isolates errors in the dialog flow
  • Highlights content that is temporary (ie natural hazard response) that needs to be removed after a certain time period

Who would benefit

  • Any user who works in an environment where more than person may be making changes on the same skill
  • Any user who wants to flag something to return back to/for more investgation
  • Areas where time-specific content is common

How should it work

  • The flagging mechanism should work similarly to how flagging emails does.
  • When clicking the 3 dots in the top right of a node, an option is presented to 'flag' a node
  • This would highlight the node (make it a different colour, ie red or yellow), and tag it with a 'flagged' status.
  • Flagged nodes should be available through search - if you search 'flagged' they come up, or there can be a tick box to show flagged nodes so they can be easily accessed + reviewed.
  • When deploying, flagged nodes should come up on the publish screen, ideally in a different colour, to highlight the need for attention.
Idea priority High