Signal

Communicates with another script by triggering the Onsignal action event. Use the Signal action to interrupt another script and pass parameters to it. Up to nine parameters may be passed. The other script may be actively processing other actions when the signal arrives. It will immediately abort whatever it is doing and jump to an Onsignal event action, if one is present. An example would be creating an after-hours tech support script. A customer calls in and multiple scripts are spawned to call four on-call technicians at the same time. When one of the scripts reaches a live technician (rather than voicemail or no answer), the spawned script signals the original script and the two calls are joined.

Dependencies

• The current implementation does not ensure that multiple ONSIGNAL events will not interrupt one another. It is possible for a script to be signaled twice at the same moment and behave as if it were signaled only once. This can be avoided by careful script writing.
• You must reference the correct Contact ID A unique numerical identifier assigned to each contact. Typically this is handled by using a variable saved in the database using the Putvalue action.

Supported Script Types

Generic	Email	Chat	Phone	Voicemail	Work Item	SMS

Input Properties

These properties define data that the action uses when executing.

Property	Description
Add Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon.
Contact ID	The unique identifier of the script to signal.
Parameters	A value (0-9) that indicates the number of parameters to send to the signaled script. Parameters are named SP1 through SPn (where n is the parameter count).

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.
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.