Finesse custom gadget to write wrap code results to 3rd party
I am trying to create a custom gadget to send a REST API call to LCM to send the wrap up data for each outbound call. I am using the External Rest API sample gadget as my base. Does anyone know how to a) get the outbound account number for the call and reference it in a variable (I need to feed it as input) and b) how can I display that on the screen so I know it was successful? Any thoughts/suggestions would be extremely helpful and much appreciated! Thanks!
Re: Finesse custom gadget to write wrap code results to 3rd party
Take a look at the UpdateCallVariableSampleGadget to see how to get the call variables from the dialog. Assuming that the outbound account number is stored in the BAAccountNumber outbound variable, you can get that information in the same fashion. You can use the browser's debugger with a breakpoint to see all of the variables in the list.
As far as displaying it on the screen, you can do something similar to how the external rest api same gadget displays the response, by just spitting it out to the screen as html. Another option is to the log it using the client logger, which you can see in the browser's debugger or in the client logs (after you submit them).
I think I found another one. For brevity, I'm stripping the soap headers.First, I'm creating a new line using addLine <line>
I need to have a notepad with some saved text to pop up with an incoming call hit to our call center. I am aware of the thick client screen pop gadget, I am working on seeing we can change that to fit our needs. I am unsure to change to get this working
HiWe have UCCX and are using cisco finesse. We have deployed popup screen feature on finesse and it is working fine, but we have a problem. It does not create new tab for each call that is handled and every new call over writes the call info with the new ...
Hi there, Suppose Agent001 is in Ready(userstate) state while Agent002 is in Not_ready(userstate) state. Agent002 makes call to Agent001,Agent001 answers the call & now they are in Talking(userstate) state...