Hello,
We have activated the beta of being able to call dialog engine bots from secure flows, we have been doing tests and our TAM (@Carlos Landa) tells us that the information provided by the Genesys product team is that although the bot is invoked from a secure flow the conversation will continue to be saved in the Utterance History, but sensitive data will be encrypted, I have a question and a request about this behavior:

Question: Based on what logic is sensitive data encrypted?

Request: our most common use case in the use of dialog engine bots from secure flows is to ask the client for the password, that is, bots that are difficult to train, so the utterance history is not very useful to us, it would be possible to have a flag that would allow to disable the utterance history of a bot?

Regards.
#BetaUpdate

------------------------------
Javier Del Olmo
Banco Bilbao Vizcaya Argentaria, S.A.
------------------------------
​

In the Bot Flow, you need to mark your variables (such as Slot variables) as Secure by unticking input and output and then Content is secure.


Once done, you will have a list of variables that are secure:


When you run the flow, anything marked as secure is replaced with stars.


There is no complex logic, only the values you mark as secure.


------------------------------
Marc Sassoon
Genesys - Employees
------------------------------

Original Message:
Sent: 07-14-2022 05:04
From: Javier Del Olmo
Subject: Dialog Engine Bot Secure Flow BETA

Hello,
We have activated the beta of being able to call dialog engine bots from secure flows, we have been doing tests and our TAM (@Carlos Landa) tells us that the information provided by the Genesys product team is that although the bot is invoked from a secure flow the conversation will continue to be saved in the Utterance History, but sensitive data will be encrypted, I have a question and a request about this behavior:

Question: Based on what logic is sensitive data encrypted?

Request: our most common use case in the use of dialog engine bots from secure flows is to ask the client for the password, that is, bots that are difficult to train, so the utterance history is not very useful to us, it would be possible to have a flag that would allow to disable the utterance history of a bot?

Regards.
#BetaUpdate

------------------------------
Javier Del Olmo
Banco Bilbao Vizcaya Argentaria, S.A.
------------------------------
​

Thanks Marc, very clear.

------------------------------
Javier Del Olmo
Banco Bilbao Vizcaya Argentaria, S.A.
------------------------------

Original Message:
Sent: 07-15-2022 06:31
From: Marc Sassoon
Subject: Dialog Engine Bot Secure Flow BETA

In the Bot Flow, you need to mark your variables (such as Slot variables) as Secure by unticking input and output and then Content is secure.


Once done, you will have a list of variables that are secure:


When you run the flow, anything marked as secure is replaced with stars.


There is no complex logic, only the values you mark as secure.


------------------------------
Marc Sassoon
Genesys - Employees

Original Message:
Sent: 07-14-2022 05:04
From: Javier Del Olmo
Subject: Dialog Engine Bot Secure Flow BETA

Hello,
We have activated the beta of being able to call dialog engine bots from secure flows, we have been doing tests and our TAM (@Carlos Landa) tells us that the information provided by the Genesys product team is that although the bot is invoked from a secure flow the conversation will continue to be saved in the Utterance History, but sensitive data will be encrypted, I have a question and a request about this behavior:

Question: Based on what logic is sensitive data encrypted?

Request: our most common use case in the use of dialog engine bots from secure flows is to ask the client for the password, that is, bots that are difficult to train, so the utterance history is not very useful to us, it would be possible to have a flag that would allow to disable the utterance history of a bot?

Regards.
#BetaUpdate

------------------------------
Javier Del Olmo
Banco Bilbao Vizcaya Argentaria, S.A.
------------------------------
​