Shape the future of IBM watsonx Orchestrate


This is the IBM Automation portal for IBM watsonx Orchestrate. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Add idea Subscribe
Status Under review
Created by Guest
Created on Apr 8, 2024

RELATED IDEAS

(WxOR6) Multi-tenant agents with user namespace isolation with deployment rings

Consider automation service providers delivering well known business processes to multiple clients, ex: “order to cash” (O2C). The service provider want to develop one standardised O2C digital agent, A, to deliver the O2C service to multiple enterprises, namely, E_1, E_2, …, E_k. When the digital agent A receives a request r from a client E_i, it needs to use the set of policy documents corresponding to the enterprise E_i and and take actions on invoices belonging to E_i. In other words, the agent acts like a multi-tenant agent with different namespaces corresponding to E_1, E_2, …, E_k. Further, each namespace E_i corresponds to the set of policy documents of E_i and the actual dataset (of invoices) of E_i.

The requirement is for Watson Orchestrate to support deployment of such multi-tenant agents with namespace separation of enterprises using the agent. This essentially means that each namespace corresponds to the data and the set of policy documents of corresponding enterprise. To serve a request, the data and RAG pipeline of the process would run on data and documents corresponding to the namespace of requesting enterprise.

The service providers would also want the agent to support deployment rings by which the clients can be on different versions of the agents based on their policy to switch to new versions.

Idea priority Urgent
  • Post comment
  • Guest
    Apr 8, 2024

    the benefit of this will be to foster rapid reuse of common skills across different business entities. easy to imagine how IBM_Customer_1 could have their policy documented ingested into their specific, secure namespace and execute the skill, and IBM_Customer_2 could invoke the skill against their different policy documents stored separately. a further advantage will be that when the skill is updated, all customer users of the skill will have the updated capabilities.

    Reply

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.