Hi @MUNIL 

May you use Application Repository 

https://www.servicenow.com/community/app-engine-blog/application-repository/ba-p/3397353

https://www.servicenow.com/community/developer-blog/update-sets-vs-application-repository/ba-p/32572...

Hi MUNIL — welcome to the Community! For a scoped application, the Application Repository is the way to go (as Rafael pointed out). Here is how it works in practice:

1. In your dev instance, open Studio, open the Alpha application and publish it to the Application Repository. This uploads the application with all its files, tables, scripts and dependencies.

2. On the target instance (test or prod), go to All > System Applications > My Company Applications, find Alpha in the repository and install it. The target instance needs the same plugins or dependencies the app relies on, so install those first if they are missing.

3. For later changes, publish a new version from dev and upgrade it on the target — the repository keeps the version history, so you can roll back if a version has a problem.

Update sets can move a scoped app too — capture the app in a completed update set and import it on the target — but they are easy to get wrong for scoped apps, because a missed record means a broken app. The repository is the safer, repeatable route for promoting between environments.

One caution: do not move it by cloning the instance or by exporting XML — that is not a supported promotion path for applications.

If this helped, please mark it as Helpful — and if it solved your issue, I'd be grateful if you accepted it as the solution.

Hi @MUNIL, 

Which route you take depends on the target instance.

Application Repository works when both instances belong to the same company, so dev to test to prod inside your own org. You publish from dev, then on the target go to System Applications > All Available Applications > All and install it from there.

If the target sits outside that company, or it’s a PDI, use Publish to Update Set instead. Open System Applications > My Company Applications, open your app, and click Publish to Update Set in Related Links. That creates a completed update set holding every file in the app. Export it as XML from there and import it on the target like any other update set.

Thanks

There are multiple ways to deploy a scoped application to a target instance:

• Publish the application to an update set (Official documentation)
• Publish the application to the application repository (Official documentation)
• Use the OOTB available Git integration (Official documentation)
• Use the Now SDK for both development and deployment (Official documentation)
• There is an OOTB available application for this purpose, called ReleaseOps (Official documentation)

I have already used all of these solutions, and I would say that selecting the right approach heavily depends on the development team's maturity level.

The simplest way is the "publish to update set" approach. Based on what you wrote, I would recommend this one.

Using the application repository is also a good option, but you need to understand how it works, how you can deploy the app. This approach is not as flexible as using update sets (e.g. managing hot fixes).

The best thing you can do to start with the following training: Application Development Fundamentals

Hi @MUNIL 

I would advise you to utilize the build in application repository for custom applications.