How to set a Protection Policy on custom Script Includes and custom Tables?

[georgimavrodiev]

Hello All,

I am interested in setting protection policy to a Script Include of one custom application of mine, along with setting the same to one of its tables.
I've reviewed the documentation about this option. From what I understand, if you are operating in a custom scope and set a Script Include's Protection Policy to 'Protected' - its Script field or in other words - its code - should not be visible to any users who imported the Update Set of the application in another instance. In the same time, if no workarounds (no scripts that remove Protection Policies are used) the user who uses the app in a different instance should also not be able not only to see the script of the Script Include, but also to change the type of the Protection Policy. Yet, this is not what I observed during my tests.

I used two DEV Instances: Jakarta & Istanbul.
I created a custom application on the Jakarta one and set the Protection Policy type of one of its Script Includes to protected.
Then I exported the application via an Update Set and imported it into the Istanbul instance. Once the Update Set was Committed on the Istanbul instance -> I opened the respective Script Include with the System Administrator and here is what I saw:
- I was not able to change the type of the Protection Policy of the Script Include;
- However, I was able to see its code (script);

Could you please provide me with explanation of this behavior plus steps how to achieve the one I am looking after?
If you know for the existence of any more detailed documentation on the matter, but the one available in SNOW Wiki & SNOW Docs, please share link also.

Last but not least -> could you please let me know how I can set a Protection Policy to a table of my custom application?

Thank you in advance!

Best Regards,
Georgi Mavrodiev

[georgimavrodiev]

Addition: After logging out and logging back into the Istanbul instance (on which the Update Set of the custom application was committed), and than switching to the scope of the custom application -> I continue to see the script of the protected Script Include, but in the same time I can even change its Protection Time from 'Protected' to 'None' for example.

P.S: Do I need a ServiceNow employee in order to really protect the Script Include of mine?

Regards, Georgi

[Chuck Tomasi]

When I go in to Studio and create a new script include on a scoped app, the field is editable with standard admin rights.

[georgimavrodiev]

Hi Chuck,

Thank you for helping out!

How I can protect it to not be editable at all on other instances and to not show the Script field in the form?

Regards, Georgi

[Chuck Tomasi · Accepted solution]

Hi Georgi,

This field is mainly intended for our TPP (technical partner program) - those people who create apps and publish them to the store. It's my understanding that it has no effect when going between instances in the same family/company (e.g. AcmeDev, AcmeTest, and AcmeProd).

Script protection policy