Can you hide the OOTB Change templates?

Martyn_Fearn

We have created a number of our own Change Templates and want to make these the only ones available when creating a new change request.

I have gone through our various User Roles and removed the OOTB templates from the scope but for some reason they are still showing up.

Is there some other way to hide them ?

Tom_Hendricks

It is possible to delete them from the console or to export, edit, and re-import the MP that they are contained within (it is unsealed): ServiceManager.ChangeManagement.Configuration.xml.  This is not the same as hiding, of course, but it is an option that may work for you, if you do not need other roles to see them.

If you do not like the idea of deleting the templates completely, you can store them outside of Service Manager.  One way (aside from keeping a copy of the XML in a file somewhere) is to use VSAE (Authoring Extensions to Visual Studio) to manage your MP edits in TFS.  Then you can comment out (enclose in <!-- and --> tags) those templates in your MP fragment, instead of deleting them.  The resulting XML that gets deployed to SCSM won't contain them, but your commented-out templates will always be there in TFS if you need to refer to it later or add them back in by un-commenting them and re-deploying.

Conner_Wood

If this is solvable for the Cireson Portal, same goes for the "Default Service Request" template that Microsoft foolishly sealed in a core functionality management pack.  They did bad and should feel bad.

Tom_Hendricks

It is possible to delete them from the console or to export, edit, and re-import the MP that they are contained within (it is unsealed): ServiceManager.ChangeManagement.Configuration.xml.  This is not the same as hiding, of course, but it is an option that may work for you, if you do not need other roles to see them.

If you do not like the idea of deleting the templates completely, you can store them outside of Service Manager.  One way (aside from keeping a copy of the XML in a file somewhere) is to use VSAE (Authoring Extensions to Visual Studio) to manage your MP edits in TFS.  Then you can comment out (enclose in <!-- and --> tags) those templates in your MP fragment, instead of deleting them.  The resulting XML that gets deployed to SCSM won't contain them, but your commented-out templates will always be there in TFS if you need to refer to it later or add them back in by un-commenting them and re-deploying.

Tom_Hendricks

I should add that this will not remove the Publish Offering template, which lives in a different sealed MP, but will take care of the others.