Dependency role evaluation
Hi,
"Enable access configuration in App Studio", when this option is selected in Access group, an AccessRole appears like Accessgroupname+"Managed". Does that influence Role dependency hierarcy.
Say I have Access Role 1 and Access Role 2 in Access group. Access Role 1 dependent on Access role 3 and Access Role 2 is dependent on Access Role 4.
So the order is,
Access Role 1
Access Role 3
Access Role 2
Access Role 4.
If the Accessgroupname+"Managed" access role comes into picture where does that fit in the hierarchy
HCA Healthcare
US
@RajaP4318 When "Enable access configuration in App Studio" is selected for an Access Group, Pega automatically adds a "Managed" role (like AccessGroupNameManaged) to support App Studio configurations. However, this does not affect the existing role dependency hierarchy or the order in which access roles are evaluated. Pega still processes roles in the order they are listed in the Access Group, and each role’s dependencies (like Access Role 1 depending on Role 3) are resolved as usual. The "Managed" role is just an additional role layered on top and is typically used for simplified access control in App Studio without altering core access behavior. So, your existing role hierarchy and dependency order remain intact.