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 Planned for future release
Created by Guest
Created on Oct 29, 2024

Add form support to conditionally display fields with specific content based on prior field content

During multi selection of records , when a user selects a record with a certain set of data items, the remaining records which cannot be grouped together with the initial selection should be disabled for selection.

An example:

  • Skill tool gets a list of requisitions

  • End user selects a requisition that contains a region

  • Only reqs with that region should appear


The current option is to implement the flow as separate steps, but it doesn't provide the desired UX:

  1. get requisitions

  2. get regions for a selected requisition

  3. get applications for a req - region combination and set this up to repeat for each region selected in the previous step


Idea priority High