SNIPPET

Allows you to add custom code to your script.

Dependencies

• Code used in this action must be written in Snippet, an in-house scripting language developed for CXone Mpower. The Studio technical reference guide provides detailed information about scripting in snippets.
• Attributes of dynamic data objects cannot be named __type (with two underscores). This word is reserved for use when parsing JSON from dynamic objects.
• You can make API calls using the Snippet action. The maximum response size is 32 KB. This is consistent with the response size limit in the REST API action.  The limit is strictly enforced to prevent cluster instability and outages. If you can, use the REST API action instead. It has the same limit, but can handle a heavier load. If you must use the SNIPPET action, follow these tips to reduce the size of the returned data: 

  • Filter the data in the API response. For example, if you're using the NICE reporting API to get contacts, you can filter the results by the startDate and endDate of the contact. This API call also allows you to return and limit a top count of items. Refer to the API documentation that came with your script integration to determine what filtering you can use.

  • Update the API request to return only the data you need. For example, if you're using the NICE reporting API to get contacts, you can use the contactId or agentId fields to return only relevant data. Refer to the API documentation that came with your script integration to determine what data limits you can use.

  • If you cannot do either of the previous options, build middleware.

• The maximum size of arrays in Studio is 63 million elements. Exceeding this array size results in the following error in the __err variable in a script trace: Array index out of bounds. The current array index ([index]) exceeds the maximum allowed index (63000000). When the array size is exceeded, the script takes the SNIPPET action's Error branch. If the Error branch is not connected, the script continues to run, but without the array information. You can configure scripts to notify you when the maximum array size has been exceeded by adding an EMAIL action to the SNIPPET action's Error branch. Finally, you can add logic in the Error branch to continue to the script. Note that it will continue without the array information.

Supported Script Types

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.
Data	Contains the custom code added in the Snippet editor window. This can include multiple ASSIGN and DYNAMICcommands, assorted flow control statements, and built-in and user-defined functions.
MaxStringSize	Sets the maximum string size for all commands in the Data property. Options are: Limit2K, Limit4K, Limit8K, Limit16K, Limit32K. This limit applies to integration responses with Rest APIs and SOAP.

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

• Use the asjson() function in a Snippet action and store the resulting JSON in a string variable. Use the string variable in the properties of other Studio actions when you need to pass the JSON data. This approach avoids the possibility of validation errors when saving the script.
• If you're tuning an ASR Automatic Speech Recognition. Allows contacts to respond to prompts by speaking, pressing phone keys, or both.-enabled IVR Interactive Voice Response. Automated phone menu contacts use via voice or key inputs to obtain information, route an inbound voice call, or both. system, there is a set of parameters you can use in snippets.
• The Snippet language provides keyword commands that allow you to declare variables and objects, create loops and iterative statements, and more.
• Studio has built-in functions that you can use in your scripts.
• You can create your own custom functions to use in snippets.
• You can test and debug snippet code in the Snippet editor window.
• Use the test system variable when debugging snippets. It allows you to set the value for variables that are used in the snippet and would be populated by the script when it runs for a contact The person interacting with an agent, IVR, or bot in your contact center..

Snippet Editor Window

The Snippet editor window opens when you double-click on a Snippet action.

The Snippet editor window in the Snippet action has two tabs. Both tabs allow you to create the same kinds of code. You can switch back and forth between the tabs and edit your code in either place. The tabs are: 

• The Text View tab. This is a free-form text field where you can type your code out manually.
• The Tree View tab. This is a graphical interface you can use to build your code. This tab has a list you can select keywords from to add statements to the snippet.

Script Example

In this simple example, the code in the Snippet is used to test whether a prospect can be created using information from a third-party system.

Download this script.