- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The following are the states in Change Management in ServiceNow.
New, Assess, Authorize, Scheduled, Implement, Review, Closed
Is it recommended to create an automated CTASK under the Change Ticket for validating the change that is implemented? Already the lifecycle has "Review" state for the change to be reviewed and validated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
No, I’m not in favor of this change. The reason is that if you create a task in the Review state, you have to manually close it every time. The Review task should only be used when a change fails or is unsuccessful, so that you can perform the PIR and take corrective action.
Keeping tasks in Review for every type of change would create unnecessary overhead, so I would avoid that.
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
PIR is not a customization — it’s a configuration and works out of the box. When a change is marked as Emergency, the task is created automatically.
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************

