The toolbar offers a mix of generic commands, such as opening or saving a script, plus Studio-specific commands, which are described below.
Increase/Reduce Space
As you are developing a script, you may need to re-structure the actions to allocate more space or avoid too much confusing clutter. The Increase and Reduce Space buttons automatically change the amount of space between all actions on the canvas in small increments. You could think of this as if the connectors between actions shorten and lengthen each time you press either button.
Trace
Tracing a script launches the active script and opens the Trace Output window to display the results of the script running. The toolbar provides 3 commands related to tracing a script: starting the trace, selecting an ANI
Also known as caller ID. Listed phone number of an incoming voice call. or DNIS Identifies the number the contact dialed to reach you for inbound voice calls and the number the agent or system dialed on outbound voice calls. with which to trace the script, or the options to trace and capture the next instance that the script runs or continuously trace and capture each instance of the script as it runs (relevant to production scripts). See the Trace Scripts page for more information.
Lock/Unlock Scripts
You can lock a script so that no other Studio user can modify it until you have saved and closed the script. Lock or unlock a script by pressing the Lock Script button (indicated by a padlock). When a script is locked, the canvas background appears white and the script icon on the tab is a locked padlock. When a script is unlocked, the canvas background appears gray and the icon appears as the script type icon. If you have not saved and closed a script before exiting Studio, the script will remain in a locked state until you open Studio again and either unlock or save and close the script.
If you have the appropriate permission (Scripts Lock Override), you can override a locked script and "kick" the user from editing the script. You can view all locked scripts on your business unit in the Locked tab. If you want to override a script lock, search for the script in the Locked tab and kick the user by pressing the Kick button (indicated by a red arrow) or right-clicking on the script and selecting Kick <user> from editing script. If you kick a user from a locked script, that user's saved changes will remain saved. After being kicked from a script, Studio displays to the user a notification the next time they log in. The notification might prompt the user to review changes to a script from the Script History function in the Browse Tab.
An administrator can customize the locking functionality for an entire business unit in the ACD module of the CXone platform. In the business unit Details tab (
and select ACD. Go to ACD Configuration > Business Units.