Second-Generation Managed Packaging Developer Guide
jNewer Version Available
Push a Package Upgrade for Second-Generation Managed Packages
Push upgrades enable you to upgrade second-generation managed packages installed in
subscriber orgs, without asking customers to install the upgrade themselves. You can choose
which orgs receive a push upgrade, what version the package is upgraded to, and when you want
the upgrade to occur. Push upgrades are helpful if you need to push a change for a hot bug
fix.
Use SOAP API to initiate the push upgrade, track the status of each job, and review error messages if any push upgrades fail. Here are the objects that help with push upgrades.
The push upgrade feature is only available to first- and second-generation managed packages that have passed the AppExchange security review. To enable push upgrades for your managed package, log a case with Salesforce Partner Support. For details on the security review process, see Pass the AppExchange Security Review in the ISVforce Guide.
| To Do This: | Use This Object: |
|---|---|
| Retrieve details about your package version. | MetadataPackageVersion SOAP API |
| Retrieve information about the subscriber org, such as the org ID and the package version currently installed. | PackageSubscriber SOAP API |
| Schedule a push upgrade, or check the status of the push upgrade. | PackagePushRequest SOAP API |
| Specify the org to receive the push upgrade. Create an individual package push job for every org receiving the push upgrade. | PackagePushJob SOAP API |
| Review any error messages associated with a push upgrade request. | PackagePushError SOAP API |
Push Upgrade Considerations for Second-Generation Managed Packages
- You can push upgrades to only packages that have passed AppExchange security review.
- The same manageability rules for package version upgrades are applicable to push upgrades.
- When a push upgrade is installed, the Apex in package is compiled.
- Push upgrades can be used even if the package version requires a password.