Skip to main content

Design

The Design blog is all about product and Qlik solutions, such as scripting, data modeling, visual design, extensions, best practices, and more!

Michael_Tarallo
Employee
Employee

Today our Leigh Kennedy, Principal Enterprise Architect, will walk you through Systems Development lifecycle concepts used with the Qlik Active Intelligence platform.  This is a 2 part series, this entry covers Part 2. Part 1 can be viewed here.

In our last video we looked at how to implement complex SDLC environments in Qlik Sense Enterprise SaaS. However we only looked at this from the point of view of a single path from Development to Production. Some organizations also separate their SDLC tiers horizontally. For example a customer may have Finance, HR and Sales in separate work-streams due to governance, information barriers or simply by preference. How to achieve this is not immediately obvious in Qlik Sense Enterprise SaaS.

In this video we will show how we can build context-aware applications so, your applications will know not just whether they are in Development, Test or production, but also whether they are a Sales, Finance or HR app. We will do this using built-in functionality of Qlik Cloud. We will also look at using these techniques to manage external script libraries so we can ensure we use the correct version of libraries based on where our apps reside.

5 Comments
paulcalvet
Partner - Creator III
Partner - Creator III

Hello,

Very interesting video, I deploy a solution like this :

if (DEV) is present in the name of the app then we use connector and ressources from DEV, if not we use production.

We work with three spaces (dev, test, prd) by functionnal domain and if we want to test our application with data from production so we just have to change the name of the app to swith.

Can you share the script to determine the space of an application ? It could be very useful.

Regards,

Paul

413 Views
Leigh_Kennedy
Employee
Employee

Hi Paul,

 

The video is based on this doc:  
https://community.qlik.com/t5/Qlik-Design-Blog/Managing-your-Analytics-lifecycle-in-Qlik-Sense-Enter...

There are scripts in the doc which cover these concepts.

Hope this helps!

376 Views
barnabyd
Partner - Creator
Partner - Creator

Thanks Leigh,

These two videos contain things that I've been wanting to know for quite a while. I learn from the videos much more readily than from a PDF. So this is great.

Cheers, Barnaby.

0 Likes
319 Views
lvdbrink
Partner - Contributor III
Partner - Contributor III

Instead of devoting a bunch of script lines to calling our own REST API, an alternative way to make our apps context aware that we started using is have a simple .qvs file in the target space next to our app that includes a link to the correct data sources in the correct spaces and then have our script use include with a relative path to load these.

This makes our apps context aware and also enables us to have for example 2 managed spaces with apps using data from a single separate space. That way we don't have to have duplicate QVDs in our environment in cases where the data is relevant for more than one business area.

Just as an aside: it would be so much nicer for Qlik to just make a function called DocumentSpaceName() or similar that just tells you what space this particular space resides in...

160 Views
barnabyd
Partner - Creator
Partner - Creator

G'day @lvdbrink,

That's a great solution to avoid the complex code and is what I used to do in QlikView. It's disappointing that it doesn't work with QS on prem.

Cheers,

Barnaby.

134 Views