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
Get Started with the License Management App
Lead and License Records in the License Management App
Modify a License Record
Refresh Licenses for a Managed Package
Extending the License Management App
Move the License Management App to Another Salesforce Org
Troubleshoot the License Management App
Best Practices for the License Management App
Troubleshoot Subscriber Issues
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Best Practices for the License Management App

Follow these best practices when you use the License Management App (LMA).
  • To take advantage of entitlements that are unique to AppExchange partners, use your partner business org as your License Management Org.
  • Create a list view filter for leads created by installed packages. The filter helps your team separate subscriber-based leads from leads coming from other sources.
  • Use the API to find licensed users. The isCurrentUserLicensed method determines if a user has a license to a managed package. For more information, see the Apex Reference Guide.
  • Treat the LMA custom objects as read-only. Use the Modify License page to edit licenses. Don’t attempt to directly or programmatically edit license records.
  • The LMA automatically creates package, package version, and license records. Customizations, such as adding required custom fields or creating workflow rules, triggers, or validation rules that require custom fields, can prevent the LMA from working properly.