Major Update Schedules Overview

The major update schedule page enables administrators to review the available major release updates for their production and sandbox orgs. They can select an update that will best suit their business model and working practices. This means administrators can choose an update that won't coincide with other business critical activities they might already have scheduled.

The major update schedules can be accessed from the System Administration Workspace by clicking the Major Update Schedules link.

The Major Update Schedules window provides excellent visibility of the update choices you make and the dates your orgs are scheduled to update.

You are able to view the update schedules in a calendar format for the current year and the following year by selecting the appropriate year tab at the top of the schedules window.

Update Schedules

There are four update schedules available for each of the following major updates:

  • Winter
  • Spring
  • Summer

You are required to select one update schedule for each of the major releases you wish to update.

The following information is displayed on each schedule calendar card:

Information

Description

Schedule number The number of the schedule between 1 and 4 in the major release representing each of the 4 months where that major release can be scheduled.
Date The month and day the production org will be updated.
Sandbox: The month and day the sandboxes associated with the production org will be updated.
Schedule status The current status of the update schedule.

Schedule Details

A schedule details section on the right side of the major update schedule window provides the details of the production org and associated sandbox orgs available for the update schedule. The production org and each of the listed sandboxes have a toggle switch adjacent to them. Only the production org toggle switch is active when an update schedule is selected. Once an update schedule is selected, and the production org switch is toggled, the following will happen:

  • The schedule status will update to Selected.
  • The remaining schedules for the release will update from Available to Unavailable.
  • The production org toggle switch will turn from grey to blue with a white tick.
  • The associated sandbox org toggle switches become active for schedule update selection.
Note:

Toggling a sandbox switch after it has become active will select that sandbox for the update schedule as well as the production org.

Schedule Statuses

The status of each schedule is displayed at the bottom of each schedule calendar card. The status of each schedule will change as major updates become available and when schedules are selected. The statuses are as follows:

  • Unavailable
  • Available
  • Pending
  • Scheduled
  • In Progress
  • Updated

Unavailable

An update calendar card has a status of Unavailable when any of the following conditions exist:

  • The release schedule has not yet been determined by Certinia.
  • The current date is later than the production date of the schedule.
  • Another schedule in the same major release is already selected.

Available

An update calendar card has a status of Available when all of the following conditions exist:

  • The release schedule has been determined by Certinia.
  • The current date is before the production date of the schedule.
  • No other schedule in the same major release is selected.

When you hover over an update calendar card, its border turns from grey to blue.

When you click the calendar update card, a blue triangle with a white tick appears in the top right corner of the card and the related information displays in the schedule details adjacent to the card. The production org and associated sandbox orgs display in the Schedule Details section. The production and sandbox orgs have a toggle switch to control update selection for each update schedule.

When you click the calendar update card, a blue triangle with a white tick appears in the top right corner of the card and the related information displays in the schedule details adjacent to the update schedule tiles.

Pending

A calendar update card has a status of Pending when the request to assign the update schedule is being processed. The pending status exists from when the request is made to assign the update schedule until the update schedule data is synchronized with the Certinia back office system. An update schedule with a status of Pending cannot be edited as doing so might result in record duplication. You will be able to modify the update schedule if required once its status updates to Scheduled. For more information on the data flow between the Certinia back office system and the update scheduler see Object Field Data Flow Between the Certinia Back Office System and Update Schedules.

Scheduled

A calendar update card has a status of Scheduled when an available schedule is selected and the request is assigned. The scheduled details section lists the production org and the associated sandboxes that will be updated. There is an option to change the currently assigned schedule update up to 48 hours before the update is scheduled to start.

In Progress

An update tile has a status of In Progress when the update has commenced and is progressing. This status will remain until the update has completed successfully.

Updated

A calendar update card has a status of Updated when its status was scheduled and the update has completed successfully. The schedule details section lists the production org and the associated sandbox orgs that have updated successfully.

Tracking Changes

You can see when changes are made to the Schedule Details component of the major update schedules window. The Last Date Choice Submitted is the date the selected schedule last changed. The Last Scheduled By field displays the user who last changed the selected schedule.

Schedule Selection Limitations

We advise that you make your update schedule choice for each release in good time. You will be unable to make any changes to an update schedule within 48 hours of when the update is due to commence. This is to ensure data is synchronized between the Certinia back office system and your org Update Scheduler, and there is sufficient time to run essential checks before the update starts.