Normal Change Templates

[Ricky Singh]

Hello,

While I see there is ability to create standard change templates however the client is looking for the ability to create normal change templates which has the ability to create change tasks on the normal change.

I also see that out of the box while some forms have a related link called "Save as templates" like on the project form if you use that same related link user is able to store all values not only on the project form but also the project tasks as a template. However this is not available on the change form.

Do i need to custom create this or can i use something out of the box to develop the feature.

Thanks in Advance.

Ricky Singh

[Yousaf]

Hi Ricky,

Please refer to this article and see if this is what you need.

Normal Change Request Templates - How To

Mark Correct or Helpful if it helps.

[Ricky Singh]

Thanks Yousaf, this not quite what I am looking for. we are looking to empower the user so that they can create the normal change templates easily without involving the admin as per the product documentation 

Documentation shows that admin needs to create the normal change template and is also not very clear on how to associate the change tasks to the change template. Once the template is created it is easy to apply on the change form use the template toggle bar.

[Yousaf]

Hi Ricky, I misunderstood totally and it doesn't seem to be possible OOB. I am not sure if anyone has implemented this before.

if you did find the answer to that don't forget to post here please.

[Doug Julian]

I was doing some searching to see if there were any new solutions and came across this old post. Not sure if this will help but our account modified the Standard change template set up to allow for normal changes to be introduced into the catelog. This took a handfull of modificiations and we did this almost a year ago though I will try to give a breif example of what we did.

1) Standard Change Properties - Modified the properties to include the "Type" field as one of the dropdowns users can update. Also removed the Type field from the restricted list(s) Including screenshot as i dont have the original settings in front of me.

2) Modified the UI action on the change form to remove "standard" for clarity sake

when a user does the Propose a change template it uses the standard change template process to create the template and follows the all the same approval processes etc that a proposed standard change would

3) the last part depends on how you present your templates in your instance. We use the service catalog (customized to include standard, normal changes along with catalog items. 

when a template is selected, the Type is also filled in. Because of this the proper workflow (normal vs Standard) will be attached to the ticket when it is created. 

Im sure with more work this solution could be cleaned up further and bundled so it can be shared. Several things we didnt do but would help would be to rename the Module names in the navegator to remove "standard" from the naming as it now works for both Normal and Standard changes. Note that this will also work for Emergency changes if that applies to the individula use case though for us it did not. 

One last note we added several process steps to our ITSM processes for when reviewing proposals that the Type is verified and approved before a proposal can move forward and be published for use.