Hello,
So, I'm using the code described in this post in a 10.5 environment. We deployed the gadget and are seeing an ~20% failure rate on the dialog.restRequest API call. It is completely random. The UI basically allows agents, when in wrap-up, to choose from a list of 'disposition codes' and then submit. On submit, the selected code should be written to PV6.
I'm hoping someone else has run into this and can help explain this behavior. We have a TAC case open as well, but wanted to also check w/ the community.
Latest variation of code....
updatePV = function (name, value, options) {
var APIstatus = "Good";
var callvar = {"name" : name, "value" : value};
var callvariable = {"CallVariable" : callvar};
var mediaProperties = {"callvariables": callvariable};
options = options || {};
options.content = {};
//alert("before the updatePV");
options.content["Dialog"] =
{
"mediaProperties": mediaProperties,
"requestedAction": "UPDATE_CALL_DATA"
};
options.method = "PUT";
options.success = function(){
//alert("disposition successful");
APIstatus="Good";
};
options.error = function(){
alert("disposition error");
APIstatus="Bad";
};
currdialog.restRequest(currdialog.getRestUrl(), options);
return currdialog;
};
functionUpdatePV : function ( name, value){
//clientLogs.log("********updating Call Variable " + name + " " + value);
//alert("*********dialog id: " + currdialog.getId() + " NAME: " + name + " VALUE: " + value + " ParticipantState: " + myParticipant.state);
//var value2 = value.substring(0,3);
$("#dispositionResult").text("Disposition Submitted");
var options = {};
setTimeout(updatePV(name, value, options), 1000);
setTimeout(this.setUserState, 1500);
//this.setUserState();
},
Any help would be appreciated.
Thanks,
Ryan.
