When executing an OD application when either the call has been answered by a human or an answering machine I'm needing the completion code for the contact. It is not being populated when I call "Get Contact Data" from OD. I am getting other information (See below)

24/03/2014 08:13:52:251 DEBUG - 2AC250A0F6691E60F454FA6B039E97F7:/POMAgentTransfer : session id:j01lisvmpp2-2014083141047-13 | POMAgentTransfer:Track_POM_Variables | Trace ALL POM Data | pomInfo : null:null:null:null:null:::3:Scheduled Contacts:1:null:null:Frank:88:en-us:Guthrie:9999999999:1:PST:null:null:null:10.104.100.61:10.104.100.61:169:null:3893,3894:null

All I really need to know is if the call was answered by a human or an answering machine. I could build a work around (which I might do until I hear back from you) and use 2 applications, one for Human and one for Answering machine, but I would rather use one application and handle it within the application based on the completion code.

Is there another method I should be using to get the completion code or am I doing something wrong?

Thanks,
Frank

Frank,

The completion code is by default populated by system. It is not required to invoke GetContactData in callflow. Please try accessing pominfo:CompletionCode before using other PDC nodes. IN appl. trace.log it should show completion code as below:

com.avaya.sce.pdc.pim.DataConnector.GetContactAttributeImpl:getVariableValue(pomInfo, SessionID): 569665

com.avaya.sce.pdc.pim.DataConnector.GetContactAttributeImpl:getVariableValue(pomInfo, CompletionCode): Answer_Human

The PomPDCInstallerSite_3.0.0.148.jar release along with POM 3.0 GA version supports this functionality.

Thanks,
Prashant

Prashant, I'm sorry, I must be missing something. I do not see either of the variables being populated in POM version 2.5. I have attached my application trace for your reference. Please let me know what I am not seeing and thank you very much.

BTW - I ended up using an configurable application variable to get around not having the completion code. You will see it in the trace as CallResult.

Frank,

Please note that this will work only for POM3.0 release. In POM2.5 you have to rely on multiple apps or CAV approach you've explained above.