Deleting Read-only Script Include (that I created)

Justin Lee2 · ‎04-22-2022

I was reviewing a Global script include with read-only protection policy. I clicked on "Insert and Stay" to make a copy of the script, that I was going to change to make my own script.

However, the copied script include also has a read-only protection policy (and is in global). I can't delete or rename it.

So now I have a duplicate global (OOB) script. How can I go about deleting this duplicate script?

Thanks

Aman Kumar S · ‎04-23-2022

I found HI article.

Description

An application file with read-only protection policy cannot be deleted. However, it is sometimes appropriate to need such a file deleted, as when a read-only script include is unintentionally duplicated.

Cause

A read-only protection policy applies special protection to an application file that prevents it from being modified or deleted. Only ServiceNow employees can alter the protection policy of an application file, and then modify or delete it.

Resolution

Please contact ServiceNow Technical Support for assistance to delete the application file.

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

Best Regards
Aman Kumar

View solution in original post

Justin Lee2 · ‎04-24-2022

Ok, thanks Aman!

Aman Kumar S · ‎04-24-2022

Glad to help 🙂

Best Regards
Aman Kumar

TylerTeter · ‎10-31-2022

Found a better self service solution than "just ask HI". Maybe do this at your own risk though, I'm sure ServiceNow will think it's a defect and patch it.

1. Move the Insert and Stay update to a new update set.

2. Complete that update set

3. Export that update set to XML

4. Delete that update set

5. Open the XML file in a text editor, and update the following lines:

From this:

<sys_update_xml action="INSERT_OR_UPDATE">

<action>INSERT_OR_UPDATE</action>

...

<payload>... action="INSERT_OR_UPDATE"

To this:

<sys_update_xml action="INSERT_OR_UPDATE">

<action>DELETE</action>

...

<payload>... action="DELETE"

6. Navigate to sys_remote_update_set.list, use the UI action to import the update set

7. Preview and commit the update set

8. Verify record has been successfully deleted

This might let you delete a lot of things you probably shouldn't delete... So proceed with caution.

xiaix · ‎07-26-2023

Very, very clever. This worked wonderfully!

Thomas Wright · ‎05-23-2024

Nice, still working in 2024!
I did try to edit the sys_policy field in the update set XML to no longer be protected but that didn't work, deleting works though so that's useful to avoid a support ticket.