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.
I will add a comment here as it aligns most with a question we received during a bootcamp from Liberty Mutual's HR team as part of a pre-sales engagement. They wanted to know if Orchestrate automatically scrubs out any PII or HAP data from its logs/agent responses. They were mostly interested in how Orchestrate handles sensitive HR queries and/or personal information a user might share. We saw that these filters are configurable in watsonx.ai as guardrail filters, but is still a work in progress for Orchestrate.
We recently introduced events & instance methods support for embedded chat.
This might enable the UI Builder persona to come in and handle PII for her instance of embedded chat & help while we look into what you are asking exactly.
Regarding PII Detection (now focus of the present idea) this does not apply just to flows but any chat interactions I assume.
Regarding requirements, we created a few from the original idea :
Form Capabilities and Integration with GenAI: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1282
Pre-populate Fields: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1283
Field Validation & Invalid Information Handling: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1284
AI Classification Transparency: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1285
Keeping the present record for PII Detection:
Thank you very much for your input, we appreciate your work and support!
I just want to make sure we act on all your point so let make sure that
all unexpected behavior(per doc) / likely defect gets reported to tech support to isolation / resolution (no need to report them here as well)
all improvements of existing features or as new feature are recorded in dedicated ideas so we can track / scope / prioritize those accordingly
We hope this makes sense, so we can act on each item appropriately, thank you again!