Proactively Managing Qlik SaaS

Since introducing Qlik SaaS, Qlik is increasingly choosing to release new features there exclusively. We're seeing that this causes many companies to switch from their "Client-managed" environment to the new Qlik SaaS environment. For this new Qlik SaaS environment, it can add real value to have it managed by an external party. In this blog, support manager Calvin Bergkamp gives you the six main reasons why you should put actively managing your Qlik SaaS environment at the top of your priority list this year.

#1 Managing self-service BI

Qlik SaaS, even more than its predecessor, is focused on self-service BI. This means end users increasingly get to work with the available data themselves. They can use it to create and share insights or reports. This is hugely valuable, but when the environment isn't managed properly, it becomes cluttered instead. It's important to keep the environment as "clean" as possible, to maximize the benefits of the new features. A support team can help your organization manage all the objects created by end users, so you only see what you want to see.

#2 Investigating failed reloads

Apps showing incorrect or outdated data is one of the main frustrations in BI. Unfortunately, these frustrations occur more often than desired. This happens, for example, when an error is generated in the script because a connection to the source can't be made, or when the source data has changed.

When this happens, you want it resolved as quickly as possible, and a support team helps you with that. They take responsibility for getting the dashboard back up to date as fast as possible. They analyze the problem and set follow-up actions in motion as quickly as possible, so your new data becomes visible again quickly.

#3 Setting quality requirements

Solving data-related issues is one thing, but preventing these issues is preferable, and that's naturally what you want to achieve.

We're convinced that apps need to meet certain quality requirements before they go into production. A support team draws up these quality requirements together with you, and enforces them so every new app or update to an existing app meets the set requirements.

When drawing up these requirements, they don't just look at preventing data-related issues, but also at the usability and efficiency of the dashboard. In Qlik SaaS, you can monitor your app's performance even better and make sure slow dashboards are a thing of the past.

#4 Development process

Unlike Qlik Sense Enterprise, with Qlik SaaS your entire development process takes place in a single environment. When you handle this well, your processes become more efficient and organized, but when this process isn't monitored, you run the risk of the environment turning into a mess. To prevent this, you'll need to set up processes to put your apps in the right places. A support team helps you manage your versions and promote newly developed apps to production once they're ready for it.

#5 Supporting new features

Qlik SaaS has introduced the 'Application Automation' feature. With this feature, you build automated analysis and data workflows. You use it to carry out basic processes such as receiving data, exporting data, or sending an email. It's also possible to create advanced processes, such as comparing your data or using webhooks. Besides the standard automations Qlik offers, users also use their own custom-built automations. A support team supports you by managing the automations that have been built, but also by sharing experience and thinking along with you about new automations.

#6 Proactive monitoring

Besides responding to questions and issues coming in from your Qlik SaaS environment, a support team also proactively monitors the environment for performance and growth. If an app becomes too large, it might no longer fit within Qlik's standard tier. To prevent you from paying too much, they notify you of the changes before they're implemented. The same applies to the use of your analyzer and capacity licenses and the automations you've started, which remain free up to 5000 automations.

Written by Calvin Bergkamp
Support Manager