How to export form section and all content within it

[mkader]

Hello,

I am trying to export multiple ( 7 to be exact) form sections. I need to have them as a backup when I do my upgrade. How can I do this without missing any content within them? When I export the "Form Section", it misses the "Section Elements", "Form Section" related list, Sys UI Form, Sys UI Section, and form sections within that. So much and so confusing.

We do not have the "Add to Update Set" UI Action, and this is something that we are not looking at adding. 

Any ideas help thanks!

[Erik Stolberg]

a) If those items have been customized, ServiceNow will not overwrite during an upgrade. You should be able to test that with a sub-prod upgrade. If the files were updated for the upgrade, they will show in the Skipped list, and you will have to manually tell ServiceNow to overwrite your customizations.

b) Complex items like forms are not meant to be manually exported. The easiest way to capture a grouping of related items is to make updates while in an update set. That way, the system will store the XML update for you, and you can easily export all files at once.

c) You can easily capture changes in an update set if you know all the related files (you listed several). When viewing one record (like the Form Section), the related list tabs at the bottom will gather related files. You can select the checkbox in front of all files, then use the UI Action dropdown "Create Application File" to write the XMLs to the current update set. That might be easier than trying to manually "Export XML" for all files.

Still, the best method is to make sure to clone from Prod to a sub-prod instance, upgrade that, and verify the results. If something has changed, you should be able to find that file in production and move that back into sub-prod as needed. But ServiceNow doesn't overwrite customizations so there shouldn't be an issue anyways.

[mkader]

Thanks for your response. We are not doing a platform upgrade. It's really a migration from Agile 1.0 to Agile 2.0. One of the steps requires deleting all customization's. There is a utility that checks for Agile customization's and several form sections appeared. 

Also, not sure if you know the answer to this, but after migrating to 2.0, I was not able to get any of my burndown charts to actively work after converting teams to groups. There was another test step in documentation I found that asked implementers to test the functionality of closing stories in active sprints after the teams to group conversions. This did not work on burndown charts. It did however work on the Velocity chart