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?

[Pradeep Sharma]

Hi Tom,

Thanks for the info. I am not able to replicate the issue at my end on fuji patch 10 instance.

I can take a look in to your instance if this is your personal instance assigned as part of developer programme.

[tschaller]

It is an instance assigned in the developer program. What information would you need from me in order to access it?

Or can you look that up on your end?

[Pradeep Sharma]

Looking in to it..

[tschaller]

Thanks!

Just FYI, the script include that I am specifically having trouble with is global.ValidateUserRoles.

(I know that there are two with the same name, but one is in the Global application and the other is in a different app. I don't think they would conflict since they are scoped differently, but who knows.)

[Pradeep Sharma · Accepted solution]

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.