Managing Applications in different instances / clones

[huntj06]

My question is around creating a custom application within ServiceNow and moving it via Application Updates menu system before/after clones.

We have three instances. DEV--> UAT --> PROD

I've developed an application in DEV. Pushed it to UAT and PROD as one normally would. When the time comes for us to "clone over" our DEV/UAT instances, how do I manage the application? I'm assuming when I clone over into DEV, the instance will no longer see the application as being developed there as it was before the clone over.

[Chuck Tomasi]

Hi Jeffrey,

You're on the right track thinking about what needs to be done before and after a clone process to ensure you don't lose work. Short answer for your specific question, you shouldn't have issues with the application recognizing where it was developed after you clone.

This may be helpful: ServiceNow KB: Post-Cloning Checklist (KB0547597)

[bernyalvarado]

Hi Chuck,

I hope you're doing great! A couple of follow up questions on this one...

a) How will the application know which was the instance where it was developed? and... what will be the process if the development needs to continue from a different instance?

b) What are the best practices in regards managing the development of an application from multiple instances?

Thanks,

Berny

[Chuck Tomasi · Accepted solution]

Here's what I found.

Cloning and application development

Synopsis:

Best practice is to keep your development on one instance so the sys_app record remains intact.

Before cloning, export your apps to Git or update sets

Do the clone

Delete the local apps (because they are an imported copy from prod

Re-install the apps on dev.

[huntj06]

Doesn't anyone have an answer to @Berny Alvarado's question?

We're cloning at the end of this week and want to make sure I have all my bases covered..