QVW Module Security for Document Prompt when Opening a QVW in QlikView Desktop or with IE Plugin Client from AccessPoint

[Chip_Matejowsky]

When users open a .QVW file containing a macro using QlikView Desktop or from AccessPoint using the IE Plugin client, the users may be prompted to set a security level for the use of macros.

 

Environment

• QlikView all versions

The selection made by the end-user updates the setting "MacroLaunchConfirmation=" in the %Users%\ AppData\Roaming\QlikTech\QlikView\Settings.ini file under the [Settings 7] section.

Disable Macros = "MacroLaunchConfirmation=0"
Allow Safe Macros = "MacroLaunchConfirmation=1"
Allow any Macro (only for trusted documents) = "MacroLaunchConfirmation=2"

This setting is updated on a per user basis and there is not a 'global' setting within QlikView Desktop or QlikView Server to apply the settings change to all users in the environment.

 

 

Cause

The QVW Module Security for Document prompt is displayed as the %Users%\ AppData\Roaming\QlikTech\QlikView\Settings.ini file contains the entry "MacroLaunchConfirmation=0".

 

Resolution

To prevent the QVW Module Security for Document prompt from occurring in the future, the end-user would need to select Allow Safe Macros or Allow any Macro.

Unfortunately, there is not a universal Settings.ini configuration setting which can be enabled for all previously installed QlikView Desktop or QlikView IE Plugin clients or enabled/turned on during the standard QlikView Desktop or IE Plugin client installation. There are a couple of ways  to accomplish enabling the setting 'globally', outside of QlikView:
(1) A Microsoft group policy object which adds the entry "MacroLaunchConfirmation=1" into %Users%\AppData\Roaming\QlikTech\QlikView\Settings.ini

(2) An MSI installation application of QlikView Desktop or IE Plugin configured with the "MacroLaunchConfirmation=1"setting within the %Users%\AppData\Roaming\QlikTech\QlikView\Settings.ini file.

Please note that the above two methods would need to executed by the customer's internal IT/Group Policy team, as the are not QlikView issues, per se.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.