-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cisco Finesse Thick Client gadget #4
Comments
Which version of the gadget are you using? |
Gadget 10.6, UCCX 10.6.1 |
Can you follow the instructions from the 11.0.1 v1.1 gadget and see if it works? |
Same result - the java version we are on is: Java 8 - update 74. Still receiving the "Class not found exception". |
Can the webserver where the ThickClientScreenPop.xml is uploaded to ping the location of the jar? RE: |
That looks correct. Did the WeindowsApplication.exe get executed? |
Hi Denis, |
Hi, I tried this out on my system and it is working correctly. I didn't use the WindowsApplication.exe because it wouldn't execute when I manually tried to run it myself. I chose a different executable that worked for my path for the workflow. The documentation says: gadget is tested on a Microsoft® Windows 7 (64-bit) with Internet Explorer 11 and JRE 8 Update 101. Are you using IE11 on windows 7. It doesn't work on Chrome or FF. You mentioned that you have java 8 but only update 74. Maybe you need to upgrade to the latest? What did you put in the in ThickClientScreenPop.xml? You should be able to download the jar by putting the codebase url + JavaScreenPop.jar. Are you sure you have allowed the JavaScreenPop App to run in step 5 of the instructions? Thanx, |
Hi Denise, |
Hi, |
Hi,
i have implemented and followed the guide to implement the "Thick Client gadget"
https://github.com/CiscoDevNet/finesse-sample-code/tree/master/ThickClientScreenPopSampleGadget
The problem i am facing is the following:
Not sure if i have missed some thing, or there is a change in the .jar file, which needs to be done?
Thank you.
The text was updated successfully, but these errors were encountered: