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
What Are Beta Versions of Managed Packages?
Create a Beta Package for First-Generation Managed Packages
Create and Upload a First-Generation Managed Package
Publish Extensions to Managed Packages
View Package Details in First-Generation Managed Packages
Notifications for Package Errors
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
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

Create a First-Generation Managed Package Using a UI

If your goal is to build an app and distribute it on AppExchange, you use managed packages to do both. Packaging is the container that you fill with metadata, and it holds the set of related features, customizations, and schema that make up your app. A package can include many different metadata components, and you can package a single component, an app, or library.

Building a new app? Have you considered using second-generation managed packages? Flexible versioning and the ability to share a namespace across packages are just two reasons why developers love creating second-generation managed packages. We think you’d love it, too. To learn more, see: Why Switch to Second-Generation Managed Packages, and Comparison of First- and Second-Generation Managed Packages.

Note


User Permissions Needed
To create packages: Create AppExchange Packages
  1. From Setup, in the Quick Find box, enter Package Manager, and then select Package Manager.
  2. Click New.
  3. Enter a name for your package. You can use a different name than what appears on AppExchange.
  4. From the dropdown menu, select the default language of all component labels in the package.
  5. (Optional) Choose a custom link from the Configure Custom Link field to display configuration information to installers of your app. You can select a predefined custom link to a URL that you’ve created for your home page layouts; see the Configure Option. The custom link appears as a Configure link within Salesforce on AppExchange Downloads page and app detail page of the installer's organization.
  6. (Optional) In the Notify on Apex Error field, enter the username of the person to notify if an uncaught exception occurs in the Apex code. If you don’t specify a username, all uncaught exceptions generate an email notification that is sent to Salesforce. This option is only available for managed packages.
  7. (Optional) In the Notify on Packaging Error field, enter the email address of the person who receives an email notification if an error occurs when a subscriber’s attempt to install, upgrade, or uninstall a packaged app fails. This field appears only if packaging error notifications are enabled. To enable notifications, contact Salesforce Partner Support.
  8. (Optional) Enable language extension packages. (Beta)
    1. Under Language Settings, click Edit.
    2. Select Enable Language Extension Package and save your changes.
  9. (Optional) Enter a description that describes the package. You can change this description before you upload it to AppExchange.
  10. (Optional) Specify a post install script. You can run an Apex script in the subscriber organization after the package is installed or upgraded. For more information, see Running Apex on Package Install/Upgrade.
  11. (Optional) Specify an uninstall script. You can run an Apex script in the subscriber organization after the package is uninstalled. For more information, see Running Apex on Package Uninstall.
  12. Save your work.