Choose a package version
Find the current Record Health Check release, install an exact package version, and plan how to
recover if a version must be reversed. Record Health Check is distributed as a Salesforce unlocked
package with the namespace rhc.
This documentation describes version 2.0.11, the current release.
| Release | Version number | Package version ID |
|---|---|---|
| Current | 2. | 04tak000000nGjZAAU |
| Previous | 2. | 04tak000000h2wDAAQ |
How Record Health Check versions work
Section titled “How Record Health Check versions work”Record Health Check is a second-generation unlocked package. Each released version has a version
number, such as 2.0.11.4, and a package version ID that begins with 04t. Salesforce never changes
a released version, so a given ID always installs the same contents.
The public installation links always open the latest released version:
| Org type | Installation link |
|---|---|
| Sandbox | Install in Sandbox |
| Production or Developer Edition | Install in Production |
Both links install the same version. They differ only in the Salesforce login domain they open.
The release registry in the Record Health Check repository
records the current version and its 04t ID under stable, and the previous release under
previous. The release notes describe what each version changed.
Find the installed version
Section titled “Find the installed version”- In Setup, enter
Installed Packagesin Quick Find, then select Installed Packages. - Find Record Health Check and read Version Number.
Install an exact version
Section titled “Install an exact version”Use an exact version ID when you install the same version in several orgs, such as a sandbox and then production, and need to be certain that each org receives identical contents.
-
Copy the
04tID of the version you want from the table at the top of this page, or from the release registry, where the current release isstable.subscriberPackageVersionId. -
Install it with the Salesforce CLI, replacing
PACKAGE_VERSION_IDandORG_ALIAS:Terminal window sf org display --target-org ORG_ALIASsf package install --package PACKAGE_VERSION_ID --target-org ORG_ALIAS --security-type AdminsOnly --wait 30 --publish-wait 10 --no-promptTo install in a browser instead, open
https://test.salesforce.com/packaging/installPackage.apexp?p0=PACKAGE_VERSION_IDfor a sandbox, or the same path onhttps://login.salesforce.comfor production, with your ID in place ofPACKAGE_VERSION_ID. -
Confirm the target org and version on the Salesforce installation page before you select Install.
If Record Health Check is already installed, follow Upgrade an installation instead. It includes the configuration backup and checks that an upgrade requires.
After installation, assign Permission Sets and add the card to a page as described in Install Record Health Check in a sandbox.
Plan recovery from a version
Section titled “Plan recovery from a version”You cannot rely on installing a lower version over a higher one. Salesforce package upgrade rules do not support downgrading an unlocked package in place. Test every version change in a sandbox that represents production before you install it in production.
| Situation | Recovery path |
|---|---|
| A new org needs a specific version | Install that version’s 04t ID. |
| An upgrade failed testing and has not reached production | Stop the rollout. Production stays on its current version. |
| An installed upgrade causes a problem | Keep your Check Sets and Checks, and install a later corrective version after it passes sandbox testing. |
| The package must be removed | Follow Uninstall Record Health Check. To return to an earlier version, reinstall that version afterward and restore your configuration from a backup. |
Back up the Check Sets and Checks your organization created, and record which Lightning pages use them, before any upgrade or uninstall. See Back up and restore configuration.