Backup before cloning

[gorleramapr]

We are experiencing an issue capturing our work in an update set. We need to back up a catalog item, flow, subflow, and decision table, but these were developed before an update set was created. Manual backups are an option, but we’re looking for a more efficient recommendation.

Note: We tried creating a new update set and making minor changes via the Catalog Builder, but the customizations are still not being captured."

Please suggest better approach for this asap.

[Dr Atul G- LNG]

That’s the only option we have. Alternatively, you could download the XML, but that won’t work properly as it will capture the current record at that point. You need to try again so that all changes are captured.

[Laveena-Agarwal]

Hi @gorleramapr 

You can use the "Add to Update Set" related link for this requirement. We had a similar use case where we needed to capture hundreds of catalog items.

With this approach, all catalog item–related components will be captured automatically, including:

• Variables
• Variable sets
• Catalog client scripts
• Any other elements available as related lists or fields within the catalog form

However, please note that any Flows or Script Includes referenced within your scripts will need to be captured separately.

To enable this functionality, install the update set available here:

https://developer.servicenow.com/connect.do#!/share/contents/9824957_add_to_update_set_utility?t=PRO...

Once installed , just click on this related link and yes it works like a butter😊