Spawn
This help page is for Desktop Studio. If you're part of the CXone Studio Controlled Release (CR) program, you can find this information in the CXone Studio online help. If you're not part of the CR program but want to be, contact your CXone Account Representative.
|
Fires off an IVR For a script to spawn successfully, the skill associated with the to-be-spawned script must meet two conditions:
This also applies to spawning a script directly from the platform (Click the app selector Spawned scripts run parallel to the calling script. When a calling script triggers a Spawn, the spawned script begins immediately while the calling script continues processing. The Start Date for the Spawn action and the to-be-spawned script both use the |
Supported Script Types
|
|
|
|
|
|
|
|
Generic |
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 default is the action name. |
ScriptName | The script you want to spawn. You can click the Choose Script link at the top of the action's properties box to select a script stored for your |
SpawnIDVar | The name of a variable to receive the unique identifier, the Contact ID![]() |
Skill |
Select an ACD skill![]() |
StartDate |
The start date for the spawned script.
The action and the to-be-spawned script both use the |
Parameters |
Parameters that are passed into a script appear in that script's trace output in the Begin 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. |
OnLinked | Path taken if the spawned script issues a voice Later, when the child script executes Link, the parent script will stop processing and jump to the action attached to the On Linked branch. |
OnTerminated |
Path taken when the spawned script finishes. The Spawn action will not suspend the script waiting for the OnTerminated branch condition to trigger. Instead, the Default branch condition will be triggered and the OnTerminated branch condition will be remembered. This is an Interrupt event.
Later, when the child script terminates, the parent script will stop processing and jump to the action attached to the OnTerminated branch condition. |
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. |
Tips & Tricks
- To have a Spawn action create a one-time script schedule, simply specify a start date at least 10 minutes in the future. If a start date is not specified, the targeted script is immediately spawned.
- The Spawn script action can trigger a new script. Use Spawn to perform actions that must occur at the same time. Typically, actions happen one after the other. The first action must complete, then the second action is triggered.