Anyone familiar with how the change "outside maintenance schedule" checkbox works?

[e_wilber]

There is a checkbox on the Change record "Outside schedule maintenance ".

I added this to the form to see when it actually gets checked and I can't find a scenario where it is. I've done this in two environments where one is completely OOB and the other has a slightly modified change process but I'm doubtful anything in this area has changed.

I created a maintenance schedule that applies to "cmdb_ci" with no conditions. My schedule entry is set from 6/7 to 6/7, repeats daily, repeats every 1 day and repeats until 6/30.

I created a new change record with a planned start and end date that falls directly in the middle of my maintenance window and select a CI. After saving the form, I click the CONFLICT checker and it says there are conflicts, just not the maintenance window I created. I have every single property under Conflict Properties checked.

Am I misunderstanding something? I added all the related screen shots below. I'm not sure why I'm not getting the checkbox to autocheck, the conflict checker to come back with my maintenance window conflict, or why I can't get this to show up as a red color on the change calendar.

[Chuck Tomasi]

Hi Eric,

I think I found what you are looking for. Take a look at the MaintenanceScheduleCalculator script include. That's the only place I found this field named on the whole system.

[e_wilber]

I was working through that script include yesterday. I'm looking at line 21 which was a little confusing to me because it's looking for a parameter checkType on the function call. If you look at the UI action that checks the change conflicts you'll see it referencing this script include but it's not passing a 2nd paramater to the SI at all.

I added a gs.log() test print on checkType within the function and it's coming back as undefined, which I half expected since I don't see where that's being injected into the script call. Then if you look at lines 47-59 or so you see this variable actually needs a value in it for something to happen and be returned.

Is there a bug in the original script include? Perhaps the UI action is supposed to pass a 2nd parameter?

[Chuck Tomasi]

Very bizarre. Don't know.

You've gone in deep! You could try passing your own checkType and follow it through to see if it starts setting the flag correctly. If it works, send it back in a HI ticket with a note "Here's your fixed script!" (just kidding, but a nice note to let the developers know there's an issue would be in order.)

[e_wilber]

Maybe I am going about this the wrong way. Do you know what has to be done in order for a change request to show up as red/crimson on the change schedule? That's what I'm trying to solve and lead me to dig into all of these scripts.

I thought it needed to be in conflict with a maintenance schedule to show up as red on the change schedule but I can't get that to work.