ISVforce Guide

Introduction
ISVforce Quick Start
Grow Your AppExchange Business
Designing and Building Your App
Packaging and Testing Your App
Passing the Security Review
Publish Your Offering on the AppExchange
Manage Orders
Managing Licenses
Manage Features
Provide a Free Trial
Supporting Your AppExchange Customers
Upgrading Your App
About Package Versions
Create and Upload Patches
Working with Patch Versions
Publish Upgrades to Managed Packages
Pushing an Upgrade
Appendices
Glossary
PDF

Newer Version Available

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

Create and Upload Patches

Patch versions and push upgrades are only available to Salesforce ISV partners.

Note

To create a patch version:
  1. From Setup, enter Packages in the Quick Find box, then select Packages.
  2. Click the name of your managed package.
  3. On the Patch Organization tab, click New.
  4. Select the package version that you want to create a patch for in the Patching Major Release dropdown. The release type must be Managed - Released.
  5. Enter a username for a login to your patch org.
  6. Enter an email address associated with your login.
  7. Click Save.

    If you ever lose your login information, click Reset on the package detail page under Patch Development Organizations to reset the login to your patch development org.

    Note

If the main development org from which you created the patch org has My Domain enabled, the patch org also has My Domain enabled. The name of the patch development org’s custom subdomain is randomly generated.

After you receive an email that Salesforce has created your patch development org, you can click Login to begin developing your patch version.

Development in a patch development org is restricted.
  • You can’t add package components.
  • You can’t delete existing package components.
  • API and dynamic Apex access controls can’t change for the package.
  • No deprecation of any Apex code.
  • You can’t add new Apex class relationships, such as extends.
  • You can’t add Apex access modifiers, such as virtual or global.
  • You can’t add new web services.
  • You can’t add feature dependencies.
When you finish developing your patch, upload it through the UI in your patch development org. 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.

When you upload a new package in your patch development org, the upload process is asynchronous. Because the time to process the request varies, the package might not be available immediately after the upload. While waiting, you can run SOQL queries on the PackageUploadRequest status field to monitor the request.

Note

  1. From Setup, enter Packages in the Quick Find box, then select Packages.
  2. Click the name of the package.
  3. On the Upload Package page, click Upload.
  4. Enter a Version Name. As a best practice, it's useful to have a short description and the date.
  5. Notice that the Version Number has had its patchNumber incremented.
  6. For managed packages, select a Release Type:
    • Choose Managed - Released to upload an upgradeable version. After upload, some attributes of Salesforce components are locked.
    • Choose Managed - Beta if you want to upload a version of your package to a small sampling of your audience for testing purposes. You can still change the components and upload other beta versions.

      Beta packages can only be installed in Developer Edition or sandbox organizations, and thus can't be pushed to customer organizations.

      Note

  7. Change the Description, if necessary.
  8. 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.
  9. 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.
  10. Click Upload.

To distribute your patch, you can either share the upload link or schedule a push upgrade.