- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 02:30 AM
After NewYork Upgrade, Manage of a group with sn_hr_core.admin role is unable to add users to group, He is able to go into Group, click on EDIT, select users and then save. But the system is actually throwing a message as below.
Gone throw https://community.servicenow.com/community?id=community_question&sys_id=5355ec42dba8fb405ed4a851ca96... but in roles table, Assignable BY is also present as sn_hr_core.admin.
This worked fine in Madrid. Earlier in Kinston or so this Issue was identified but now unsure of the Fix now.
Any small Info would help!!
Solved! Go to Solution.
- Labels:
-
HR Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2020 03:29 AM
The PRB: PRB1358656 is fixed in Orlando and New York Patch 6 releases
Temporary workaround given by Service now :
Solution Proposed:
There is already a problem record: PRB1358656 for the issue which is under 'Testing' state.
As a workaround, you can add 'sn_esign.admin' or 'sn_hr_core.admin' to the 'Assignable by' field of the role: 'sn_esign.admin' .

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 03:49 AM
Hello Akhila,
Please refer another topic below

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 04:26 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 06:03 AM
I have only seen this when the user does not have the HR Admin role. The HR groups have the role propagated when they have a parent of HR. OOB the HR Roles have an attribute that they are only assignable by HR Admin role, no other role is specified here OOB. In my OOB instances I can just add a user to the HR Admin role and they can add without issues. Have you tried (as a test) to give the user the user_admin role to see if your instance is expecting a different role?
Again, in my OOB, the user I tested with did not have the user_admin role, just HR Admin. Just a thought so you can see where the issue lies.
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 07:10 AM
User has HR Admin role and he is the manager of a group in which group has HR Admin role. Inspite of all this, the group is non-editable for him is the group has any role related to HR, if not in that case. If I give ITIL role to the group then Manager is able to edit the group and add members to the group.
This is only happening in Newyork. This used to work fine in Madrid.
To replicate: Create a group, give HR Admin role to the user and core.manager role as well to view Manage HR group module.(the user should be manager of the group). Now user is manager for a group and he has core.admin and core.manager role.
then add core.admin role to the group and then impersonate as user/manager of the created group, add members to group, UNABLE TO ADD