What is best practice to move a scoped application to another instance without update sets

[Raviteja Kunal1]

What is the best practice to move a scoped application from one instance to another without using update sets? Is it doable?

[Community Alums · Accepted solution]

Hi @Raviteja Kunal1 ,

Part of the beauty of scoped app is that you DON'T need update sets to move data between your instances. Use the Publish/Install feature and forget about it.

If you are providing this to another instance outside of your organization, then that's an exception because Publish only works between YOUR instances. If you were to ask for a copy of my Safety app that I wrote on my Personal Developer instance or another instance that I have to talks to our repo, the only way I can get that to you is to give you an update set. 

I wouldn't bother using update sets in scoped apps. There's really no point. I would rather use source control to drop tags on the main branch to mark releases/sprints, etc. and then if needed, create a branch from that tag.

But ideally, if you are using update sets, then use these links :https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_Publ...

[AndersBGS]

Hi @Raviteja Kunal1 ,

Have you verified the KB article which refers the same: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293?

According to bullet 3: you should do it via "Publish an application to the application repository".

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

Best regards

Anders

[Community Alums · Accepted solution]

Hi @Raviteja Kunal1 ,

Part of the beauty of scoped app is that you DON'T need update sets to move data between your instances. Use the Publish/Install feature and forget about it.

If you are providing this to another instance outside of your organization, then that's an exception because Publish only works between YOUR instances. If you were to ask for a copy of my Safety app that I wrote on my Personal Developer instance or another instance that I have to talks to our repo, the only way I can get that to you is to give you an update set. 

I wouldn't bother using update sets in scoped apps. There's really no point. I would rather use source control to drop tags on the main branch to mark releases/sprints, etc. and then if needed, create a branch from that tag.

But ideally, if you are using update sets, then use these links :https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_Publ...

[AndersBGS · Accepted solution]

Hi  @Raviteja Kunal1 ,

Just posting a snip of the KB, and have also posted the correct link - I unfortunately made a typo in the previous link:

Furthermore, try this link instead - this should work: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

Best regards

Anders

[Community Alums]

@AndersBGS  But this link works in my answer :https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293