Vitara charts will show the ‘Edit’ button when a user hovers cursor on the chart. We have to click on this ‘Edit’ button to open properties window of any vitara chart. Properties window is the only way we can make changes or edit any vitaar chart.
When we run a VI Dashboards or Dossiers in ‘Presentation Mode’ Vitara Charts will NOT show ‘Edit’ popup button. Therefore without ‘Edit’ button users are unable to edit or change any Vitara Chart..
The end users who have only security role - “Run the dashboards/dossiers in presentation mode”, will not get ‘Edit’ button on any Vitara Chart.
By default, irrespective of the user’s security privileges or user permissions, vitara charts will show the ‘Edit’ button to all users who are able to open and execute a report services document.
In some cases it is desired to hide the EDIT button from end users. The following tech note explains the method to hide the EDIT button.
Vitaracharts will use the security model, so that only developers or document designers are able to edit the vitara charts and not the end users.
NOTE: This method of disabling ‘Edit button in Vitara Charts will work with only Report Services Documents, and not with VI Dashboards.
This security model will work by inheriting the user’s privileges and file permissions from MicroStrategy.
In MicroStrategy “User Privileges” and “File Permissions” are the two methods in which we can implement security at different levels of users;
Privileges are assigned to individual user or to a group of users or to a job role (Administrator, Architect, Analyst, Reporter, Consumer, etc.).
Permissions control’s what data users can see and what objects users can use.
Permissions differ from privileges in that, permissions restrict or allow actions to a single object, while privileges restrict or allow actions across all objects in a projects.
The ability for a user to accomplish an action is based on the cumulative security settings of privileges and permissions.
You can allow/restrict a user to edit or modify vitara charts depending on the privileges or file permissions that user has in MicroStrategy.
In Vitara Charts the privilege and permission settings are defined in ‘global.txt’ file, which will be in the Vitara Charts installation folder. Generally it will be in the following path:
Tomcat 8.0\webapps\MicroStrategy\plugins\VitaraCharts\custom.
The following is the screenshot of ‘global.txt’ file, showing only the part of the code related to user security.
The lines which starts with ‘#’ will be considered as a comment. Use the following two lines to set security condition to display vitara charts ‘Edit’ button.
#checkPrivilegeForPropertiesEditor=125
#accessControlLevels= read,write
The code “#checkPrivilegeForPropertiesEditor=125” will deal with user privileges. In this line we have to give the DSSXML Privilege value of a particular privilege on which we want to set a security condition. The default value 125 is the DSSXML Privilege value of ‘Web Document Design’ privilege.
Uncomment this line by deleting ‘#’ to set condition using user privilege - ‘Web Document Design’.
Now only the users who has ‘Web Document Design’ privilege enabled will get edit button for all vitara charts. You can set this condition using other privileges also. For example the DSSXML Privilege value for ‘Web Print Mode’ privilege is 27. Give this values in privilege settings line.
checkPrivilegeForPropertiesEditor=27
The users who has this privilege enabled are only able to edit or modify vitaracharts.
To know more about User Privileges in MicroStrategy browse the following link.
While the security condition defined using user privileges works at user level, the security condition defined using file permissions will work on individual objects in MicroStrategy.
For example, User ‘A’ and User ‘B’ both has ‘Web Document Design’ privilege enabled, therefore both the users are able to edit and execute web documents. Now the security requirement is, user ‘B’ should not able to modified the documents designed by user ‘A’ and user ‘A’ should not able to modified the documents designed by user ‘B’. File Permissions or access control list (ACL) of an object addresses these kind of security requirements.
We can also set these kind of security conditions for Vitara Charts. Vitara Charts will inherit the file permissions a user has on a particular report services document and will show ‘Edit’ button if it matches with the permission set in global.txt file.
The following is the screenshot of properties window where we can set file permissions to a users or a group.
In the ‘global.txt’ file the following code will deal with setting security condition using file permissions.
#accessControlLevels= read,write
By default this line will be in commented mode. Uncomment this line by deleting ‘#’ character.
Suppose you want the users who have ‘Write’ permission on a particular document only able to edit Vitara charts, modify the code as follows,
accessControlLevels= write
Now only the users who have write permission on that particular report services document will get ‘Edit’ button in Vitara Charts.
Choose from the following access control levels - read, write, use, execute, fullcontrol and delete to specify user access control levels for enabling Vitara Property Editor in MicroStrategy documents.
For more information about file permissions in MicroStrategy browse to the following link.
Proprietary and Confidential
