What is the best practice for customizing applications provided by ServiceNow?

bbarber9
Giga Expert

I would like to know what the best practices are for customizing applications that are provided by ServiceNow, such as Policy and Compliance. I normally work on a dev instance and make changes and test them before pushing up to production. However, because I don't own the application I can't publish updates to it. What is the best way to modify an application provided by ServiceNow and push those changes from one instance to another?

1 ACCEPTED SOLUTION

Chuck Tomasi
Tera Patron

Hi Breyton,



The best practice is to create a new application scope and capture your changes there. This enables the use of Studio, source control, and publishing   your app rather than the legacy update sets. I have a colleague who is mere days away from publishing a blog article on this with great details (and caveats). I will socialize it when it becomes available.


View solution in original post

7 REPLIES 7

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hello Breyton,



There are two use cases when considering application scope: extending an existing app or creating a custom app from scratch. If you are extending or modifying an existing global scope application and the changes are having a high impact on other applications, then leave the change in the global scope. However, if the changes are going to have less impact to other applications, then the modifications can be done as a scoped app.


Understanding Application Scope on the Now Platform (Whitepaper)


poojamehta237
Tera Contributor

Hi,

Please look into the given look for brief understanding

https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/success/quick-answer/...

Thanks!