Case Level Permissions: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 8: | Line 8: | ||
|- | |- | ||
|Permissions | |Permissions | ||
|This section specifies data security restrictions for objects within the QPR ProcessAnalyzer model (i.e. limit visibility). If the Permissions section hasn't been defined, all the model data is visible to all users having '''GenericRead''' permission for the project in which the model resides ([[User Roles and Permissions|more information about roles and permissions]]). Permissions defined in this section, are only available | |This section specifies data security restrictions for objects within the QPR ProcessAnalyzer model (i.e. limit visibility). If the Permissions section hasn't been defined, all the model data is visible to all users having '''GenericRead''' permission for the project in which the model resides ([[User Roles and Permissions|more information about roles and permissions]]). Permissions defined in this section, are only available when using the[[Installing QPR ProcessAnalyzer Server#Configure_Web_Service_to_use_In-Memory_or_In-Database_processing|In-Memory core]]. | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 18:15, 7 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 | This section specifies data security restrictions for objects within the QPR ProcessAnalyzer model (i.e. limit visibility). If the Permissions section hasn't been defined, all the model data is visible to all users having GenericRead permission for the project in which the model resides (more information about roles and permissions). Permissions defined in this section, are only available when using theIn-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" } }