Secure Variables
Store credentials in a fully encrypted manner.
The value is masked everywhere it appears in the user interface and logs.
The value is available to the Integration node only.
Name
Give the secure variable a name.
Value
|
Scenario |
Description |
|---|---|
| Creating the secure variable |
Enter the variable value and click Create. The value is encrypted and cannot be seen again. |
| Editing the secure variable |
The value is masked. You can replace it, but you cannot see it or partially edit it.
|
There is a character limit when setting the value on the screen Build > Content > Variables. The value should not exceed 150 characters. This limitation does not apply when setting the value while the task is running or assigning a value to a secure column in a datastore and reading the value back to the secure variable while the task is running.
Access to Secure Variables
Following are some general tips.
-
The Expression Builder has access to secure variables, dependent on the node it is opened from.
-
The Integration node is the only node that can be used to construct a URL with query parameters using secure variable values.
-
Studio accesses JSON formatted data through open form types and nodes like the Integration node. You can assign any JSON path result value to a secure variable except if the value is audio. You have no access to secure variables when using variables to create a JSON path.
Following are nodes and their level of access to secure variables.
|
Node |
Level of Access |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Prompt fields have no access to secure variables. You can store the enroll ID in a secure variable. |
|||||||||||||
|
Expression builder has no access to secure variables. |
|||||||||||||
|
Expression builder has no access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
Prompt fields have no access to secure variables. From the Speech Recognizer tab, you can assign the caller's transcribed responses and the confidence score associated with the transcribed text to secure variables. The entire message is then masked (**********) in the system log. |
|||||||||||||
|
No access to secure variables. If you assign a secure variable to any of the extracted words then the entire message is masked (**********) in the system log. |
|||||||||||||
|
Insert and update actions have access to secure variables. Secure variables can be used inside expressions and the expression builder has access to secure values. If a secure value is written to a non-secure column, the masked value (**********) is written. Fetch query conditions do not have access to data store secure columns. |
|||||||||||||
|
Expression builder has access to secure variables and values. Comparisons allowed with data store secure column values. |
|||||||||||||
|
Access secure variables with open form types as follows.
|
|||||||||||||
|
Access secure variables in almost all places where variables are referenced. |
|||||||||||||
|
If you assign a secure variable to the text detail (the caller's unstructured input) then assign secure variables to the extracted words, otherwise the masked value (**********) is written to the variables assigned to the extracted words. |
|||||||||||||
|
No access to secure variables inside prompt fields. |
|||||||||||||
|
Can store URL and request parameters in secure variables. You can assign response values to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
Expression builder has no access to secure variables. |
|||||||||||||
| Send Email | No access to secure variables. | ||||||||||||
|
No access to secure variables. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
Can assign values to secure variables. |
|||||||||||||
|
Input text fields and query parameters have no access to secure variables. Can store the language ID in a secure variable. Can assign the transcribed text and the confidence score associated with the transcribed text to secure variables. The entire message is then masked (**********) in the system log. |
|||||||||||||
|
No access to secure variables. |
|||||||||||||
|
The expression builder has access to secure values.
|
|||||||||||||
|