Thank you Rory,
Looks like once the variable is defined for input/output there's no way to revert it and it will not allow "secure" to be checked.
I created a new slot and I can see I can set it as secure.
------------------------------
Jason Neuman
The Capital Group Companies, Inc.
------------------------------
Original Message:
Sent: 10-02-2023 04:02
From: Rory Brennan
Subject: Secure Flows and Slot Filling - Sensitive data is exposed in Utterance history - Help?
Hey Jason,
You can set the Slot variable as secure (provided its not set as output or input aswell) like:
Hope that helps!
------------------------------
Rory Brennan
Genesys - Employees
Original Message:
Sent: 09-29-2023 14:37
From: Jason Neuman
Subject: Secure Flows and Slot Filling - Sensitive data is exposed in Utterance history - Help?
Hello,
I have an inbound flow I've created which transfers the call to a secure call flow. From the Secure Call Flow I do slot filling via a bot flow.
The slot I'm referencing contains sensitive data which I do not want exposed anywhere within Genesys cloud logs. Unfortunately this is being exposed in utterance history.
How are you preventing sensitive slot data from being exposed in the utterance history?
#ConversationalAI(Bots,AgentAssist,etc.)
#Security
------------------------------
Jason Neuman
The Capital Group Companies, Inc.
------------------------------