Script Include Protection Policy

tschaller · ‎01-19-2016

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?

Pradeep Sharma · ‎01-19-2016

Hi Tom,

I see that the script include you created is in the global scope. Generally protection policy is used in case of scoped applications only.

In Geneva instance if you are in global scope the fields "Protection policy" becomes readonly.

Please let me know if you are facing the similar issue in case of scoped apps so that I can take a look.

View solution in original post

Pradeep Sharma · ‎01-19-2016

Hi Tom,

You should be able to make the changes on the instance you have developed the application on. On which release you are facing this issue?

tschaller · ‎01-19-2016

Hello Pradeep,

That was my impression as well. The instance I am working on right now is Fuji.

Thanks for the quick response.

Pradeep Sharma · ‎01-19-2016

Hi Tom,

Thanks for the update. Can you do stats.do and update on which patch you are facing this issue.

tschaller · ‎01-19-2016

Not sure if you need more information than what follows, but I got this from stats.do:

Build name: HEAD (Fuji)

Build date: 10-29-2015_1529

Build tag: glide-fuji-12-23-2014__patch10-10-21-2015