Result Processors is a container node for Result nodes.
Within Result Processors, you can add multiple Result nodes to handle different dispositions or contact attempt results. Result Processors have only one child node, that is, Result.
If the Runtime Change Pacing Type property is set to ON in the Call task node, you can also add Result nodes relevant to the new pacing type a user can potentially specify in real time for the Call task node.
For more information about changing the pacing type of a Call task node in real time, see Allowing to change the pacing type of a Call task node in real time.
The following table lists the properties of the node and their descriptions:
Property Name |
Description |
Name |
Type a display name for the Result Processors node. If you do not specify a name, the default name is Result Processors. |
Description |
Type a description for the Result Processors node. |
Next State |
Next State has the default value as done. If a particular result is not handled by adding a result node, the Next State value from the Result Processors node is used as the Next State for that result. By default it has three values: initial, done and wait. As you add new handlers in the campaign strategy, those states are available in the Next State drop-down list. |
Custom Processor |
Use to select the custom processor class that POM invokes for each completion code. You can have:
Publish: If you select this option, POM publishes all results to an ActiveMQ server pom.attempt.result.topic. You can write a client program to subscribe to this topic to read the results from the JMS topic. You can have multiple clients reading results from the topic. POM provides a sample client which you can use as a reference. This sample client reads the results and writes them to a file in the Export folder. You can run the sample client using $POM_HOME/bin/testResProcClient.sh. For more information about the sample client, see Developer Guide for Proactive Outreach Manager. POM publishes every result as an object of type PomResultInfo, comprising of: String campaignName,int jobID, long pimSessionID, String contactID, int contactGroupID, String contactGroupName, String address, String result, String zoneName For more information, see Application notes on Avaya Support site at: http://support.avaya.com Custom: If you select this option, you can specify a Java class for processing custom results. This Java class must implement the PomCustomResultProcessor interface. POM initiates this class and invokes when a result is available. The result data is passed as part of PomResultInfo parameter. None (Default)
POM ActiveMQ documentation addition for producer.setTimetoLive() & activeMQ logging enablement. Scenario 1: A client (subscriber) can receive a real-time event from ActiveMQ in a delayed manner due to network latency. In such cases, the client gets the event but discards if the timestamp of the published event is 6 secs or more than the event received timestamp by the subscriber (client). Scenario 2: Client (subscriber) machine is not time-synchronized with POM Server via an NTP Server. The time difference is “variable” and not consistent. On some customer environments, it was seen that due to this, the behavioral pattern varied. At times when the time difference was less than 6 secs, the subscriber received the event but did not discard it, and the client application registered the entry of the event. Whereas at times when the time difference was 6 or more seconds, the client discarded the event as the time to live set by the producer had expired. |
Result Processor Custom Class |
Specify the custom class. |
Edit Description |
Click to edit the description of the Result Processors node. |
