Planned Start/End Date Change at Authorize

[Sameer7]

I have had a few instances where the planned start and end date change after passing through Authorize (our CAB). 

I am curious if others run into these situations and does your change workflow return the change to the assess stage? I would assume this is a workflow change?

[Michael Fry1]

That's why those fields should become read-only if the State isn't New. Your approvers are approving the CHG based on the CIs, schedule, etc. You shouldn't have the ability to change the schedule without going back through approvals.

[Sameer7]

Thanks Michael,

In our instance, the planned start/end date can be updated but only by the CAB coordinator and these situations happen in our environment. I guess I would then need to update the workflow to send the stage back to assess right?

[Michael Fry1 · Accepted solution]

Depending on CHG type, but out of the box there is UI action: Revert to New, that will take the change back to a New state. From there you can make changes and resubmit for approval.

[Sameer7]

Thanks Michael.

The UI action is active, however it does not move the change back to New after Authorize. The script is

revertToNew(current);
action.setRedirectURL(current);

function revertToNew(changeRequestGr) {
var changeRequest = new ChangeRequest(changeRequestGr);
if (!changeRequest.revertToNew())
gs.addErrorMessage(gs.getMessage('State Model for {0} changes does not allow reverting change from {1} state', [changeRequest.getValue('type'), changeRequest.getDisplayValue('state')]));
}

The condition is

gs.hasRole('itil') && ((current.type == ChangeRequest.EMERGENCY && new ChangeRequest(current).isAuthorize()) || (current.type == ChangeRequest.NORMAL && new ChangeRequest(current).isAssess()))