Issues with client role assignment rules?

Pete R1 · ‎06-11-2019

Does the client role assignment functionality work for you guys? It seems to be very inconsistent in both my company's instance and my dev instance. I have not made any modifications to the script includes or the scheduled job.

Example from my dev instance.

Condition for the employee role:

Employee Condition Criteria (Notice that 562 profiles match):

After running the "Assign HR Client Roles for Integration Users Sync" job:

Once in a while it will seem to work but I cannot figure out a pattern.

Justin Lucas · ‎06-14-2019

Hi Peter,

We ran into a similar issue in our instance where client roles were not being assigned appropriately. The issue was due to the user being referenced in the Run As field for the "Assign HR Client Roles for Integration Users Sync" scheduled job did not have the appropriate permissions to assign the roles (was set to System Admin OOTB when it needed to be HR Admin). After changing the user, the roles were being assigned consistently. You might also check the "Update Client Roles" scheduled job. I believe the former only applies when you're using an integration.

Note: you may need to add the Run As field to the Scheduled Job form view since it's not on the form by default.

Hope that helps!

Justin

View solution in original post

manasamaniac · ‎06-17-2019

IT Worked !! Thanks a ton...I provided HR admin roles to integration user and the client role assignment rules were working.

Pete R1 · ‎06-17-2019

Hi Justin, this was precisely our issue as well. I wish I had read your reply earlier, I ended up testing all the business rules (they worked fine, as me, an admin), the only piece that would fail was the scheduled job. It was running as a user without the appropriate roles.

It worked fine as soon as I set it to run as a user with the right set of roles.

Thanks!

shetzel · ‎06-17-2019

What I found over the past week where we are setting up the HR Shared Services Application for the first time.

1. My browser would time out. So I could create my assignment rule, deactivate/activate which would kick off a "background" script which would attempt to run through the condition and assign roles but... I think my browser would time out and sn instance would only process about 10,000 users.

2. We went to run on demand 'Update Client Roles' scheduled job. But i had to modify/comment out the glide record condition which didn't match for our first run of this rule against users already in the system. (first time setup issue) Once I commented out the glide condition I could run it on demand and assign roles to the condition of my new rule.

Now we will be ok as each new user added or when someone leaves their employment the scheduled job 'Update Client Roles" scheduled job would take care of role assignment and/or the business rule 'Assign HR Roles' which is on the HR Profile table.

I think sn has a bug as the browser/application shouldn't timeout when adding a new rule. Hope this helps also!

Pete R1 · ‎06-26-2019

I noticed that too when changing client role rule conditions, the change triggers the business rule to run but it seems to only run on around half of our users (probably times out like you said).