<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Re: Acces to Script for published apps in read-only in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1624344#M413</link>
    <description>&lt;P&gt;Hello Jheasley,&lt;BR /&gt;&lt;BR /&gt;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... &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; I would prefer a native solution by design that does not require rework of hundreds of application.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Simon&lt;/P&gt;</description>
    <pubDate>Mon, 16 Sep 2019 18:01:19 GMT</pubDate>
    <dc:creator>simonaubert</dc:creator>
    <dc:date>2019-09-16T18:01:19Z</dc:date>
    <item>
      <title>Re: Acces to Script for published apps in read-only</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1624331#M412</link>
      <description>&lt;P&gt;We have had 2 solutions for this:&lt;/P&gt;&lt;P&gt;the more primitive solution is an extension that displays the load script (&lt;A href="https://developer.qlik.com/garden/58a7765279b22ca23d1ae0cb" target="_blank"&gt;https://developer.qlik.com/garden/58a7765279b22ca23d1ae0cb&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;The alternative is to store your script externally and use the include or must_include function to read in the script.&amp;nbsp; This can also lead to using source control as you get more advanced.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2019 17:29:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1624331#M412</guid>
      <dc:creator>jheasley</dc:creator>
      <dc:date>2019-09-16T17:29:50Z</dc:date>
    </item>
    <item>
      <title>Re: Acces to Script for published apps in read-only</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1624344#M413</link>
      <description>&lt;P&gt;Hello Jheasley,&lt;BR /&gt;&lt;BR /&gt;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... &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; I would prefer a native solution by design that does not require rework of hundreds of application.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Simon&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2019 18:01:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1624344#M413</guid>
      <dc:creator>simonaubert</dc:creator>
      <dc:date>2019-09-16T18:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: Acces to Script for published apps in read-only - Status changed to: Partially Delivered</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1695851#M1968</link>
      <description>&lt;P&gt;Marking this is as partially delivered as I'm assuming that you are asking in regards to the QSEoW composition.&lt;/P&gt;&lt;P&gt;But this problem does no longer exist as part of our QSEoCS &amp;amp; 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.&lt;/P&gt;&lt;P&gt;The whole concept of Spaces is well described as part of our help page:&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/Spaces.htm" target="_blank"&gt;https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/Spaces.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Please let me / us know if you want to talk more in detail about those supported scenarios as part of Spaces.&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2020 17:26:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Acces-to-Script-for-published-apps-in-read-only/idc-p/1695851#M1968</guid>
      <dc:creator>Thomas_Hopp</dc:creator>
      <dc:date>2020-04-22T17:26:00Z</dc:date>
    </item>
  </channel>
</rss>

