This video explains the benefits of using the standard change plugin. Standard changes are pre-approved, low-risk changes with a proven history of success that are logically grouped under specific categories. This video demonstrates how to submit standard change requests in the ServiceNow platform and how to propose and approve standard change templates.
Applies to ServiceNow releases starting with Geneva.
Roles required:
To submit a standard change request: itil or change_manager
To propose a standard change template: itil or change_manager
To approve standard change templates: change_manager
For best video quality, increase your player resolution to 1080p.
Excellent video - one note for customers upgrading to Geneva from previous releases.
The video suggests that the "Change Management - State Model" plugin is required, which isn't actually so.
We understand that changing your state model is a big deal, and so it is possible to use the new Standard Change functionality with your own change state model if you have done customisation work.
I don't think people have grasped how big this can actually be. For *years* there's been this strange grey area between Change and Request on ServiceNow, with Catalog Items typically winning due to its "easier" workflow and less rigid pathing when compared to Change.
Now all that goes out the window. A *HUGE* amount of what we used to think of only Catalog Items can now be routed through Standard Change processes.
It can change the whole way the system is deployed.
