A Qlik Sense app is a task-specific, purpose-built application. The user who creates an app is automatically designated as the owner of the app. An app can be reused, modified, and shared with others.
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.
You can also duplicate, reload, import, export, or delete an app from the QMC.
The Apps overview lists all the available apps. The following table presents the available fields and buttons. By default, only some of the fields are displayed. You can use the column selector (') to add fields.
|Name||The name of the app.|
|Owner||The owner of the app.|
|Version||Shows the engine version, and when applicable, the text Migration needed for apps that require manual migration.|
|Published||The date that the app was published.|
|Stream||The stream that the app is published to.|
|Tags||The tags that are connected to the app.|
|Target app ID||The app ID of the published original app that you have duplicated. When you create a copy of a published app and want to replace the original app, the target app ID is used to identify it.|
The app description, if any.
|File size (MB)||
The file size of the app.
Note: The app file size displayed in the QMC differs from the file size on disk. This is because the size in the QMC only includes data objects, such as fields, tables, and document properties, and not visualizations, bookmarks, measures, etc, that are also included in the .qvf file.
When the app was last reloaded.
|ID||The app ID.|
|Created||The date and time when the app was created.|
This field is updated under the following conditions:
This field is not updated under the following conditions:
|Modified by||By whom the app was modified.|
|<Custom properties>||Custom properties, if any, are listed here.|
Sort the list ascending or descending. Some columns do not support sorting.
Type a string to filter on, or, when available, select a predefined value. All rows that match your filter criteria are displayed. You can filter on multiple columns simultaneously to narrow your search. If a filter is applied to a column, . is displayed.
To remove your criteria, click Actions in the table header bar and select Clear filters and search.
You can combine filtering with searching.
Options for clearing filter and search, selecting and deselecting all rows, and toggling wrapping.
Note: The option Select all rows is applied to the rows that are currently displayed. Any rows that have been filtered out before selecting all rows are disregarded, even if they were selected. The option Deselect all rows is applied to all rows, including those that were filtered out.
|'||Column selector: Select which columns to display in the overview. Click B to reset to the default columns.|
Search – both basic and more advanced searches.
Refresh the page.
Edit the selected apps. The number next to Edit indicates the number of items in your selection that you are allowed to edit.When you do not have update rights for the selected items, Edit is replaced by View.
View the selected apps. When you do not have update rights for the selected items, Edit is replaced by View.
Delete the selected apps. The number next to Delete indicates the number of items that will be deleted.If you do not have delete rights for the selected items, Delete is disabled.
|Publish||Publish the selected apps.|
|P Import||Import a new app.|
|More actions > Export||Export the selected app.|
|More actions > Duplicate||Duplicate the selected app.|
|More actions > Reload now||
Reload the selected app.
Note: In a multi-node site, where the Qlik Sense Scheduler Service (QSS) on the central node runs as master and the QSSs on the rim nodes run as slaves, the task might fail the first time it is triggered through Reload now. This is because the task has not yet been synced from the master QSS to the slave QSSs. The second time the action is performed, the task will work.
|More actions > Create new reload task||Create a new reload task.|
|Show more||The overview shows a set number of items, by default. To show more items, scroll to the end of the list and click Show more. Searching, sorting, and filtering of items is always done on the full database list of items, not only the items that are displayed.|