In Architect, a flow assumes secure functionality when processing a secure action or when a variable’s content is marked as secure. When it consumes secure data, a key icon appears.
Within a task, the key icon indicates that an action or an action beneath it is either secure or consumes secure data.
Note: Secure flows impact agent analytic metrics, including time in IVR, average time in IVR, agent handle time, average agent handle time, and agent talk time. For more information, see Metric definitions.
To help familiarize yourself with secure flows in Architect, see Secure call flows overview and Secure flow scenarios. For more information on configuring and designing secure flows, review the following sections:
See the list of Architect built-in variables for all flow types. The built-in variable for secure flows is Flow.InvocationData. In a secure flow, the Update Data action updates the variable to the value of Flow.InvocationData supplied to the secure flow.
Find more information on flows, including configuring default settings; managing flows; dependency searches; flow design resources; and tips, best practices, and troubleshooting.
Architect permissions are based on flow design tasks, or job functions. An administrator from the Genesys Cloud organization must assign the appropriate permissions to an Architect user.
