First-Generation Managed Packaging Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
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
Get Access to Agentforce in Your 1GP Packaging Org
Components Automatically Added to First-Generation Managed Packages
Protected Components in Managed Packages
Set Up a Platform Cache Partition with Provider Free Capacity
Package Dependencies in First-Generation Managed Packages
Metadata Access in Apex Code
Permission Sets and Profile Settings in Packages
Permission Set Groups
Custom Profile Settings
Protecting Your Intellectual Property
Call Salesforce URLs Within a Package
Develop App Documentation
API and Dynamic Apex Access in Packages
Connected Apps
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

Develop App Documentation

To help your subscribers make the most of your app, provide documentation about how to configure and customize your app.
  • Configure Option—You can include a Configure option for installers. This option can link to installation and configuration details, such as:
    • Provisioning the external service of a client app
    • Custom app settings

    The Configure option is included in your package as a custom link. You can create a custom link for your home page layouts and add it to your package.

    1. Create a custom link to a URL that contains configuration information, or a Visualforce page that implements the configuration. When you create your custom link, set the display properties to Open in separate popup window so that the user returns to the same Salesforce page when done.
    2. When you create the package, choose this custom link in the Configure Custom Link field of your package detail.
  • Data Sheet—Give installers the fundamental information they must know about your app before they install.
  • Customization and Enhancement Guide—Let installers know what they must customize after installation as part of their implementation.
  • Custom Help—You can provide custom help for your custom object records and custom fields.