Configure change window

Anubhav Srivas1
Tera Expert

Hello Experts,

I need to configure a change window like the attached image. I'm new to this. Please help me out.

Thanks in Advance!

1 ACCEPTED SOLUTION

Hey,

Maintenance windows don't prevent the change from being logged, they just highlight to the change scheduler that they have scheduled it outside of the maintenance window. If the window is configured correctly, a 'Conflict detected' message will popup when they save the Change.

I generally suggest adopting OOTB here and not implementing logic to prevent the Change from being scheduled. Why do I say this?

In my view, it is better to know about Changes that are happening outside of hours than to have people subverting the Change process entirely and not logging changes when they want to do them outside of hours. That's the behaviour that is encouraged by preventing them from logging Changes - people will just stop logging Changes that they want to do outside of hours. Introducing behaviour that discourages Change logging is probably the worst thing you can do to that process.

If you must proceed, you could build checks into the ChangeRequestStateModel Script Includes to enforce this by looking at the Conflict State field.


ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

View solution in original post

7 REPLIES 7

I'd use ServiceNow's Maintenance Window functionality to determine valid change windows.

Instructions in the provided link.


ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

I have created the maintenance schedule but still i'm able to create change in odd hours.

How to stop that?

Hey,

Maintenance windows don't prevent the change from being logged, they just highlight to the change scheduler that they have scheduled it outside of the maintenance window. If the window is configured correctly, a 'Conflict detected' message will popup when they save the Change.

I generally suggest adopting OOTB here and not implementing logic to prevent the Change from being scheduled. Why do I say this?

In my view, it is better to know about Changes that are happening outside of hours than to have people subverting the Change process entirely and not logging changes when they want to do them outside of hours. That's the behaviour that is encouraged by preventing them from logging Changes - people will just stop logging Changes that they want to do outside of hours. Introducing behaviour that discourages Change logging is probably the worst thing you can do to that process.

If you must proceed, you could build checks into the ChangeRequestStateModel Script Includes to enforce this by looking at the Conflict State field.


ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022