I have checked other posts related to this however, the solutions provided have not worked.
The customized unauthenticated access group has access to System-Locks (PegaRULES:SysAdm4 role). The access group that the user is using is PegaRULES:User4 which does not have access to System-Locks. However, the users in non prod have the same setup but is not throwing this exception at all after trying to replicate in the lower environments.
Thank you for the reponse. The Customized Access Group has the PegaRULES:SysAdm4 access role which has Production level (5) access to all.
Setup in Production for users uses PegaRULES:User4 access role which does not have prod level access to System-Locks. I have the same setup in the lower environments and tried replicating the issue, however the issue only occurred in Production. Not sure why is there a difference in behavior though. Should we modify the PegaRULES:User4 access group to have Production level (5) access to all as well?
Posted: 4 years ago
Posted: 16 Mar 2018 7:52 EDT
Mohammad Asif Hasan (Asif Hasan)
Senior Technical Solutions Engineer