Upgrade to the Australia release
Upgrading and patching your instance requires planning, testing, and validation. To ensure a safe and effective upgrade, read the release notes, create upgrade plans, and test your upgrade on non-production instances before upgrading your production instance.
Important: These topics contain in-depth explanations about upgrades. For a step-by-step reference of upgrade steps, refer to the Upgrade planning checklist.
Image omitted: phase1-book.png Release notes | Before you begin the upgrade process, it is essential to read the release notes for your target version so you understand the required upgrade and migration tasks. This information helps you plan a safe and effective upgrade. |
Image omitted: phase2-checklist.png Upgrade checklist | For a better understanding of your production upgrade duration, request a full clone of your production instance (including large tables and attachments) onto a non-production instance. Confirm your current and target release versions, because you will later use this information when scheduling your upgrade in Now Support. |
Image omitted: phase3-calendar.png Calendar with an upgrade date | Check the configuration of the Check distribution for possible upgrade scheduled job to view how often and when it runs. Review information about timing your upgrade in coordination with the Check distribution for possible upgrade scheduled job. Then, schedule your upgrade in Now Support. |
Image omitted: phase4-upgrade-progress-checkmark.png Upgrade progress screen | Track the progress of your upgrades with the Upgrade Monitor. For your first non-production instance upgrade (your development instance), use the Upgrade Monitor to process the skipped list of records that were not addressed in the upgrade. Then identify your update sets and perform functional testing. |
Image omitted: phase5-recursive-arrow.png Upgrade other instances | After you've configured and refined your development instance, request to upgrade any other non-production instances you have, such as a test instance. Immediately after the upgrade is complete, apply the post-upgrade changes made to your development instance, including activating optional plugins, installing and upgrading applications, and applying update sets. |
Image omitted: phase2-checklist.png Upgrade checklist | After you have configured and refined your test environment to be a good representation of your production environment, prepare to upgrade your production instance. |
Image omitted: phase4-upgrade-progress-checkmark.png Upgrade progress screen | After you have upgraded your development, non-production, and test instances, upgrade your production instance last. Then validate that the upgrade was complete, apply update sets and fix scripts, and perform post-upgrade user acceptance testing (UAT). |