Skip to main content Skip to complementary content

What's new in Qlik Sense February 2022

This section provides Qlik Sense administrators a summary of the new administrative features and improvements available in Qlik Sense Enterprise on Windows.

Administrators should also review the Release Notes before beginning an upgrade or update process. You’ll find the release notes in the Qlik Community.

Information note

Business users, analytic creators, and data integrators should review the What’s New section in the Qlik Sense Enterprise on Windows documentation set.

Qlik Sense developers should review the What’s New section in the Qlik Sense for Developers documentation set.

Data and platform

Run reload tasks in between hours

Reload tasks in QMC have a new capability that allows you to do a custom triggered task to run a reload in between a set of hours during the day.

Reload tasks - Custom option (available in February 2022 Patch 1)

Creating reload tasks

Options to set listening ports and database maximum pool size

Installations of Qlik Sense Enterprise Client-Managed now include options for configuring listening ports and database maximum pool size.

Enable modification to cache-control headers

Adding this capability creates an accessible interface for QMC administrators to modify the cache-control headers. All UI for the content cache control is managed from the content library edit page, under Associated items.

Content library: associated items

Security rule: ReadContentCacheControl

Retire centralized logging

As announced in 2021, centralized logging has now been retired. With the Qlik Sense February 2022 release, you will not be able to configure or install centralized logging anymore.

Allow for SCRAM encryption

New support has been added for SCRAM encryption as part of the Qlik Sense Repository Service when installing and upgrading, as well as the ability to make it a persistent setting.

Database security

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!