System Clone - Impact on scoped applications

arjunalagar
Kilo Contributor

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 

1 ACCEPTED SOLUTION

Mark Roethof
Tera Patron
Tera Patron

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

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

View solution in original post

6 REPLIES 6

Mark Roethof
Tera Patron
Tera Patron

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

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

CMDB Whisperer
Mega Sage
Mega Sage

What I'm not clear on here is how this affects the source control integration.  Let me explain the scenario:

 

  • MyApp has been developed in Dev and linked to Source Control.  It is in the Custom Application [sys_app] table in Dev.
  • MyApp 1.0 has been updated in Source Control and published to Prod via the Application Repository.  It is stored in the Store Application [sys_store_app] table.
  • Prod is then cloned down to Dev, so Dev has the Store App record.  Not only have we lost any updates we did since 1.0, but we have also lost the Source Control link, right?  So after we convert back to Development mode, is there a way to maintain the link to Source Control that we had before we cloned?  I'm guessing that the Repository Config should still be valid since the app record is still the same, it has has been reclassified.  Testing this theory now, but I have heard anecdotally that it doesn't work and that you cannot relink an existing app to the same source control.  Anyone experienced issues with this?

The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.