How to avoid wiping in progress update sets during clone process

Daemyian
Tera Expert

‎06-22-2021 05:30 AM

Hello,

Quick question cloning form production to Dev. What's the best way to avoid wiping out existing update set that are in progress during cloning instance from production to dev instance? The clone profile states it will wipe out in-progress update sets and flagged a warning when cloning.

Can I just set the update sets in DEV to complete and then process clone. What's the best approach to avoid wiping out update set. 

 

Thanks,

Daemyian

0 Helpfuls
  • 2,871 Views
9 REPLIES 9

jrcamposanto
Tera Contributor

‎06-22-2021 05:40 AM

Starting in Orlando, you can use the "Preserve In Progress Update Sets" option during cloning and this will keep your open Update Sets after the clone. See https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827916.

Prior to Orlando, if we need to clone and keep the open Update Sets, we complete those Update Sets and export them as XML (including any other data related to the ongoing development). After the clone, we will import them back.

Gaurav Shirsat
Mega Sage

‎06-22-2021 05:50 AM

Hello

Preserve in progress update sets is now available. A new setting for clones is a checkbox that allows you to select to preserve any in-progress update sets from the last 90 days in the target instance.

refer docs

Preserve Update Sets

https://community.servicenow.com/community?id=community_question&sys_id=ff1b6c82db7edc106621d9d96896...

Please Mark Correct and Helpful
Thanks and Regards
Gaurav Shirsat

T_Bridge
Kilo Contributor
In response to Gaurav Shirsat

‎06-22-2021 06:24 AM

be careful - this "in progress update set" counts only for Global application, thus no scoped applications. It's only half useful. Therefore - although kinda cool, I think the default behaviour should be to save the update sets as we do today