Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
Announcing the formal deprecation for Qlik Sense Widgets and Custom Components. This is effective for all editions of Qlik Sense Enterprise on Windows (client-managed editions). Similar or enhanced functionality of widgets are now offered through the Dashboard and Visualization bundles!
Environment: Qlik Sense Enterprise on Windows
FAQ:
When will this happen?
Widgets and Custom Components will be removed when the Qlik Sense August 2021 release achieves general availability.
Will it be fully removed from the platform?
Yes.
Will my widgets and custom components continue to work?
The last release widgets functionality is part of client-managed editions of Qlik Sense (Qlik Sense on Windows) is May 2021. Creating new widgets, editing existing widgets, and widget use will no longer be supported in Qlik Sense on Windows beginning with the August 2021 release.
Will widgets and custom components become available in SaaS editions of Qlik Sense?
No.
Are widgets being replaced with new capabilities?
Many of the benefits from widgets are now offered out of the box in Qlik Sense! Proceed to the Dashboard and Extension bundles within the Assets Panel. Here, you’ll find objects such as Multi KPI Chart, Variable input controls, sliders, action buttons, and more.
These Extension Bundles are now offered within the platform and supported by Qlik R&D through future releases.
Is there a way to convert my widgets to visualization extensions?
Unfortunately, there is not a way to transpile syntax used in widget development into JavaScript. We recommend replacing deprecated controls with the native controls found within the platform.
@Jamie_Gregory getting permission to use widgets in a secure environment was hard enough, but getting permission for extensions is nigh-on impossible. I could code the widget I need in 10 minutes and it's laughable that the simple label I'm talking about isn't available anywhere in the supplied objects or bundles and requires an extension now.