With the design work to introduce Spaces, available in Qlik Sense cloud-based editions and discussed in Part 1 of this series.... today Fredrik Lautrup is back with Part 2 - sharing how his team wants to evolve the life-cycle for content in Qlik.
Observing and talking to our customers we have seen that there are often two needs that the customer wants to cater for with their Qlik platform.
The ad-hoc flow where you develop concepts and explore data. Here it is important that you can be agile and collaborate on content quickly.
The governed flow where quality and control are important to create trust with the users who want to make decisions based on the data.
So, we set out to create the two flows. In the ad-hoc flow we have personal spaces as a starting point where you can do experimentation and exploration of your data and the shared spaces where you can continue your collaboration around with others on the data.
Both these space types are targeted for self-management allowing users to quickly and in an agile/collaborative way work to author content.
But once we have content that we want to move into production for consumers and self-service users to explore and make decisions on we have a different set of requirements targeted at creating trust.
Here we have the managed spaces which introduce a more controlled release process allowing users to trust the quality of content.
With two flows, ad-hoc and governed, we need a way to bridge them. This is publishing.
The publish workflow allow developers to continue developing while consumers and self-service users can start using the content to make data driven decisions. This is achieved by the publish workflow by creating a copy and move one of the items to the managed space locking it for changes. While maintaining a linked copy in the ad-hoc flow to continue building on. When a new version of the app is ready the content can be moved in a controlled manner into the managed space again.
With the publishing as a bridge we have been able to evolve the content life-cycle to both support an ad-hoc flow for the agile/collaborative work and bridge this with the managed flow to maintain the trust in the data.
But even if this default life-cycle has evolved there are always more advanced use cases that we would like to support, so in the next post I will walk through some of the more advanced capabilities that will be built out to support things like data movement and release management of content.
If you have questions or ideas, please do not hesitate to put a comment below.
For more information on spaces and our cloud editions of Qlik Sense check out this 2 part videos series plus bonus video on Spaces.