This is a post to notify you about an upcoming change to Custom Widgets.
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”.
If you have any additional questions, please reach out to your Tulip representative.
[As of 3/20] This is intended to roll out in the next few weeks. In r313, we are implementing checks so we can proactively reach out to users who it may impact.
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.
Could you let us know the differences among gardens? I heard this role out will effect to original Tulip garden users.
You don’t mention about target gardens. Right now, maintenance schedule can cover the differences among gardens. Please consider the scope of influence like garden?
This post is treated like normal post but this post needs customers to change firewall policies. This is a big impact for customers. We need two months or more to add firewall policies to their firewall and check if all widgets can work properly. It’s not so easy.
We need a precise plan for this role out like below.
ex)
21st,March → check communication for all users
21st.April → check behaviors of all custom widgets
21st.May → new feature role out for USA gardens
21st.Jun → new feature role out for JPN gardens … etc
Hi @jakerigos
I’m interest by the new widget feature, could you activate in our sandbox, i will send you detail by email.
Our first use case is to implement Scandit Web-SDK (super fast bar code scanner). If there is any Tulip expert that have work on this integration, it would be nice to share experience.
Thanks a lot,
There is no difference in the rollout for gardens.
To address some of your apprehension and expand on my previous point, we are rolling out a check to proactively reach out and work with users with these issues. We deeply care about the impact on customers hence the detailed investigation.
Once we better understand the scope of how this will impact users, we will publish a more granular timeline.
I am also interested in the new feature. Custom widgets are encoded and loaded from a restricted sandboxes in iframe right now.
After the improvement, custom widgets will be loaded from a different domain, enabling the use of browser APIs that were unavailable. Is my understanding right? If so, I would like to try camera API, bluetooth API, and file API. Let me know how I can try it. Thank you.
