Customising ServiceNow Delivered Scoped apps

[MattSN]

When customizing a ServiceNow delivered scoped app should we stick with update sets in the that application's scope or create new custom scope and grant the delivered scope full access to our custom scope in both directions. Then make all the changes in the custom scope.

For example, lets say you're working with PPM and you want to add a new business rule, flow and field. If we create a custom scope and grant the 2 way privileges to the SN scope, all of your customizations will be visible and versioned in your custom scope.

Does this make sense or should we stay with update sets for altering delivered scoped apps?

[Saurav11]

Hello,

As per my knowledge on Scoped apps I think it is the best to work in the same Application scope using update set itself as cross scoping sometimes brings it's own challenges.

Thanks,

Please mark answer correct/helpful based on impact.

[MattSN]

If this is accurate then update sets would be required to maintain customizations. 

[Saurav11]

Yes we need to

[MattSN · Accepted solution]

I found the answer here

https://community.servicenow.com/community?id=community_question&sys_id=df78cfeddb1cdbc01dcaf3231f96...

If there are major changes to be modified in the scoped SN app then the best practice is to create a new scoped application and capture all the changes within that application scope. All the SN app artifacts can be inherited by creating a dependency with in your custom scoped app. This way you get the option to publish an app on multiple instances via "make the app available to other instances". On the other hand, if the changes are minor then you can create an update set in the same SN app scope and move the changes through the update set.