ISVforce Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Newer Version Available

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

Creating and Uploading a Managed Package

Use the following procedure to create and upload a managed package. The procedure assumes you have already created a namespace and beta package. If you are uploading a beta package for testing, see Creating and Uploading a Beta Package.
  1. Create a package:
    1. From Setup, click Create | Packages.
    2. Click New.
    3. Enter a name for your package.
    4. From the drop-down menu, select the default language of all component labels in the package.
    5. 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.
    6. In the Apex Exception Notification Recipient field, enter the username of the person who will receive an email notification if an exception occurs in an Apex script that is not caught by the script.
    7. Enter a description of the package.
    8. On the right side of the screen, select the Managed checkbox.
    9. 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 components:
    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.

    Some related components are automatically included in the package even though they might not display in the Package Components list. For example, when you add a custom object to a package, its custom fields, page layouts, and relationships with standard objects are automatically included. For a complete list of components, see Components Automatically Added to Packages.

    Note

  4. Optionally, click Show Dependencies and review a list of components that rely on other components, permissions, or preferences within the package. For more information on dependencies, see Understanding Dependencies. 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, such as 1.0. For more information on versions, see Upgrading Your App.
    3. Select a Release Type of Managed - Released.
    4. Change the Description, if necessary.
    5. 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.
    6. 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.
    7. Click Upload.
  7. Once your upload is complete, you can do any of the following.
    • Click Change Password link to change the password option.
    • Click Deprecate to prevent new installations of this package while allowing existing installations to continue operating.

      You cannot deprecate the most recent version of a managed package.

      Note

      When you deprecate a package, remember to remove it from AppExchange as well. See “Removing Apps from AppExchange” in the AppExchange online help.

    • Click Undeprecate to make a deprecated version available for installation again.
You will receive an email that includes an installation link when your package has been uploaded successfully.

If you uploaded from your Salesforce production organization, notify installers who want to install it in a sandbox organization to replace the “login.salesforce.com” portion of the installation link with “test.salesforce.com.”

Note