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.

[Alex Ng]

Hi Nayan,

Got it done through the easy way of doing export/import via excel file instead as per topic Bulk load/import of standard change templates into new standard change catalog on Geneva?

Thank you for your prompt response and help!

[nayanawadhiya1]

Great I am glad you got the answer.

[Dominik Simunek]

Hi Alex,

Similar question was raised here: Is it possible to migrate Standard Change Catalog Templates through an update set?

Update set will move the Standard Change Template and Standard Change Producer and as I have tested, this could suffice to be able to create the standard change requests (I deleted template version and proposal on my instance and it was still working). However missing Standard Change Template Version means you won't have those statistics about success rate of that version, so I would try to move that one as well. The proposal is not probably needed at all.

However what is the reason for moving standard change template between instances?

Thanks,

Dominik

[Alex Ng]

Hi Dominik,

I have a number of Standard Change Templates that I would like to transfer from sandbox to production. I understand that, normally, a Standard Change Proposal goes through a workflow from Standard Change Producer upon submission. Only when it is approved, it will generate records in Standard Change Template and Standard Change Template Version. Do correct me if I am wrong.

In this case, I noticed only the records from my Standard Change Template table is appearing after I committed my update set. The rest of the records from the relevant tables is not even captured. Is there any way that I migrate these templates from sandbox to production without going through the manual process of creating them one by one on Production?

Thank you.

[Dominik Simunek]

Hi Alex,

Also Standard Change Template Value (std_change_record_producer) was not moved by update set? That one is captured by update sets so you should have it there. Also the relationships to catalog and category. Then I would suggest to export/import at least the Standard Change Template Version record and possibly also the Standard Change Proposal (but I would try it firstly without it) - here it is necessary to check what happens with workflow so that it is not started again on target instance.

I recommend to try the process to other instance than PROD. So try to migrate the update set and export/import records to DEV from Sandbox and try how that works. It would be great if you can then share your findings here 🙂

Best regards,

Dominik