First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Plan the Release of First-Generation Managed Packages
Remove Components from First-Generation Managed Packages
Delete Components from First-Generation Managed Packages
Modifying Custom Fields after a Package Is Released
Manage Versions of First-Generation Managed Packages
View Unused Components in a Managed Package
Push Package Upgrades to Subscribers
Push Upgrades
Push Upgrade Best Practices
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
Scheduling Push Upgrades
Enable a Package Subscriber to Restrict Push Upgrades
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Push Package Upgrades to Subscribers

A push upgrade is a method of automatically upgrading your customers to a newer version of your package. This feature can be used to ensure that all your customers are on the same or latest version of your package. You can push an upgrade to any number of organizations that have installed your managed package.

A package subscriber doesn’t need to do anything to receive the push upgrade. The only indication a subscriber receives after a successful push upgrade is that the package’s Version Number on the Package Detail page has a higher value. The developer initiating the push resolves upgrades that fail.

Use the Push Upgrade Exclusion List to exclude specific subscriber orgs from a push upgrade. You can specify up to 500 comma-separated org IDs.

Push upgrades minimize the potential risks and support costs of having multiple subscribers running different versions of your app. You can also automate many post-upgrade configuration steps, further simplifying the upgrade process for your customers.

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.