Built something you're proud of? Tell the story. A quick G2 review of App Engine or Build Agent helps other developers see what's possible on ServiceNow. Share your experience.

Reassign UI Action under risk assessments not visible for Central GRC Manager group

ShubhamV6766495
Tera Contributor

Hi,
I modified a existing condition on Reassign UI Action for risk assessments such that Reassign ui action must also be visible to any member who is part of Central GRC Manager group.

((current.state>=2 && current.state<=5) || current.state==10) && ( gs.hasRole('sn_risk_advanced.ara_admin') || gs.getUser().isMemberOf('Central GRC Manager') || new RiskAssessmentUtils().canPerformAssessment(current) )
Unfortunately, it is not working as expected.

1 REPLY 1

Naveen20
ServiceNow Employee

The condition syntax itself looks fine, but two things to check:

1. The banner message is your real blocker. The screenshot shows: "This risk assessment is not assigned to you. Therefore, you can't take any actions on this assessment." This likely comes from a client script or ACL on the sn_risk_advanced_risk_assessment table that hides/disables UI actions independently of your UI Action condition. Even if your condition evaluates to true, that separate logic is overriding visibility. Look for an onChange/onLoad client script or a UI Policy on that table that disables buttons when assigned_to != current user.

2. isMemberOf() can be unreliable with group names. Use the group's sys_id instead for consistency:

gs.getUser().isMemberOf('sys_id_of_central_grc_manager_group')

To get it quickly:

var gr = new GlideRecord('sys_user_group');
gr.addQuery('name', 'Central GRC Manager');
gr.query();
if (gr.next()) gs.info(gr.getUniqueValue());

Recommended fix: Address #1 first — find the client script/UI policy that enforces the "not assigned to you" restriction, and add a similar exception there for Central GRC Manager group members. The UI Action condition alone won't help if something upstream is blocking all actions on unassigned assessments.