Save Variables

Transfers customer defined variables from their calling scripts to their OnDisposition action scripts.

Dependencies

A Snippet action must always precede this action. The snippet is where the variable information is created, the Save Variables action is where the variable information is stored.

Supported Script Types

The icon for a Generic script type - a rectangle with < and > symbols inside it.

The icon for the Email script type - a large @ symbol in a diamond.

The icon for the Chat script type - a chat bubble with an ellipsis inside (...), in a diamond shape.

The icon for the Phone script type - an old-style phone handset with curved lines indicating sound coming out of it.

The icon for the Voicemail script type - a symbol that looks like a cassette tape - two circles sitting on a horizontal line.

The icon for the Work Item script type-a piece of paper with one corner folded down and a bullet list on it.

The icon for the SMS script type - a smart phone with a chat bubble coming out of it.

The icon for the Digital script type - a computer monitor with a smartphone next to it.

Generic

 Email Chat Phone Voicemail Work Item SMS Digital

Input Properties

These properties define data that the action uses when executing.

Property

Description

Caption

Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.

ProspectiveContactId

The value for this property should always be _prospectiveContact.ProspectiveContactID.$value. This allows your variables to show up in the OnDisposition script.

CustomVariables

The name of the dynamic data object that was created in the Snippet action prior to this Save Variables action.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition

Description

Default

Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
Success Path taken if the action completes without errors and any API calls or data returns were successful (2xx response codes).
Error Path taken when the action fails to execute properly. For example, when there is an unexpected problem such as poor connectivity, syntax errors, and so on. The _ERR variable, with a single underscore character, should be populated with a condensed explanation of the problem.

Script Example

This is an example to show how this action can be used in scripts. It is not intended to be a complete script. Additional scripting may be required.

This example is a subscript that uses a Snippet and Save Variables action to create and store dynamic data that should be sent to an OnDisposition script.

The Snippet action contains code similar to this:

And the properties of the Save Variables action should look similar to this:

Download this script.