Skip to main content

Managing apps

You can create and publish apps to streams from the Qlik Sense hub, if you have the appropriate access rights. Apps can also be published from the QMC. To publish an app that is created in a Qlik Sense Desktop installation, you must first import it from the QMC. The security rules applied to the app, stream, or user, determine who can access the content and what the user is allowed to do. The app is locked when published. Content can be added to a published app through the Qlik Sense hub in a server deployment, but content that was published with the original app cannot be edited. To publish an app to Qlik Sense Enterprise on Kubernetes or Qlik Sense Enterprise SaaS, you must first create distribution policies, see Distribution policies - introduction

Warning: App extensions are not supported in Qlik Sense Enterprise SaaS. If you publish an app with an extension to a Qlik Sense Enterprise SaaS deployment, the extension will not be available there.

You can only publish apps that are unpublished:

  • To publish an app to more than one stream, you must first create a duplicate of the app.
  • To republish an app, create a duplicate of the published app, edit the duplicate and publish it. Use the option Replace existing app to replace a published app. You can also import an exported app and replace the existing app with it.

If you publish an app from the hub, the app in the owner's Work folder will get a stream icon to indicate that it has been published. If you want to publish the app again, you must first make a duplicate of the published app.

Note: You can duplicate an app if you have create and read access to the app and read access to the Apps section in the QMC. However, for security reasons, the script will only be duplicated if you also have read rights to the script. Access to the script enables editing or removal of section access, and, as a consequence, a possibility to load data that should not be accessible.

When importing an app that is created in a local installation of Qlik Sense, the data connection storage can differ between the environment where the app is created and the server environment. If so, the data connection properties Name and Connection string must be updated to match the server environment. Before publishing the app, check the app in your Work section in the hub.

Note: If the name of a data connection in the imported app is the same as the name of an existing data connection, the data connection will not be imported. This means that the imported app will use the existing data connection with an identical name, not the data connection in the imported app.

Workflow: Apps developed on a Qlik Sense Desktop installation

The following workflow illustrates importing an app created from the hub in a Qlik Sense Desktop installation and publishing the app using the QMC in a Qlik Sense installation:

Create an app in Qlik Sense Desktop installation, then log in to QMC, then Import app. After importing app, if the data connection is incorrect, edit the data connection, then reload. If the data connection is correct, reload. If the imported app does not look OK in my work in the hub, then go to the first step of creating an app in Qlik Sense Desktop installation. If the imported app is OK, then Publish app check if the app was published to more than one stream. If the app was published to more than one stream, then duplicate the imported app and publish imported app to stream A and publish duplicate of imported app to stream B, and then App is available for users with access to the stream. If the app is not published to more than one stream, then publish to the stream, and then the app is available to users with access to the stream

Workflow: Apps developed on Qlik Sense in a server deployment

The following workflow illustrates publishing an app from the QMC in a Qlik Sense installation:

Create app in Qlik Sense installation, then log into QMC, and then reload now or, optionally, create reload task. If the app is published to more than one stream, then duplicate the imported app, publish imported app to stream A, publish duplicate of importated app to stream B, and then app is available to users with acess to the stream. If the app is not published to more than one stream, then publish to the single stream, and then the app is available to users with access to the stream.