First-Generation Managed Packaging Developer Guide
jNote: 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.
Best Practices for Feature Management
Here are some best practices when working with feature parameters.
- We recommend that you use this feature set in a test package and a test LMO before using it with your production package. Apply changes to your production package only after fully understanding the product’s behavior.
- Create LMO-to-subscriber feature parameters to enable features from your LMO for
individual subscriber orgs. Don’t use the Apex code in your managed package to modify
LMO-to-subscriber feature parameters’ values in subscriber orgs. You can’t send the modified
values back to your LMO, and your records will be out of sync.
Use LMO-to-subscriber feature parameters as read-only fields to manage app behavior. For example, use LMO-to-subscriber feature parameters to track the maximum number of permitted e-signatures or to make enhanced reporting available.
- Create subscriber-to-LMO feature parameters to manage activation metrics. Set these feature parameters’ values in subscriber orgs using the Apex code in your managed package. For example, use subscriber-to-LMO feature parameters to track the number of e-signatures consumed or to check whether a customer has activated enhanced reporting.