Skip to main content Skip to complementary content

What's new in Qlik Sense May 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

Updates to distributing apps from Qlik Sense Enterprise Client-Managed to Qlik Cloud

New capabilities now make distributing apps from Qlik Sense Enterprise Client-Managed to a Qlik Sense SaaS tenant more robust and scalable. A new distribution task is available in the Qlik Management Console. You can schedule the distribution of apps using distribution tasks in the same way that you schedule app reloads using reload tasks. Once an app has been distributed to Qlik Cloud, on subsequent distributions, the Application Distribution Service will only update app data when it detects a change from the last reload, reducing the amount of network traffic between Qlik Sense and Qlik Cloud.

Replacing extensions in QMC

You can now update and replace an existing extension with a new one of the same name in QMC. Existing files are overwritten by the new ones, without affecting the GUID of the extension or associated items, such as, custom security rules.

Importing extensions

Content cache-controls

Hub-specific requests

Further enhancement to content cache-controls allows system administrators to set the caching policy for requests specific to the Hub service. They are to be configured as "global" cache controls, not referencing any content library: "contentLibrary": null. Configured cache-controls are fetched at the startup of the Hub service by looking up the configuration from the "ContentCacheControls" table in the QSR database, therefore, for any changes to take place, you must restart the Hub service by restarting the Qlik Sense Service Dispatcher service.

Default security for admin roles

Updated security rules for ContentAdmin and SecurityAdmin roles now allows read access to Content libraries.

Configuring the expiry date of Qlik Sense certificates

Qlik Sense now offers the ability to configure the expiry date of its certificates. The default value has been changed from 10 to 5 years (60 months). The minimum value is 12 and the maximum value is 60 months. Any value below the minimum or above the maximum will be ignored and set to the border value—12 or 60 months respectively.

Tracking changes to custom properties

For auditing purposes Qlik Sense logging has been extended with additional logging for tracking changes to Custom Properties. The AuditSecurity_Repository logs now include information when new custom properties are added or existing ones are modified or deleted.

Self-service task management—Create, edit, and delete reload tasks in the hub

New capabilities in the hub allow users with the appropriate permissions to create, edit, and delete reload tasks and scheduled triggers.

This feature is released under the feature flag "HUB_CREATE_EDIT_DELETE_TASK", and is disabled (set to false) by default.

Empty streams do not display in the hub

In the hub, streams with no apps—either empty streams or streams that do not show apps due to the existing security rules for a user—will not appear. After you publish or move an app from another stream, or delete an app, the list of streams is dynamically updated and will appear in the hub or be hidden depending on whether the stream contains at least one app. Changes outside of the hub, for example in QMC, will not trigger an update to the stream list in the hub.

Managing streams

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!