Ditch Update Sets for GitHub in ServiceNow (Part 2)

Good Practice

"When you create something in ServiceNow (that could be a catalog item, flow, playbook, etc.) think about creating it in an application. Stop using Global scope; stop using customized update sets... Pull yourself separately enough away from the OOTB. Yes, there are use cases for using the OOTB apps and customized update sets, but they are few. So, when you're creating think about first creating an app, and don't worry about creating an update set."

I agree that creating applications in ServiceNow is better than using global scope and customized update sets. Some reasons why I think so:

• It allows you to separate your customizations from the out-of-the-box functionality
• It enables you to use version control and branching for your changes
• It makes it easier to deploy and test your changes across different environments

So, create an app first. Link it to a source control platform. Then you can create branches for each configuration or customization in your application and commit the changes to the source control whenever you are ready.

What do you think? Do you have any tips or best practices for creating applications in ServiceNow?

Source