Has anyone ever encountered a situation where they couldn't edit a script field in business rules

yana7
Tera Contributor

3 weeks ago

Has anyone ever experienced being unable to edit a script field in business rules even though the user has admin roles?
This happened around 8 p.m.—suddenly, I couldn’t edit the script field, whether I was creating a new rule or editing an existing one.

yana7_0-1793041863882.png

 

0 Helpfuls
  • 634 Views
3 REPLIES 3

Tanushree Maiti
Tera Patron

3 weeks ago

Hi @yana7 

 

Is there any patch update /upgrade  has taken place in your instance recently ?

What version you are using currently ?

 

Zurich release onwards, servicenow has introduced Scriping Governance tool  where Admin role is not sufficient to edit script . 

Admin users must have either:

  1. Membership in the Conditional Script Writer group, or
  2. The snc_required_script_writer_permission role directly assigned to user.

 

The tool monitors any action where a user saves data into a field that could contain executable code. This includes:

  • Business rules
  • Client scripts
  • Script includes
  • UI policies
  • Background scripts
  • Any other scriptable elements

Refer: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2581331

 

 

 

Ankur Bawiskar
Tera Patron

3 weeks ago

@yana7 

looks like you upgraded to Zurich and this is new security feature introduced in zurich

check below links

Scripting Governance Tool: What changed in Zurich. 

Why Your Admins Can't Script Post-Zurich Upgrade: Mastering ServiceNow Scripting Governance 

Help us understand about this group - Conditional Script Writer and role snc_required_script_writer_... 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

Sandesh Powar
Kilo Sage

3 weeks ago

Hi  @yana7 ,

This could be related to Scripting Governance introduced in the Zurich release or later. Having the 'admin' role alone may no longer be sufficient to edit script fields.

Could you please check the following?

1. Verify whether your user has the 'snc_required_script_writer_permission' role.
2. Alternatively, check whether your user belongs to the Conditional Script Writer group.

Official reference: ServiceNow Zurich Release Notes – Access Management 

A related discussion is also available here: Issue: Script editor becomes read only after upgrade 

If you find this solution helpful, Mark this response as Helpful and Please Accept the solution.

Regards,
Sandesh Powar
ServiceNow Rising Star