System Clone - Impact on scoped applications

[arjunalagar]

Hi All,

This seems to be a very silly question, but just need to understand is there impact of performing a clone on the dev instance with the production if we have scoped applications developed in the dev instance and deployed into the production instance via application migration. As i could see the applications which were developed in the dev instance is available for editing only in the instance in which it was created and not on the other instances where it has been migrated. Will this functionality gets impacted when we clone the production instance with the dev instance.

Also it would be helpful if someone could provide the best practices which needs to be followed while managing scoped applications.

Thanks & Regards,

Arjun 

[Mark Roethof · Accepted solution]

Hi there,

In theory, when you clone from production to your developer instance, it will copy the application version from your production environment over the application version that exists on your developer instance. It will become editable, but it will not have the draft version you might have been working on in your development environment.

So if you are not using source control:
Be sure your last changes to your scoped application, are published and on your production environment.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

[Christian Ander]

Hi Arjun and Mark,

There is a documented way to convert installed applications to development mode. This will solve your problem and you are not forced to perform a restore from backup.

Regards

Christian Andersson

[Bhanu Kiran]

https://docs.servicenow.com/bundle/jakarta-application-development/page/build/applications/task/pres...

As per the above doc, the cloning process does not preserve version differences for applications in development. Instead, the system clone only copies the application version installed on the source instance onto the target instance.

1. For e.g. the customer has a dev instance and there is an app developed with version 1.0.

2. Later they have made changes to this app with newer version 1.1 and it has been published to application repository.
3. But in Prod instance , they didn’t install the newer version of 1.1 and they have the older version 1.0 only.
4. So if the clone happened from Prod  to Dev then the Dev instance will be having the same version of Prod which is 1.0 and not 1.1 which is expected.
   5. We will only preserve the development state of the application on the target. For e.g. if the application in dev instance is under development state (1.2) and not published to application repository then we will preserve that state 1.2 while cloning.
   
   If the customer wants the latest version of the application (which was already published to repository) in development state on dev instance (even after cloning) then before the clone they need to have a backup of the newer version of the application taken from the dev instance by either using Source Control Integration or publish to Update Set. Then they can easily install that latest version from that backup, as described in the documentation Preserve unpublished applications during a system clone

If you don't have the backup anywhere, then you may need to restore the instance from a backup (i.e. rollback clone), take the backup of the application as described in the doc, repeat the clone and then install the app from the backup.

[Mark Roethof]

Hi there,

Did this solve your question? Or do we need to follow-up on this?

Please mark this answer as correct if it solves your question. This will help others who are looking for a similar solution. Also marking this answer as correct takes the post of the unsolved list.
Thanks.

Kind regards,
Mark

---

LinkedIn
Community article list