custom application and updatesets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2024 05:31 PM - edited 02-14-2024 05:35 PM
Hello Everyone,
We have a custom application "App N" . when changes are made we publish the application via studio and install the app ver in production.
we have "App N ver" 1.0.6. installed in prod after that other developers created updatesets and these were deployed as part of the application scope "App N ".
- What can be done to have a new version of App N with all the changes deployed as update sets together as a new version.
- The application "App N" has various flows with endpoints (diff for prod and dev) .when we are going he route of publishing application how should the diff endpoints (Dev/Prod) be handled. Currently updatesets are created with prod endpoint on dev and deployed to Prod then immediately the endpoint is changed on dev .
Please advise.
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2024 07:13 PM
Hi @CV1
Deploying applications via Update Set is not a recommended practice. Instead, you could publish the application to application repository and install it on your prod instance through that. Refer https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_Publ...
Also, the information like endpoints which is configurable should be set to one or more system properties which could be tweaked as per the environment (Dev or Prod) and referred inside the flows.
Thanks & Regards
Amit Verma
Please mark this response as correct and helpful if it assisted you with your question.