This is a post to notify you about an upcoming change to Custom Widgets in the next month.
We have made some changes to how Custom Widgets are loaded in Tulip Apps to provide the ability to use even more powerful capabilities like more powerful browser APIs like camera, microphone, geolocation, and more.
However, this will mean that customers using existing and new custom widgets will need to update their domain lists to include “*.tulip-custom-widgets.com”.
I can provide a little more context about the changes to the domains used to load Custom Widgets. In the near future Custom Widgets will be loaded using a unique subdomain for each Custom Widget. An example may look like cw-9b7d5910e8b0ccc0818a65a17d89c0aec670751d.tulip-custom-widgets.com . In order for Custom Widgets to successfully load, any firewalls used to control outgoing connections in your organization’s networks will need to be configured to allow any subdomain of tulip-custom-widgets.com . This is often represented by using a wildcard * in the domain like *.tulip-custom-widgets.com , but might be configured differently in different systems.
This would impact existing and new custom widgets so we would recommend both.
If not updated in time, some custom widgets may not work properly. Tulip will be implementing safeguards and try to ensure that customers have been notified before we roll out this change.
