Endwi
This help page is for Desktop Studio. This information is also available for CXone Studio.
|
Ends a work item with a cause code to be used for reporting purposes. |
Supported Script Types
|
|
|
|
|
|
|
Generic |
Chat | Phone | Voicemail | Work Item | SMS |
Comparison of Similar Actions
The following actions have similar functions, but with some key differences:
- Discard: Terminates an email script.
- End: Terminates a phone, voicemail, SMS, or digital script. Does not terminate a digital contact, but terminates contacts in scripts with other media types.
- End a Contact: Terminates the active contact. Does not terminate the current script.
- EndText: Terminates an SMS workflow that doesn't include a Regagent action (for digital Any channel, contact, or skill associated with Digital Experience. channels only).
- EndWi: Terminates a work item with a cause code. Does not terminate the current script.
- Exit: Terminates a chat session and disconnects the chat contact.
- Hangup: Terminates a phone script.
- Return: Terminates a subscript and returns control to the originating script.
Do not use the Stop action to end a script. It does not terminate the script and leaves contacts running. This has a negative impact on the CXone servers.
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. |
ContactID |
The contact ID for the work item "contact" that was ended. |
ReasonCode |
Select from a drop-down the cause code that you want to be reported. |
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. |