I have implemented the integation of CAD with IBM's Tivoli Service Request Manager(a case management tool) successfully. Neveretheless, one of the agents is facing an issue with this integration. The ideal scenario would be, when a caller calls into the system and punches his ID, all the information for that ID should get populated within the integrated browser. Basically, I am using the HTTP action in CDA and doing a POST to the TSRM url by appending the entered ID. It is working perfectly in all the agents laptops except one. Though I am able to see that the ID is getting populated in the CAD's enterprise data, no data gets populated in the integraed browser (TSRM screen). I have checked the logs on both sides but nothing looks fishy. I looked into the agents's user id previledges in the TSRM, that too looks ok. I then upgraded the IE from version 6 to version 8 but no luck. I am running out of options to troubleshoot this.
Firstly, CAD doesn't use Internet Explorer if you use a HTTP action within the CAD window. It uses it's own browser, which can lead to compatibility issues. If you want to use IE you usually end up using the macro facilities of CAD.
If it's simply not launching the URL, then have you definately added the problem user to the correct workflow in CDA, and have they definately fully closed down the Agent and reopened it to get the changes? If so, perhaps restart the 'Deskop Sync' service in UCCX Control Center and get them to close/reopen CAD to ensure they have the workflow applied.
If that doesn't help, or the URL is being launched but is failing, you need to work out whether it's not working on this one agent because of a problem with CAD, or something else.
I would do this:
1) Run a wireshark capture on the 'bad' agent, see what is sent out by CAD and see what is returned
2) Same on a 'good' agent for comparison
If you send out the same URL in the correct format on both, but one returns an error, then show that to the customer and leave it to them to troubleshoot their app...
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.