First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Environment Hub
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
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
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

Newer Version Available

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

Sample Post Install Script for a Push Upgrade for First- and Second-Generation Managed Packages

Automate the assignment of new components to existing users of a package.

Post-install scripts can be used with first and second-generation managed packages only.

Note

For more information on writing a post-install Apex script, see Run Apex on Package Install/Upgrade.

In this sample script, the package upgrade contains new Visualforce pages and a new permission set that grants access to those pages. The script performs the following actions.

  • Gets the Id of the Visualforce pages in the old version of the package
  • Gets the permission sets that have access to those pages
  • Gets the list of profiles associated with these permission sets
  • Gets the list of users who have those profiles assigned
  • Assigns the permission set in the new package to those users