Skip to Main Content
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.

Status Not under consideration
Created by Guest
Created on Mar 26, 2024

Parameter Store that can save values from skill responses and requests.

How does it work:

Some kind of string datastore, that is shared between all skills. Skills can optionally pull from this datastore every time they are run, and also save to this data store. These settings can be treated as input for skills in the same way requested data is fetched so that it can be used in the same way as well.

Why is this useful:

We need a way to save settings in Watson orchestrate. Something more permanent that the user's session in the chat or relying on chat history.

Who will this help:

In our case it will help systems that store configs in our app service that need to be handed off to Watson, that can be used in AI generated content.

Idea priority High
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Reply
    |
    Apr 1, 2024

    Thank you for the interesting idea that w/should be addressed by our workflow capability which will become the core way to orchestrate skills take a look at what we have today as we do have the ability to store data in variables during the duration of a flow execution but you might be looking for something more permanent/persistent.

    Can you provide a concrete example of the use-case so we can make sure understand the req?

  • Guest
    Reply
    |
    Mar 26, 2024

    But also support individual parameters as well.

  • Guest
    Reply
    |
    Mar 26, 2024

    It was not clear, but this should support tabulated data.