Best practice to promote changes to higher instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 12:29 AM
Hello Community,
We developed one of the custom app using App engine studio in lower environment and looking for the way to promote changes to higher instance without activate app engine studio plugin in the higher instance.Is it possible to move through update sets ??
Thanks,
Steve An
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 12:47 AM
Hi @Steveanner ,
No need to capture in Update set, you have to install again with latest version in upper instance.
Plese refer the link: Re: When are pipelines necessary for moving betwee... - ServiceNow Community
Please mark helpful if it's helped your answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 12:59 AM
Hello Steveanner,
You can use application manager for publishing and then update version in higher instances:https://docs.servicenow.com/bundle/vancouver-application-development/page/build/applications/concept...
However if you want to use only update sets, I'll use batch method for this (also yo can update one by one the update sets without any problem): https://docs.servicenow.com/bundle/vancouver-application-development/page/build/system-update-sets/h...
☆ Community Rising Star 22, 23 & 24 ☆
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 01:14 AM
you can move the application between your instances via update sets.
But why not use App engine studio? any challenge in that?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 11:02 AM
Absolutely. No matter where you start building an Application (Native UI, Studio, AES) it is still just an Application. You have several options to move it into other instances without using AES/Pipelines. Many of those are already covered, so I'm just going to address your question around moving the application via update sets.
You can move the application via update set by navigating to the Custom Application record in the Native UI or in Studio. Here is one of the many methods you can use to get to that record and Publish the application to an Update Set. https://docs.servicenow.com/bundle/vancouver-application-development/page/build/applications/task/t_...