Assign Override Values in Your LMO

To override the default value of a feature parameter in a subscriber’s org, update the appropriate junction object record in your LMO.

  1. Open the license record for a subscriber’s installation of your package.

  2. In the related list for Feature Parameter Booleans, Feature Parameter Integers, or Feature Parameter Dates, select the feature parameter whose value you want to update.

  3. Click Edit.

  4. Set a value.

  5. Click Save.

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Set Up Your Development Environment
Before You Create Second-Generation Managed Packages
Scratch Orgs and Package Development
Workflow for Second-Generation Managed Packages
Components Available in Second-Generation Managed Packages
Editable Properties After Package Promotion or Installation
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in Second-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
Assign Override Values in Your LMO
Check LMO-to-Subscriber Values in Your Code
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
Get Started with AgentExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
Previous Versions