Upgrades

The user running the upgrade must be a System Administrator with the following assigned permission sets:

Compile all Apex codes before upgrading your environment(s) to ensure no issues exist that could cause the upgrade to fail. For more information, visit Salesforce's Apex Developer Guide.

Run all local (non-namespaced) unit tests. Although failing does not normally cause issues during an upgrade, it occasionally can. In addition, they can sometimes cause issues when deploying your own customizations to production. You are encouraged to follow Salesforce's best practices by running and monitoring unit tests.

Unschedule all Apex jobs prior to performing the upgrade and reschedule them after. If an upgrade modifies the scheduled class, this can cause failures in running jobs or, depending on the changes happening, deploy errors.

It is recommended that you perform upgrades when users are not in the system. The installation process can be long and happens in steps, thus users may encounter strange behaviors or errors during upgrades while components have mismatched versions.

Use Advanced Upgrade if you are upgrading to a version that is more than one version ahead of your current one. For example, if you are on version 11, use Advanced Upgrade to upgrade to version 13. Steps labeled Intermediate should only be run once. If restarting a failed upgrade, uncheck any Intermediate steps that have already ran. Failure to do so will not harm your org but the step will likely fail, requiring you to restart with the step unchecked.

When upgrading an org to version 13 from one that originally had Classic Medical Information Cloud in it, select one of the following steps: