Suggest an Idea

[SubbuAcharya]

We follow 3 tier Architecture for developing our Qlik View/Sense Dashboards. With this approach, we have a Data Extraction layer, Transformation Layer and a Presentation Layer (the dashboard).

In a Qlik View setup, when we promote the Applications to Production, we move all 3 layers into Production, while the first 2 (Extraction & Transformation layers) will only be available under Source Documents and will be scheduled to run periodically, the presentation layer will be moved into User Documents as well (and scheduled) and will be available to the uses.

However, in Qlik Sense, the Stream is the only folder available for all related layers of an application. Since all apps in a Stream will be visible to the user, we are not maintaining the extraction and transformation layers within the Stream, instead maintaining them in a separate but common stream (common for all apps in Production). Our Admin will maintain these layers in that common stream. This is not convenient for developers and as the number of applications  grow, causing a maintenance issue.

The idea is to have a feature/functionality that enables us to maintain all layers related to an App in a Stream while only exposing the dashboard layer to the users.

[Thomas_Hopp]

Hi @SubbuAcharya  I'm going through a couple of posts today and this one is actually delivered but to our SaaS platfrom only. Within a QSE SaaS Tenant you have the ability to use Spaces for data files or data connections only and only publishing an App to your consumers which they will use out of a different managed space. The Space concept in our SaaS Platfrom gives you all this flexibility to use a relative path for instance to reload an App based on Data which comes from a different Space, etc. And by using Spaces you can setup a 3 tier (DTAP / Dev Test Prod) scenario into one Tenant.

Have you been using Spaces in a SaaS Tenant before ?

Let me / us know if you have further questions.

Thomas