Qlik Community

Ideas

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
BI & Data Trends 2021. Discover the top 10 trends emerging in today. Join us on Dec. 8th REGISTER

Acces to Script for published apps in read-only

Partner
Partner

Acces to Script for published apps in read-only

Hello,

Everything is in the title, I guess. As of today, even when you only want to read the script you have to :
-duplicate an app in your work
-go to your work
-open the app
-go to script
-HALLELUIAH, you get it : read the script
-delete the application once the script read.

This is at least 4 useless time-consuming step to do something basic.


Best regards,

Simon

Bi Consultant (Dataviz & Dataprep) @ Business & Decision
3 Comments
Luminary
Luminary

We have had 2 solutions for this:

the more primitive solution is an extension that displays the load script (https://developer.qlik.com/garden/58a7765279b22ca23d1ae0cb)

The alternative is to store your script externally and use the include or must_include function to read in the script.  This can also lead to using source control as you get more advanced.

Partner
Partner

Hello Jheasley,

Thanks for the comment and the turnaroud but it's all at the initiative of the developer who can choose not to add the extension or nor to store the script externally. A huge part of my job is to audit QS apps that others produce... 😉 I would prefer a native solution by design that does not require rework of hundreds of application.

Best regards,

Simon

Employee
Employee

Marking this is as partially delivered as I'm assuming that you are asking in regards to the QSEoW composition.

But this problem does no longer exist as part of our QSEoCS & QSEoK composition. That's because you are working within Spaces and you as a developer can create / manage / work on an App as usual. At a time where you want to publish the App for consumption into a "Managed Space" we do create a copy of the App for you. But this is not just a copy, there is a parent child relation in between of those Apps. Meaning a developer can continue to work on the App in their Personal or Shared Spaces, accessing the script, changing the App, etc. When ready you can republish the App and this overrides the published version in your Managed Space while the parent version of the App stays with you in your Personal / Shared Space.

The whole concept of Spaces is well described as part of our help page: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/Spaces.htm

The ability to show the Script as part of a published App within your QSEoW environment is something which I'll review together with our development teams and add it to our backlog.

Please let me / us know if you want to talk more in detail about those supported scenarios as part of Spaces.

Thomas

Status changed to: Partially Delivered