03-13-2018 05:21 AM
I have a TAC case (684122397) for this, but let me ask here too.
After upgrading UCCX/Finess from 11.5(1) to 11.6(1) ES02 loading 3rd party gadgets configured in "relative path mode" fails with the designated tab on Finesse desktop showing:
There were issues rendering this gadget.
Unable to retrieve spec for http://localhost:8082/3rdpartygadget/files/decisyonApp.xml
HTTP error 404 http://localhost:8082/3rdpartygadget/files/decisyonApp.xml
That happens when the gadget, which is hosted on the UCCX server, is configured in "relative mode", that is: <gadget>/3rdpartygadget/files/decisyonApp.xml</gadget>
If the gadget is instead configured to use FQDN it works normally:
<gadget>http://<Finesse FQDN>:8082/3rdpartygadget/files/decisyonApp.xml</gadget>
We want to access the gadget in "relative mode" as mentioned in the relevant documentation, because that makes it independent from the server address, which can change in an HA scenario.
Solved! Go to Solution.
03-13-2018 02:37 PM
Thank you Denise.
After a while the relative path gadget started working again. I believe I was running into the situation described here:
03-13-2018 12:30 PM
Hi,
I've used the relative path with 11.6(1) FCS version and it was working. I wasn't made aware that there was a change for this in the ES. So, what you describe seems to be a bug to me.
Thanx,
Denise
03-13-2018 02:37 PM
Thank you Denise.
After a while the relative path gadget started working again. I believe I was running into the situation described here:
03-13-2018 03:01 PM
Hi,
Glad to hear that it is now working for you. That is still strange that the absolute path worked fine but the relative did not even with that situation you linked. But I guess its good that it works now.
Thanx,
Denise
03-13-2018 03:22 PM
I think what happened is that I had uploaded the gadget on the master only, and for a period of time the HA system tried to fetch it from the slave. While the FQDN config was pointing to the master, so it was fine.
As a side note, there have been a couple more things that didn't worked right after the upgrade:
Needed to set again Supervisors permission for dashboards permalinks.
We use custom dashboards, something in the data "formatting" has changed, so our application had to be corrected accordingly.
Thanks again, Paolo.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide