In our application we had an issue changing the favicon, while we followed the documentation
We mitigated this by calling the AddFavicon action in the OnApplicationReady. But now we have installed version 2.9.0 and our application crashes with a "ReferenceError: Outsystems is not defined."It seems the OutsystemsUI.js is not loaded when the OnApplicationReady runs and while in before the add favicon contained the javascript
It now (in 2.9.0) call a function in the
Is there a neat way to solve this?Kind regards,
Daan
Hello @Daan van Hoeke
We were able to replicate that on our end and it will be fixed on the next release.This was a side effect of the changes done on all client actions that are now using our framework and, in your scenario you don't have the OutsystemsUI.js file loaded the moment you're calling the action.Meanwhile, so that you can be unblocked you can add this code:
Hope it helps and thank you for the feedback.
Cheers,GM
In the module you have to put the OutsystemUI as required script.
That is not so much the issue here, and I doubt if we should do this just to use a building in OutSystems UI feature.
The issue is that this is a breaking change and not documented as such.
I have moved the AddFavicon to the OnReady of the layout. That solves our issue for now, but i would still expect the OutsystemsUI.JS to be there
Great!
Thanks for the quick answer.
Cheers,