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 Not under consideration
Created by Guest
Created on Aug 10, 2023

Input from previous skill should be readonly in the next skill

In the current version, the inputs sent by the previous skill can be modified in the next skill. For example, my "skill-1" is doing a validation and the validations results are sent to "skill-2" (Send Email skill) as the email body. However, at the time of execution, the email body can be updated and sent.


This will give an option for the person who is executing to alter the email text. (A rejection message can be modified as "Approved"



  • Admin
    SABTAIN KHAN
    Jul 24, 2025

    The strategy has shifted to Agents and Tools - builders will have more control over this in the tool flow builder

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Mar 21, 2024

    Our workflow capability is eventually to become the one way to sequence skills of all kinds, the ability to make fields read-only is already available there.

    It does not support the skill flow pattern yet but you can vote / comment on idea LSABER-I-280 which we are planning on. Any other ideas to facilitate your needs in workflow are welcome!

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Aug 10, 2023

    Thank you for the input, this is indeed an interesting feature to consider.