Add change type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
In change_request normally we have 3 type of change Normal, Standard, Emergency so
4th type of change add is it possible.
There is any way to add or for this do customization as well as there is any another approaches to do.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @Vaibhav Ramteke ,
You can refer to the below article, which explains how to add a custom change type to the Change Request process and the approach to achieve this.
How to add new change type in change request main view
Hope this helps!
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Iftekhar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @Vaibhav Ramteke,
You can achieve this very easily; you just have to create a new template, which is given below:
Creating from here, you may be able to add any amount of template in your instance.
Let me know if it helps!! 😉
If you find my answer useful, please mark it as helpful and correct. 😊
Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
i want create all together 4th type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
20m ago
Being the Platform Owner, I’m happy to share my thoughts.
Adding a new Change Type is a simple configuration change and only takes a few seconds. However, making it mandatory introduces unnecessary complexity and could potentially be considered a bug or customization.
The reason is that Change Types should not be used as the sole basis for the Change process. If we build workflows, reports, and other functionality around Change Types, it can make the process harder to maintain when the Change Type needs to evolve.
Therefore, I would recommend not creating a new Change Type solely for this requirement. Instead, keep the existing Change Type and use the Change Model to drive the required process and workflow.
This approach is also more aligned with ITIL principles and avoids increasing technical debt.
I hope this helps you make a decision that meets the requirement without introducing unnecessary technical complexity.
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
******************************************************************************************