Script Include Protection Policy

[tschaller]

When creating a new script include, I set the protection policy to "protected" and can no longer make changes to it.

As I understood the protection policy field, this would only come into effect when users other than the creator attempted to edit it. Even as the user who created the script include (and as admin as well), I still cannot edit this file.

Is there something that I can change on my end, or is this something that I will need to have a ServiceNow admin change?

[tschaller]

Ahh, interesting. No, when I set the protection policy in an application, it works just fine.

So, just so I'm clear, in the latest version, if you create a script include in the Global scope, the protection policy is read only?

Thank you for your help. That information clears up the why.

Now, is there any way that I can remove global.ValidateUserRoles from my current Fuji instance? I would like to recreate it in the Global scope (though this time, with the information I now have, I will NOT set the protection policy on it).

[Pradeep Sharma]

Hi Tom,

The protection policy field is not selectable for latest release in case you are in global scope.

For current situation, I have modified the script include protection policy. Please check and let me know if you are facing any issues.

[tschaller]

Everything looks good in my instance now; thank you again for your help!