Cloning with Scoped Applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2015 12:02 PM
Hi all,
Apologies if this seems like a n00b question but we are nervous about what to do!
We have been experimenting with developing Scoped Applications in ServiceNow but we have reached a point where we may have developed too much to lose if we have misunderstood how developing scoped applications works.
We have developed 90% of a scoped application in our development instance (Dev) and have published the scoped app to the repository. We now need to arrange a clone to reset Dev as some prototype work outside of the work done for the scoped application has been done and caused a few issues. We are hesitant to do so in case we lose any of the work we have done and if we lose the ability to continue to develop the remaining requirements within the application.
So my questions are:
What happens to scoped applications if we are to clone the environment that it was created in:
1. After it has been published to the application repository?
2. Before it has been published to the application repository?
Thanks for any help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2016 04:01 PM
Hi Graham. We are going to be facing a similar problem to what you describe above. What did you eventually end up doing for your clones?
Thanks,
Sid Sonrexa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2016 03:05 PM
Hi Sid,
The answers to my questions were:
1. It saves the work to the respository where you are then able to retrieve that application and continue to work on.
2. If you have not uploaded the work to the repository, the clone will delete it all.
What happened to us though was we published the application to the repository which we then tried to retrieve following the clone, however we did have an issue where the clone removed the associated sys_app record for the application from the environment. This meant that when we tried putting the app back on our development environment it could not identify that the app belonged to it so wouldnt allow you to then edit it. We managed to retrieve this via a backup that ServiceNow pushed to our Dev instance for us.
We have not used scoped applications since even though ServiceNow have said that the issues with the cloning engine have since been resolved. Instead we now continue to do development work in update sets within the Global application. I'm sure we will look at scoped applications in the future but we will wait until we have completed the application developers training course.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2016 03:17 PM
That helps. Much appreciated Graham!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2019 09:07 AM
HI,
we did the same, worked on scoped apps and the promoted to application repository. Before the clone, I created an update set as a a backup. After the clone, I deleted the scoped app from development and then restore the update set, that brought the development instance back again.
But, but for the rest of scoped apps we are using now update sets to avoid precisely deleting and restoring in the development environment after cloning it.