Case Level Permissions: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Each QPR ProcessAnalyzer model has '''model JSON settings'''. These JSON settings contain configurations and settings related to the model. The model needs to be reloaded into memory for the changed settings to take effect. | Each QPR ProcessAnalyzer model has '''model JSON settings'''. These JSON settings contain configurations and settings related to the model. The model needs to be reloaded into memory for the changed settings to take effect. See how to [[Project_Workspace_in_QPR_ProcessAnalyzer_Excel_Client#Model_Properties|change model JSON settings]]. | ||
The below defined settings are available. | The below defined settings are available. | ||
Line 25: | Line 25: | ||
|} | |} | ||
== Examples | == Examples for Defining Case Permissions == | ||
In this example, visibility of cases is limited in a way that only those users can see the cases belonging to a user group which name is same as the Region (case attribute). | In this example, visibility of cases is limited in a way that only those users can see the cases belonging to a user group which name is same as the Region (case attribute). | ||
<pre> | <pre> |
Revision as of 22:03, 6 February 2018
Each QPR ProcessAnalyzer model has model JSON settings. These JSON settings contain configurations and settings related to the model. The model needs to be reloaded into memory for the changed settings to take effect. See how to change model JSON settings.
The below defined settings are available.
Section | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Permissions | Permissions section specifies data security restrictions (limit visibility) for objects within the QPR ProcessAnalyzer model. If these settings have not been used, all the model data is visible to all users having GenericRead permission for the project in which the model resides. It is possible to configure additional case level permissions by using these settings. The feature is only available in In-Memory core.
|
Examples for Defining Case Permissions
In this example, visibility of cases is limited in a way that only those users can see the cases belonging to a user group which name is same as the Region (case attribute).
{ "Permissions": { "Initialization": "Let(\"groupNames\", OrderByValue(CurrentUser.GroupNames))", "Case": "Region.In(groupNames)", "EventLogKey": "StringJoin(\"_\", groupNames)" } }
In this example, cases are only visible for users whose user name is same as the Account Manager (case attribute).
{ "Permissions": { "Initialization": "Let(\"userName\", CurrentUser.Name)", "Case": "(Attribute(\"Account Manager\") == userName)", "EventLogKey": "CurrentUser.Id" } }