Replace Catalog Item with Change Request Template

ZachOnNow
Tera Guru

Hello everyone,

I have a catalog item designed for requesting changes, which includes standard variables, two multi-row variable sets, catalog tasks, and a workflow. Recently, I've been exploring change management and am considering whether this catalog item should be converted into a change request template within the Change application, as its purpose is to manage changes.

However, I am facing challenges in understanding change request templates and ensuring they can accommodate the same variables and functionality as my current catalog item. Any advice or guidance on this matter would be greatly appreciated.

Thank you.

1 ACCEPTED SOLUTION

Hi @ZachOnNow 

 

In theory it is done by change team only , not by developer.  

 

In my previous account, there are 5 change teams and each team has dedicated user to create the change template including quality check/ information check and follow and make sure life cycle get completed on time. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

3 REPLIES 3

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @ZachOnNow 

 

Change and request are 2 different terms but looks similar in nature when it come to Standard change. We recommed end user to raise standard change ( in back end it is linked with template). Now the main catch for Request you can as many variable and other for change, we need to raise a proposal first and once proposal get approved, it become template and then we use.

 

I will not recommend to to change REQ to Change until unless you have a solid use case.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Thank you for your assistance! As I’m in the process of developing an application for the ServiceNow store, I’m curious about the typical practices. Is it common for application developers to create change templates, or is this task usually handled by the change management team within the individual company’s ServiceNow instance?

Hi @ZachOnNow 

 

In theory it is done by change team only , not by developer.  

 

In my previous account, there are 5 change teams and each team has dedicated user to create the change template including quality check/ information check and follow and make sure life cycle get completed on time. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************