Set Variable
Understand how to configure Set Global and Set Flow variables
Webex Contact Center supports use of global variables and custom flow variables (local variables) while building flows for the digital channels.
Authorization
Refer to section Node Authorizations for more information.
Methods and Outcomes
Here’s a brief description of various methods, and corresponding output variables and node outcomes associated with each of the methods.
Method Name - Set Global Variable
Global variables are defined in the Webex CC Admin Portal. Flow developers can fetch and use these variables within flows to set and pass values in the context of interactions handled in the contact center.
How to Fetch variables
To fetch variables:
- Select the Method Name.
- Select the required Node Runtime Authorization from the list.
- Enter the Task ID.
- Click Fetch Global Variables to fetch the variables.
All the fetched variables are pre-populated with values. - Select the required variables from the Fetch Global Variables pane.
- Enter the value for the selected variable which can be used within the node.
- Click Save.
Note
Maximum number of variables that can be added/updated are 30.
| Input Variables | Output Variables | Node Outcomes |
|---|---|---|
| TASK ID - $(flid) Flow transaction id from the start node is converted into UUID in the evaluate node, and passed to create task node, for creating task with flid as task id. | Task ID responsePayload | onInvalidData onError onInvalidChoice onTimeout onauthorizationfail Invalid Token Bad Request Not Found serviceUnavailable Task Updated * Task Failed |
All the global variable that are fetched with the default values can be modified and be used in the flow.
It is mandatory to use the latest version.
Method Name - Set Flow Variable
Flow variables are defined in the flow. Flow developers can create and use these variables within flows to set and pass values in the context of interactions handled in the contact center.
How to Add variables
To add variables:
- Select the Method Name.
- Select the required Node Runtime Authorization from the list.
- Enter the Task ID.
- Click Add Variable.
- Enter the data in the required fields in the Set Variables pane.
- Toggle the Make Agent Viewable to make all the variables can be viewable to the agent.
- Select the Agent Editable checkbox to allow the agent to make changes to the variables in the flow.
- Click Save.
Note
To Delete a set of variables, click Delete icon the right-side of the Set Variables pane.
Maximum number of variables that can be added/updated are 30.
| Input Variables | Output Variable | Node Outcomes |
|---|---|---|
| TASK ID - $(flid) Flow transaction id from the start node is converted into UUID in the evaluate node, and passed to create task node, for creating task with flid as task id. | Task ID responsePayload | onInvalidData onError onInvalidChoice onTimeout onauthorizationfail Invalid Token Bad Request Not Found serviceUnavailable Task Updated * Task Failed |
| Name - Name for the variable. Contains the alphanumeric value. Maximum length is 80 characters | ||
| Type - Type of the variable you want to associate with the flow String Boolean Integer Decimal * Date Time | ||
| Value - String - Contains the alphanumeric value. Maximum length is 256 characters Value - Boolean - Contains True or False value Value - Integer - Contains integer value Value - Decimal - Contains decimal value * Value - Date Time - Contains epoch timestamp in seconds | ||
| Description - Contains the details of the flow | ||
| Desktop Label - Contains the name for the label which is seen by the agent. Contains the alphanumeric value. Maximum length is 50 characters |
Note
Multi-language allowed for 'Description', 'Desktop Label' And 'Value' field (for Value field multi-language allowed in case when 'Type' field is String only)
Note that using Set Variable node a large number of times (typically more than 25) in the same flow canvas can at times cause loading issues leading to the inability to save your flow configurations. Please modularise your flow using the Call Workflow node in such cases.
Updated 3 months ago