Scheduling a Change Request via the Change Catalog
Administrators can schedule Change Requests via Change Catalog Items (CCIs), which allows standard changes to run on their own with a defined cadence.
Go to Service Desk > Changes. The All Changes Index page opens.
All scheduled change requests have a Scheduled tab at the bottom. (Administrators can update scheduled change requests directly from this page).
Notice the fields for Planned Start and Planned End dates above the area where changes are scheduled.
The scheduled date is the date the request is submitted. The planned start/planned end date is the number of days after the scheduled date, which is when the change is executed.
For example, a change is requested on Friday, November 20 is not executed on this date because the planned start/planned end date is 3 days. This means that the change is executed (implemented) 3 days after November 20; that is, Monday, November 23.
Benefits and Use Cases
Scheduled CCIs allow customers to automate scheduled standard changes to occur without human intervention.
As a result, customers can automatically run change requests that need to be carried out on a regular basis. This includes the following use cases:
- A change runs every month to check for backups on all servers.
- A change runs every six months to check license counts on all SaaS software. This can help ensure licenses are not exceeded and identify whether the number of licenses can be reduced.