How to create & upload Managed Package in Salesforce? | Techila
single,single-post,postid-1978,single-format-standard,ajax_updown_fade,page_not_loaded,,qode_grid_1300,footer_responsive_adv,hide_top_bar_on_mobile_header,qode-content-sidebar-responsive,qode-theme-ver-9.4.2,bridge,wpb-js-composer js-comp-ver-4.12,vc_responsive

How to create & upload Managed Package in Salesforce?


How to create & upload Managed Package in Salesforce?

A package is a container for something as small as an individual component or as large as a set of related apps. After creating a package, you can distribute it to other Salesforce users and organizations, including those outside your company.

Unmanaged packages

Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application. Once the components are installed from an unmanaged package, the components can be edited in the organization they are installed in.

Managed packages

Managed packages are typically used by Salesforce partners to distribute and sell applications to customers. These packages must be created from a Developer Edition organization. Managed packages are also fully upgradeable. To ensure seamless upgrades, certain destructive changes, like removing objects or fields, can not be performed.

  1. Create a package:
    1. From Setup, enter Packages in the Quick Find/Search box, then select Packages.
    2. Click New.
    3. Enter a name for your package. This does not have to be the same name that appears on AppExchange.
    4. From the drop-down menu, select the default language of all component labels in the package.
    5. Optionally, in the Notify on Apex Error field, enter the username of the person who should receive an email notification if an exception occurs in Apex code that is not caught by the code. If you don’t specify a username, all uncaught exceptions generate an email notification that is sent to Salesforce.
    6. Optionally, 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 your Salesforce representative.
    7. Optionally, choose a custom link from the Configure Custom Link field to display configuration information to installers. The custom link displays as a Configure link within Salesforce on the Installed Packages page and package detail page of the subscriber’s organization.
    8. Optionally, enter a description that describes the package. You will have a chance to change this description before you upload it to AppExchange.
    9. Optionally, specify a post install script. This is an Apex script that runs in the subscriber organization after the package is installed or upgraded. 
    10. Optionally, specify an uninstall script. This is an Apex script that runs in the subscriber organization after the package is uninstalled. 
    11. On the right side of the screen, select the Managed.
    12. Click Save.
  2. Optionally, change the API access privileges. By default, API access is set to Unrestricted, but you can change this setting to further restrict API access of the components in the package.
  3. Add the necessary components for your app.
    1. Click Add Components.
    2. From the drop-down list, choose the type of component.
    3. Select the components you want to add.
    4. Click Add To Package.
    5. Repeat these steps until you have added all the components you want in your package.
  4. Optionally, click View Dependencies and review a list of components that rely on other components, permissions, or preferences within the package.Click Done to return to the Package detail page.
  5. Click Upload.
  6. On the Upload Package page, do the following:
    1. Enter a Version Name, such as Spring 12. The version name is the marketing name for a specific release of a package and allows you to create a more descriptive title for the version than just a number.
    2. Enter a Version Number.
    3. Select a Release Type of Managed – Released.
    4. Change the Description, if necessary.
    5. Optionally, specify a link to release notes for the package. Click URL and enter the details in the text field that appears. This link will be displayed during the installation process, and on the Package Details page after installation.
    6. Optionally, specify a link to post install instructions for the package. Click URL or Visualforce page and enter the details in the text field that appears. This link will be displayed on the Package Details page after installation.
    7. Optionally, enter and confirm a password to share the package privately with anyone who has the password. Don’t enter a password if you want to make the package available to anyone on AppExchange and share your package publicly.
    8. Salesforce automatically selects the requirements it finds. In addition, select any other required components from the Package Requirements and Object Requirements sections to notify installers of any requirements for this package.
    9. Click Upload.


Courtesy :

“Know more about Salesforce Consulting at Techila”

Author: techila

No Comments

Post A Comment