Deploy custom application to production

davidb2000 · ‎08-03-2016

With the help of this forum and the experts I have my first custom application ready to go to production.

Two questions:

What is the best way to deploy this application?
1. Publish to "My Instance"

or

2. Publish Applications to an Update Set

Is there a preferred method?

Pros and cons of each?

thanks,

David

Chuck Tomasi · ‎08-03-2016

Publishing:

Pros: Easy, simple, quick, publishes the entire app at once so you don't forget anything.

Cons: You may not want "everything" in your app to be published at a specific time (think of a sprint that has stories that are still in development and not ready for testing.)

Update sets

Pros: Able to publish smaller incremental changes with your app. E.g. Just the business rule that uses the new property rather than the whole app.

Cons: You have to remember to manage the update sets as you develop. E.g. Are you using Update set 1 or 2 when you make the mods?

View solution in original post

Chuck Tomasi · ‎08-03-2016

Publishing:

Pros: Easy, simple, quick, publishes the entire app at once so you don't forget anything.

Cons: You may not want "everything" in your app to be published at a specific time (think of a sprint that has stories that are still in development and not ready for testing.)

Update sets

Pros: Able to publish smaller incremental changes with your app. E.g. Just the business rule that uses the new property rather than the whole app.

Cons: You have to remember to manage the update sets as you develop. E.g. Are you using Update set 1 or 2 when you make the mods?

davidb2000 · ‎08-03-2016

Thanks Chuck - exactly what i was looking for.

Appreciate the help again

Bonnie Cresswe2 · ‎02-26-2018

Hi - let's say you are already live with ServiceNow, and you have a Dev, Test and Prod instance. You develop a new scoped app in Dev and publish it, then install it on Test. You find a few issues, fix on Dev, publish a new version, install that on Test, etc, until you are ready to go live with it in Prod. If you install the latest published app into Prod you then cannot develop it further from that install as it shows under Downloads not Develop in the Applications selector (which is awesome for Prod itself of course!), but what about now after a while we have it all settled and want to clone Prod back to Dev to refresh that and start on a new project. I guess we would now have an "installed" "published" scoped app on the Dev instance, as opposed to the original development copy. How can we continue to develop that scoped app? Am I missing something here, should we be doing it another way?

Bonnie Cresswe2 · ‎02-27-2018

All good - found this article: https://docs.servicenow.com/bundle/kingston-application-development/page/build/applications/task/preserve-applications-during-clone.html