I am hoping I can get an answer too my use case here.
Use case: User clicks a button - a pop up appears - user enters some 10 fields - user clicks submit. Post Processing activity updates values on parent case by doing obj-open-by-handle.
Requirement: The parent case and child case both are system generated. User should be able to only access child case but not parent case.
To achieve this, I have updated access role for parent to '0' so that user will not be able to access parent case from perform mode. However, the user is not able to do Obj-Open-By-Handle on parent after the ARO change. Any way we can achieve this (other than removing all the parent case references from the UI)
***Edited by Moderator Marissa to update platform capability tags****
So, the user needs to update values on parent case while he is on child case (Obj-Open-By-Handle; Param: .pxCoverInsKey). If the user himself opens the parent case by clicking the parent case key (from top left), system should not let him. If I try to achieve this using ARO, Obj-Open-By-Handle also failing.
Since the user is already on the child case, he would not need to obj-open-by-handle the same case.
So is there any way i can achieve this. Pega methods should have access to parent case but not when user tries to click the parent case link (top left in perform)
Posted: 3 years ago
Posted: 26 Jul 2019 19:35 EDT
Michael Michalski (MMIchalski)
Senior Consulting Manager - Public Sector