How to transfer Standard Change Template from one instance to another

[Alex Ng]

Hi community,

Can anyone share with me on the procedures on how to import existing Standard Change Template from one instance to another? I want the existing Standard Change Template to be able to be selected from the Service Catalog.

Initially, I thought the Update Set will be able to migrate this together but apparently, I found some error about not able to find Standard Change Proposal Version record.

Therefore, if I were to do this manually via XML Export and Import, what are tables that I should be exporting/importing to make sure everything falls in place since I understand that, Standard Change Template created from record producer has workflows created?

Thank you.

[Dominik Simunek]

And regarding Standard Change Template Version - you might want to fix the numbers in there if you created some change requests for that version on sandbox - otherwise you move also the statistics that are not relevant for PROD. This is why it is not tracked in Update Set by default I guess. So maybe it would be possible to try to generate the versions dynamically on the target instance with clean data stats once Template and Producer are there. But that would require implementing a script for that.

[Alex Ng]

Hi Dominik,

Thank you for your prompt reply. It seems the easiest way would be to export to excel file and re-import back into the destination instance so that, it automatically runs the workflow and business rules through use of Transform Map as per topic Bulk load/import of standard change templates into new standard change catalog on Geneva?

I will use this method then. Thanks for your help!

[Dominik Simunek]

What records do you want to export/import via excel? If you want to have workflow started and just make standard change proposal process running, you should probably export/import only Standard Change Proposals but in a way they are in "New" state. Then you could request them and approve one-by-one. In such way they would be created as normal, you would just save time to entering all those template values.

[Alex Ng]

I am importing the Standard Change Proposal records. By setting the Type to New and Approval to Approved, it will trigger the workflow and automatically approve the proposal to create Standard Change Templates.

[SusanWinKY]

Hi Alex,

I prepared a spreadsheet for standard change proposals and tried importing it.  I got a message:  

The following fields have been ignored, because they don't exist on the destination table: Change Request values

My spreadsheet has a column named "Change Request values" with the following data:

short_description=MDM reboot 6 - Include a title for your change no greater than 100 characters^description=MDM reboot 6 - Describe what you plan to do - Weekly planned reboot during maintenance window^implementation_plan=MDM reboot 6 - List the steps in order of completion that will be worked through when implementing this change. Note who will perform each step and whether there are dependencies between steps.^backout_plan=MDM reboot 6 - Describe the steps you will take to revert the change to its pre-implementation state. At what point during the implementation will you take the decision to backout your change?   Does your change window include time to backout if you need to?^test_plan=MDM reboot 6 - Explain what testing you have done or will do prior to implementation that gives you confidence this change will be successful. Describe the tests that will be carried out after implementation to confirm that the change has been successful.^assignment_group=364bfb936f216100a70bff2f5d3ee4f2^justification=MDM reboot 6 - Weekly planned reboot during maintenance window^risk_impact_analysis=MDM reboot 6 - TBD^EQ

Do you have any advice on how to format the spreadsheet so that it will accept this data as the Change Request values? 

I am using the standard import process by right-clicking the list and selecting Import.  Kingston, patch 3.  Would appreciate any insight you can give.  Thanks!