The role is connected to an AD entitlement that we have no reason to believe there is anything wrong with the configurations of. To test the automated provisioning we observed a user with the primaryrolecode in question.
After performing an account aggregation the role was not provisioned for the user. We attempted enabling access requests on the entitlement (which shouldn’t be necessary considering it is set globally). This did not seem to fix it. We also attempted changing the operation logic to “Equals” and performed another aggregation, this also did not remedy it.
I’m not sure what we’re doing wrong with this one? It’s my first time automating roles, so I apologize if it’s something obvious I’m overlooking. Any help is appreciated.
Wow, thanks Jesvin. So does that mean everytime I enable a roll and want it to automatically propogate to the appropriate users I need ot select the Apply Changes button in the roles menu? If that’s the case it just seems like I was missing a simple step.
