Create a First-Generation Managed Package Using a UI

If your goal is to build an app and distribute it on AgentExchange, 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

From Setup, in the Quick Find box, enter Package Manager, and then select Package Manager.
Click New.
Enter a name for your package. You can use a different name than what appears on AgentExchange.
From the dropdown menu, select the default language of all component labels in the package.
(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 AgentExchange Downloads page and app detail page of the installer’s organization.
(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.
(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.
(Optional) Enter a description that describes the package. You can change this description before you upload it to AgentExchange.
(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.
(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.
Save your work.

What Are Beta Versions of Managed Packages?

A beta package is an early version of a managed package. The purpose of a beta package is to allow the developer to test their application in different Salesforce orgs and to share the app with a pilot set of users for evaluation and feedback.
Create a Beta Package for First-Generation Managed Packages

Follow this procedure to create and upload a beta package through the UI. (You can also upload a package using the Tooling API. For sample code and more details, see the PackageUploadRequest object in the Tooling API Developer Guide.)
Create and Upload a First-Generation Managed Package

Use the following procedure to create and upload a managed package through the UI. You can also upload a package using the Tooling API. For sample code and more details, see the PackageUploadRequest object in the Tooling API Developer Guide.
Publish Extensions to Managed Packages

An extension is any package, component, or set of components that adds to the functionality of a managed package. An extension requires that the base managed package is installed in the org. For example, if you have built a recruiting app, an extension to this app can include a component for performing background checks on candidates.
View Package Details in First-Generation Managed Packages

From Setup, enter Packages in the Quick Find box, then select Packages. Click the name of a package to view its details, including added components, whether it’s a managed package, whether the package has been uploaded, and so on.
Notifications for Package Errors

Accurately track failed package installations, upgrades, and uninstallations in subscriber orgs with the Notifications for Package Errors feature. Proactively address issues with managed and unmanaged packages and provide support to subscribers so that they can successfully install and upgrade your apps.