You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, the opwidget snippet should be generated with the property utility instead of service.
Ex:
{
"utility": "opwidget",
"widgetId": "6000"
}
Fundamentally, it still works with property service but it tries to load a file webtools.opwidget.css which does not exist. This is why it's better to switch to utility.
FYI, Webtools changed the code on the Webtools side to prevent a 404 on webtools.opwidget.css however it's still advised to use utility instead of service. THank you and best regards. Alexandre - DIGIT WEBTOOLS
Dear colleagues,
Alexandre from DIGIT WEBTOOLS.
We'd like to report an issue detected thanks to this issue: https://citnet.tech.ec.europa.eu/CITnet/jira/browse/WEBTOOLS-17694
Actually, the opwidget snippet should be generated with the property
utility
instead ofservice
.Ex:
Fundamentally, it still works with property
service
but it tries to load a filewebtools.opwidget.css
which does not exist. This is why it's better to switch toutility
.The documentation on Webtools wiki has been updated accordingly: https://webgate.ec.europa.eu/fpfis/wikis/display/webtools/OP+Widgets
Thank you and best regards.
Alexandre - DIGIT WEBTOOLS
The text was updated successfully, but these errors were encountered: