GETRICHMESSAGE

Passes rich message JSON to the digital AskCaller action or TExtMsg action.  This allows you to use rich message templates created on the digital Point of Contact page in ACD in your scripts instead of building the JSON in the script.

Dependencies

• This action requires Digital Experience.
• Before working with digital scripts, learn about the differences between traditional ACD scripts and digital scripts.
• Must be used with one of the following actions: AskCaller (Digital) or TExtMsg.
• Place GETRICHMESSAGE before AskCaller (Digital) or TExtMsg in your script.

• Support for rich messaging content type varies by channel, as shown in the following drop-down.

  Learn more

• Create rich message templates to use with this action on the Point of Contact Digital page in CXone. You can create templates for list pickers, time pickers, rich links, and quick replies. If you need to use other rich media, you cannot use this action. You must build the JSON in a Snippet action and pass it directly to AskCaller or TExtMsg. See the Dependencies section in the online help for those actions for more information.

Supported Script Types

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.
channelID	Select the digital channel this script uses to send messages.

Output Properties

These properties contain variables that hold data returned from executing the action. They're available for reference and use when the action completes.

Property	Description
resultSet	Holds the JSON returned from CXone. Pass the contents of this variable to Askcaller (Digital) or TExtmsg.

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.
OnSucess	Path taken if the action completes without errors and any API calls or data returns were successful (2xx response codes).