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 Feb 20, 2025

Update Control Mechanism for Large-Scale Environments

In large environments where multiple updates and implementations are occurring simultaneously, there is a need for an update control mechanism. For instance, consider an environment with several watsonx assistants, referred to as “sandboxes,” where each user develops their own content. Once the development is completed within the sandbox, the content is transferred to the main DEV assistant via the “Copy to Assistant” feature, which consolidates all the developed content.

This process becomes particularly complex to manage, especially when many developers are involved. A suggested improvement would be to introduce a mechanism that prevents overwriting content in the main assistant. Specifically, it would be helpful to implement a locking feature for content in the main assistant, preventing it from being overwritten by other users. Additionally, notifications could be triggered in case of attempted overwrites, especially if the content is locked.

This enhancement would streamline collaboration, improve content integrity, and reduce the risk of overwrite contents in the main DEV assistant.

Idea priority Urgent