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?
Move to 2GP: Migrate Your Managed Packages with Ease
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
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
Feature Parameter Metadata Types and Custom Objects
Set Up Feature Parameters
Install and Set Up the Feature Management App in Your License Management Org
Create Feature Parameters in Your Packaging Org
Add Feature Parameters to Your Managed Package
Use LMO-to-Subscriber Feature Parameters to Enable and Disable Features
Track Preferences and Activation Metrics with Subscriber-to-LMO Feature Parameters
Hide Custom Objects and Custom Permissions in Your Subscribers’ Orgs
Best Practices for Feature Management
Considerations for Feature Management
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Create Feature Parameters in Your Packaging Org

Create a feature parameter in your packaging org, and set its type, default value, and data flow direction.
  1. From Setup, enter Package Manager in the Quick Find box, then select Package Manager.
  2. In the Packages section, in the Package Name column, select your managed package.
  3. On the Feature Parameters tab, click New Boolean, New Integer, or New Date.

    If the Feature Parameters tab isn’t visible, log a case with Salesforce Partner Support.

  4. Give your feature parameter a developer name that meets the standard criteria for developer names. The name must be unique in your org. It can contain only alphanumeric characters and underscores, and must begin with a letter. It can’t include spaces, end with an underscore, nor contain two consecutive underscores.
  5. Give the feature parameter a label.
  6. Set a default value for the feature parameter. If you’re creating a Feature Parameter Boolean, you see only a checkbox for Default Value. If you want your default value to be true, select this checkbox. Integer values can’t exceed nine digits.
  7. Set a data flow direction. To use this feature parameter to control behavior in your subscriber’s org, select LMO to Subscriber. To collect activation metrics from your subscriber, select Subscriber to LMO. Note: After the feature parameter is included in a promoted and released package version, the data flow direction can't be changed.
  8. Click Save.