Change request implementation must be planned and scheduled carefully. It is very significant for a successful change implementation implementation. Also, planning and scheduling allow minimizing vital business functions disruption.
If the chosen time period overlaps another scheduled change implementation, it is recommended to minimize the effect caused to the multiple services or CI's at a time when implementing.
It is a good practice to follow the rule: One timeframe – one change request. |
Change Schedule helps to monitor scheduled changes and points out conflicts (overlapping implementations).
Change Schedule includes change request records in the following states: Authorization (approved and not defined), In Progress, and Scheduled. Change requests in other states and requests with denied approvals will not be displayed. |
To check out the planned changes, navigate to Change Enablement → Change Schedule.
Change Schedule consists of the following elements:
To open the Change Schedule, perform the following steps:
Unlike the page variant of the Change Schedule, this widget contains the following elements:
The current record is highlighted by blue color.
The start and end datetimes will be applied via the Change Schedule to the Planned Start Datetime and Planned End Datetime fields accordingly. To apply changes, click Save or Save and Exit. |
If the processes overlap, check information about the change requests by clicking on the titles. If the processes may affect each other and can't be implemented at the same time, reschedule them.