Ways to export custom code and configuration changes

cc11
Tera Contributor

I am looking for ways to query and export all changes made to my servicenow instance.

Example, any config changes such as new drop down values added to an out-of-the-box field.

OR, any code changes made to a form or scripts. 

Basically, I need to export in xml or csv or any readable format all changes made to my Kingston instance since it was vanilla.

Want to know if anybody has done anything like this.

 

Thank you.

 

1 ACCEPTED SOLUTION

Coleton
Kilo Guru

The 'sys_update_xml' table is your 'Customer Updates' table. I'd start there. Here's some documentation to further elaborate on why you would want to search that table for information regarding modifications to OOTB functionality.

View solution in original post

4 REPLIES 4

Coleton
Kilo Guru

The 'sys_update_xml' table is your 'Customer Updates' table. I'd start there. Here's some documentation to further elaborate on why you would want to search that table for information regarding modifications to OOTB functionality.

cc11
Tera Contributor

Thank you Coleton,

 

That's very helpful.

I will wait to close this thread for a day to see if somebody has any other approach and then mark is as Correct.

 

Thank you again!

 

sachin_namjoshi
Kilo Patron
Kilo Patron

All custom configuration code changes should be captured in update sets.I hope this was followed for your instance.

Best way is to export these export these update sets in XML and then you can import them back as per your requirements.

 

https://docs.servicenow.com/bundle/london-application-development/page/build/system-update-sets/task/t_SaveAnUpdateSetAsAnXMLFile.html

 

Also, you can export full custom scoped applications to repository (e.g github) 

https://docs.servicenow.com/bundle/london-application-development/page/build/applications/concept/c_SourceControlIntegration.html

https://docs.servicenow.com/bundle/london-application-development/page/build/applications/task/t_PublishApplicationsToAnUpdateSet.html

 

Regards,

Sachin

Thank you Sachin,

That's very helpful.

 

I forgot to mention that in our case the earlier developers have left the organization and there is no concrete documentation on how the changes were migrated to prod.

I am thinking, in that case @Celeton's comments may be used.

Once we implement a concrete process and document the changes, your solution is quite suitable.

I truly appreciate your answer.  Every input helps.

 

Thank you very much,

CC