Suggest an Idea

[ShireyJW]

In various locations throughout Compose, the only option presented to the user is "close" to dismiss a window.  When this button is clicked, whatever changes (either intended or unintended) will be applied.  We notice when doing demos that we don't want to make changes but clicking the "close" button will potentially make changes. 

We would like a more standard set of options whenever there is "code" behind the close button (we would like to cancel out without changes).

[Tzachi_Nissim]

Hi ShireyJW,

Thank you for your idea. Can you please provide specific examples? We are considering changing our experience around metadata editing, but not as a product-wide change.

Regards,

Tzachi

[ShireyJW]

When we are demoing the solution to our constituents, we are opening up screens like ETL mappings and other things to show what was created. The only option to dismiss the screens is to click "close". We know we didn't and don't want any changes (because we are showing, not changing things). Unfortunately, if something was accidently changed by the demo, the "close" action seems to "commit" the changes... even though we don't want that to happen. So, we click close and hope that nothing material happens during demos.

[TimGarrod]

This feature is not planned for Qlik Compose but is under consideration for Qlik Cloud DI

[Meghann_MacDonald]

Hi, this idea has been in "Not Planned" status for over a year and is still not in consideration. If you'd like to open a new request, please visit the Browse and Suggest page and click "Suggest features" and open a new request.

Meghann