Question
Lanit
RU
Last activity: 12 Jan 2016 10:52 EST
Search security customization
Hello everyone!
Our system goes to production now (PRPC 7.1.8). System contains standard search panel - we have no customization here.
And now users can found any work object with with this search. Which is not good - users must see only work objects in which they are included as work party. So, if you are in work party of WO - you can find and open WO, if you don't - WO doesn't appear in search results.
What is the Pega way to create such functionality?
Kind regards,
Ilya Fedotochkin
Accepted Solution
Lanit
RU
So, we can't do anything with search result until new releases where must be indexing of embedded properties. But we can manipulate access with Access when rules in Access role names.
Our solution for now is to add access when to Open Instances for Work- class with this condition:
ANY non-empty value in .pyWorkParty().pyWorkPartyUri = pxRequestor.pxUserIdentifier
So user can find foreign WO, but can't open it, which is good for us.
Pegasystems
IN
You might want to refer to this discussion - https://mesh.pega.com/message/180458#180458
Accepted Solution
Lanit
RU
So, we can't do anything with search result until new releases where must be indexing of embedded properties. But we can manipulate access with Access when rules in Access role names.
Our solution for now is to add access when to Open Instances for Work- class with this condition:
ANY non-empty value in .pyWorkParty().pyWorkPartyUri = pxRequestor.pxUserIdentifier
So user can find foreign WO, but can't open it, which is good for us.
Pegasystems
US
Yes, the access-when rules in conjunction with role rules and access group role settings and privileges on the flow and related rules are the expected way to control who can do and see what with work objects. /Eric