Is it possible to migrate Standard Change Catalog Templates through an update set?

[Shant Cancik]

I tried to do it between two ServiceNow instances and the names of the templates did migrate over to the correct categories but no information within them came along. Clicking on any of them just opens a blank change request form (no values entered for the fields)

Anyone have any idea as to what I'm doing wrong? Or if this is even possible to do?

Thanks!

[Dominik Simunek]

Hi Shant,

When approving a standard change proposal several records should be kept in update set - especially "Standard Change Template" and "Standard Change Template Value" - these are the template itself and the second one is the standard change producer that you then see in the catalog.

I guess it should work when having only these two records available. However I would recommend not to move Standard Change Template through update set as still some records are not tracked via update set - especially "Standard Change Proposal" and "Standard Change Template Version" - these are useful to track success rate of change requests for that template version.

So from my point of view, Standard Change Templates are more like "process" data that should be managed in production instance compared to configuration data that are managed on dev instances.

Best regards,

Dominik

[Dominik Simunek]

Check out this thread: Bulk load/import of standard change templates into new standard change catalog on Geneva? Jason has experience and described how he did it successfully.