Update Sets Vs Application Repository

[dipak_thakor]

As part of Technical governance, we need to understand when to use Update Sets Vs Application Repository, so we can plan the update process any avoid any common mistakes.

ServiceNow Application Repository

The ServiceNow Application Repository is a central location for all scoped applications that are published by all ServiceNow customers. After you develop and test a custom application, you can make the application available to company instances by publishing it to this repository.

System Update Sets

An update set is a group of configuration changes that can be moved from one instance to another. This feature enables administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.

When to use Update Sets:

So when to use update sets?

Good For	Future Considerations
Storing changes to a base system or installed application. Storing and applying a particular version of an application. Producing a file for export.	You can manually create update sets to store a particular application version. Use update sets to deploy patches or changes to installed applications. Note: Don’t use update sets to install applications. Instead, use the application repository or the ServiceNow Store to install applications.

When to use Application Repository:

So when to use the Application Repository?

Good For	Future Considerations
Installing and updating applications on all company instances. Automatically managing application update sets. Restricting access to applications to the same company. Deploying completed applications to end users.	Consider uploading an application to the ServiceNow Store to share it with other users. Allows installation of and update to the latest application version only. Use update sets to store prior application versions. Note: If used with team development, publish applications only from a parent instance.