Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Managed Packages
Components Available in Managed Packages
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Schedule a Push Upgrade Using SOAP API for First- and Second-Generation Managed Packages
Assign Access to New and Changed Features in First- and Second-Generation Managed Packages
Sample Post Install Script for a Push Upgrade for First- and Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in Second-Generation Managed Packages
Get Started with AppExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Newer Version Available

This content describes an older version of this product. View Latest

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 support case in the Salesforce Partner Community. 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.