A Custom node can be used in Result node of a Call action. When you use the Custom node in the Result node of a Call action, you must select the Orchestration Designer application to be used for that result. Orchestration Designer applications can be used only for results corresponding to successful calls.
A Custom node does not have any child node.
Property
Value
Name
Use this as a display name in the campaign strategy editor. If you do not specify a name, then the default name is Custom.
Description
Use to specify a description for the Custom action.
Application
Select the desired Orchestration Designer application from the drop-down. An Orchestration Designer application shows up in the list only when it is configured as POM Application in Avaya Experience Portal.
VDN
Enter a string here. This is passed as a parameter to the Orchestration Designer application.
Agent Script
Select the agent script that POM must display on the agent desktop.
The following fields are not applicable if you are running a non-agent campaign.
Callback Parameters
Preferred Agent Call back
This parameter is enabled by default. If you disable this parameter, then an agent cannot schedule a preferred agent callback.
Strict Agent Call back
This parameter is enabled by default. If you disable this parameter, then an agent cannot schedule a strict agent callback.
Campaign Call back
This parameter is enabled by default. If you disable this parameter, then an agent cannot schedule a callback for a campaign.
General Call back
This parameter is enabled by default. If you disable this parameter, then an agent cannot schedule a general callback.
Can Cancel Call back
This parameter is enabled by default. If you disable this parameter, then an agent cannot cancel a callback.
Edit Description
Click to edit the description of the Custom action.
