Question
Pegasystems Inc.
JP
Last activity: 26 Jan 2016 10:06 EST
7.1.9 Is there OOTB access when rule which can restrict only work parties can open a work
I have a requirement to restrict a work object can be open only by operators added to the work object's pyWorkParty.
There is a list type work party role which can have multiple operators assuming the same role.
Accepted Solution
Pegasystems Inc.
JP
It seems there isn't any OOTB access when rule, so we created new when rule as below.
Work-.IsWorkParty
When expression evaluates to true:
| @(Pega-RULES:Utilities).IsInPageList(OperatorID.pyUserIdentifier,"pyWorkPartyUri",.pyWorkParty) |
Pegasystems Inc.
IN
Hi
I think you need to modify / create ARO to fulfil this requirement. May be these two articles can help to start with ?
https://pdn.pega.com/how-secure-work-objects-non-authorized-users
https://pdn.pega.com/how-restrict-which-work-objects-user-can-access-rule-access-role-objs-rules
Pegasystems Inc.
JP
I am looking for a specific access when rule to restrict only work parties can open work object.
I don't want to reinvent the wheel if there is one already exists.
For those list type work parties, I couldn't find an easy way to test whether the current operator is in the work parties.
Accepted Solution
Pegasystems Inc.
JP
It seems there isn't any OOTB access when rule, so we created new when rule as below.
Work-.IsWorkParty
When expression evaluates to true:
| @(Pega-RULES:Utilities).IsInPageList(OperatorID.pyUserIdentifier,"pyWorkPartyUri",.pyWorkParty) |
Pegasystems Inc.
US
Please make absolutely certain that if any flows in this case create an assignment to a user, that the user be added as a work party. Otherwise, you will have created a situation where the assignee can't open the very case he needs to work on.