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:
stick to one feature enhancement per idea
add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)
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.
Absolutely, your observation is spot on. When configuring Next Best Actions (NBA) during the build phase, the ability to specify mapping values for passing to the next skill is crucial. This becomes particularly powerful when dealing with scenarios such as the first skill, where the input is the manager ID, and it produces a list of employees with detailed information like employee ID, name, and salary...etc. In the subsequent skill, which requires manager ID, employee ID, and name, avoiding redundant user input by mapping data from the first skill significantly streamlines the user experience and minimizes manual inputs. This not only enhances efficiency but also ensures a seamless flow of relevant information between skills.
it's essential to note that while achieving this data mapping is possible within skill flows, there is a limitation to consider. Currently, skill flows follow a linear path, and incorporating multiple Next Best Actions (NBAs) or branching within the skill flow is not supported. This highlights the need to address scenarios where branching might be necessary for varied user interactions.
Thank you for the feedback, you refer to the ability to define data mapping at build-time for next best actions so the data flows at runtime, is that right? Can you provide an example?