Application Repository Self Hosted

After you develop and test a custom application, you can make the application available to company instances by publishing it to the ServiceNow application repository.

After installing the application repository, you must configure it using the following procedure.

When your applications are placed in the Custom Applications table [sys_app], you can't upgrade them directly through the Application Repository. This procedure helps you do a one-time conversion when you want to migrate deploying your applications using the Application Repository.

Convert the installed applications that your company owns to development mode after you install an application onto a non-production instance to use for development or clone a production instance into a non-production instance for development. With this conversion, you enable newer versions of the application to be created, committed, and published.

Delete an application from the application repository so that it's no longer available to your company instances.

Install your application on an instance so that employees can start using the application that you developed.

Because self-hosted, air-gapped customers don't allow their instances to communicate with external networks, they don’t install the Application Repository directly from the ServiceNow Store. These customers should use the following procedure instead.

Install a customization of a store application from the Application Repository to your instance.

Add or remove application entitlements to limit which instances the application can be installed on.

Learn how to manage the applications you publish to the ServiceNow application repository.

You can manage your company's customizations for applications that belong to other organizations or a scoped ServiceNow plug-in.

This application feature enables self-hosted customers to use their own internal application repository just as cloud customers do. These customers don’t install the Application Repository via the ServiceNow Store; they use an alternative method.

Manually preserve a copy of each application and customization that you currently have in development before you can clone the application version to the target (development) instance.

After you have designed, developed, and successfully tested your customizations to a store application or a scoped plugin, you can publish it to the ServiceNow application repository to share it to other instances in your company.

Release a scope from the application repository so that the scope can be used to create new scoped applications.

Publish a custom application to the application repository so that it can be installed on other instances in your organization.

The results to expect post cloning for application customization display the expected behaviors based on the state of the application, and the actions to recover your application customizations.