Security Rule Limitation: Collaborative Development on Unpublished Apps

[Andre_Sostizzo]

Note: The information below is only applicable to pre-November 2018. For later versions please see the approved Publishing workflow on Qlik Help.  

Inside of Qlik Sense Enterprise, it is conceptually possible to allow multiple users to work on an unpublished app using security rules. Inside of this paradigm, there is a limitation in the security rule framework that can express when this style of security rule or rules are used. Specifically, when a given user publishes an app, the user needs to be the owner of all the sheets (and other app.objects) inside of the app. If this is not the case, then you can end up with a scenario where the sheets owned by other users are not included as a part of the base sheets of the app.

For example:

QMC > App Objects and filtering on the Multi-User App:

What both DOMAIN\Administrator and DOMAIN\qvservice see in the unpublished app:



When the app is published in this state, the resulting app looks like this:

Cause:

Under the current design of the Repository Service, during the publish operation only objects which are owned by the app's owner will be published as base content.

Resolution:

The most ideal method of working around this limitation is as follows:

• Have the user who intends to publish the app, duplicate the app immediately prior to publishing
• Publish that duplicate copy

The process of duplication sets the owner of all the objects inside the app to be the user who is doing the duplication.