Prohibit editing document properties for end users in 9.0

[siddharth_kulka]

We migrated from 8.5 to 9.0 SR 3 recently.

Problem:

When the end user opens a qvw file, he should not be able to change/edit document Properties.

Example:- If export to excel is unchecked, he should not be able to check it, and save the file.

Question:

Previously, users were using QV Analyzer in 8.5.

Is this a licensing thing in 9.0 personal edition? What is the user's version called in 9.0? I assume its called personal edition

generically, irrespective of a user or developer in 9.0.

Is this even an issue? OR the user will be automatically prohibited to edit document properties based on his license key and control number?HOW CAN I TEST THIS AT THE DEVELOPER SITE?

Kindly advise. Any help will be appreciated!

Regards,

Siddharth

[deepakk]

hi,

In QV 9 there have removed the concept of Local Analyzer. IN order to achieve your requirement , you need to create the Section Access.

In Section you can provide two types of Access 1) Admin 2) User.

People who have User access can be restricted from Saving, Exporting ,Prinitng etc.

Go to Document Properties --> Secuirty Tab for the user privilages.

[#3 · Accepted solution]

Hi Siddharth,

since QV 9 every user is a developer. Special licenses like ANALYZER or PROFESSIONAL no longer exists.

If you want to restrict a user to ANALYZER level you have to change the registry entries for this user.

You will find explanations and the reg files in the attached ZIP file.

Use it with care!!!

*****************************************************************************************************************************

QlikView Personal Edition
With QlikView 9.0, everyone is free to create QlikView documents for personal use. Hence, a normal QlikView desktop can be run without purchasing a license. There are no limitations, except that it is not possible to open QlikView documents created by other users. Nor is it possible to import an entire layout from an xml file. Technically, every QlikView document is now saved with a user key - information
defining the user and the computer. A QlikView Server or a QlikView User License (a bought license) can open any file, but a user of QlikView
Personal Edition can only open files with the correct user key. Should you change computer, you will not be able to open your old documents
with a QlikView Personal Edition. However, you will be asked to recover your files instead. The difference is that a new user key is generated and used for subsequent files. QlikView will accept four (4) user key changes.

Good luck!

Rainer

[siddharth_kulka]

Rainer,

Thanks for the prompt response.

Now, we have a 500 MB qvw, that gets reduced into 3000 QVW's using QQ Publisher. Some users view them on access point, while the others use their desptops to view the qvws. Do you reccomend registry changes for the above. How should this be implemented? I am skeptical, only because we are talking of REGISTRY CHANGES here. Can you please present an example.

Well, I don't know if you agree with me, but this is a very basic requirement one feels. Should this demand Registry changes!!!

Regards,

Siddharth

[siddharth_kulka]

Also,

Is there a way to have this taken care of during installation itself, based on different users?

Thanks

[#6]

Hello Siddharth,

user of the "Access Point" are not able to change document properties.

There are some software products on the market which helps to craete, distribute and install MSI packages.

The DeskCenter Package Studio allows, especially in conjunction with the DeskCenter Management Suite, creating flawless MSI packages and automated distribution / installation on all Windows platforms.

I recommend to get in contact with QlikTech "Expert Services" in your area to work out the right security concept.

Rainer