topic Re: Qlik SaaS Starter Pack - Development & Deployment Workflow best practices in Management & Governance

Qlik SaaS Starter Pack - Development & Deployment Workflow best practices

Michele-Gava — Wed, 01 Oct 2025 16:03:30 GMT

Hi all,

as some of us may know, Qlik SaaS Starter Pack subscription does not provide Managed Spaces (just Shared Spaces)

I'm wondering which best practices to adopt in order to manage development, deployment and re-publishing of apps

In a standard pack subscription, we usually develop in Shared Spaces and publish to Managed Spaces, being comfortable about the fact that:

1) apps in Managed Spaces cannot be modified

2) when publishing from a Shared Space, we can "overwrite" the target app with the modified one

But what if we don't have any Managed Space to keep "safe and secure" our published apps? And what about not being able to overwrite ("re-publish") an app with a new version?

Any idea?

Thanks in advance

Michele

Re: Qlik SaaS Starter Pack - Development & Deployment Workflow best practices

FedericoDellAcqua — Thu, 02 Oct 2025 08:14:30 GMT

Honestly in this case, the starter pack could not be the best solution.

Anyway, you could work within the space "XX" where users have permissions to read, modify and consume data; then create a space "PROD_XX" (always shared) in which you can move or duplicate the applications validated, and in this space give only read permission to the selected users.

For the republish, I think that you should work versioning your applications (ex. v.1.0.0) adding the serial number to the application name. Then just keep the last version in your production space.

Please leave a like to this comment if it helps you out!
Federico

Re: Qlik SaaS Starter Pack - Development & Deployment Workflow best practices

Michele-Gava — Thu, 02 Oct 2025 15:10:56 GMT

Hi Federico and thanks for your reply

Your suggested solution based on a Dev and Prod space (both of type "Shared") works surely fine for the first release of the app, but I'm still not confident about subsequent maintenance management

Let us state that:

1) Working "live" on the published app is not feasible, because this would expose to end-users an app in development state - not good!

2) Moving the published app back and forth from Production to Devolpment space is neither feasible, as end users won't be able to access the app during develpoment - neither good...

So, how to work it out?

One possibile solution:

a. duplicate the app in Production space

b. move the duplicated app to Development

c. once development is complete, move back the modified app to Production

d. Back-up the initial revision with some versioning naming (for instance: v.1.0.0, as suggested in your reply) - Possibly, move the versioned app back to Development to keep Production space "clean"

Some downsides:

- as far as I know, duplicating an app does not duplicate the scheduled activities (ie: reloading). So, you have to re-configure the scheduled activities from scratch on the modified app after re-publishing

- any personal content (for instance: personal sheets) created by end-users while the app is in development state, will be lost after re-publishing

I totally agree that Starter Pack subscription is a low-cost solution, and, as such, has some limitations. But I also think that the standard workflow of publishing on Managed spaces is quite a core functionality of QlikSaaS....

Anyway, thanks again for posting

Michele