First-Generation Managed Packaging Developer Guide

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
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
AgentExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Considerations for Feature Management

Keep these considerations in mind when working with feature parameters.
  • After a feature parameter is included in a promoted and released package version, we recommend that you only edit the value field located in LMO-to-subscriber junction objects.

    Modifying or deleting other fields or records related to feature parameters, including the data flow direction, may cause the FMA to stop operating correctly.

  • Don’t use the LMO to create or delete feature parameters.
  • When you update LMO-to-subscriber values in your LMO, the values in your subscribers’ orgs are updated asynchronously. This process can take several minutes.
  • When you publish a push upgrade to your managed package, feature parameters in your LMO and your subscribers’ orgs are updated asynchronously. Creating and updating the junction object records can take several minutes.
  • When the Apex code in your package updates subscriber-to-LMO values in your subscriber’s org, the changes can take up to 24 hours to reach your LMO.