Second-Generation Managed Packaging Developer Guide

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
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
Get Started with AgentExchange App Analytics
App Analytics Use Cases
Enable App Analytics on Your Second-Generation Managed Package
Download Package Usage Logs, Package Usage Summaries, and Subscriber Snapshots
Considerations for Custom Interactions
AgentExchange App Analytics Best Practices
Package Usage Summaries
Package Usage Logs
Subscriber Snapshots
Test Custom Integrations
AgentExchange App Analytics Developer Cookbook
What Are Recipes?
Before You Begin
Get Help with Prerequisites
CRM Analytics Recipes
App Analytics Recipes
Gaps Between First-Generation and Second-Generation Managed Packaging
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.

Before You Begin

Complete these prerequisites before you create App Analytics recipes.
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To access License Management App data, packages, and package versions: Read on Licenses, Packages, Package Versions
To request and retrieve AgentExchange App Analytics data: Create, Read, Edit, Delete, View All, and Modify All on the AppAnalyticsQueryRequest object
To use CRM Analytics: CRM Analytics Plus Admin user

To brush up on your AgentExchange App Analytics or CRM Analytics skills, we recommend completing these Trailhead modules.

  1. Set up your License Management Org (LMO).

    Use your LMO to track all Salesforce users who install your managed package. The LMO receives a notification in the form of a lead record when a user installs or uninstalls your package. It also tracks each package upload on AgentExchange. Typically, as an AgentExchange partner, you use your Partner Business Org (PBO) as your LMO.

  2. Register your security-reviewed managed package with your LMO. Follow the directions in Link a Package with Your License Management Organization.
  3. If you’re not using your PBO as your LMO, install the License Management App (LMA) in your LMO. The LMA lets you manage leads and licenses for your AgentExchange offerings. To install the LMA, read Get Started with the License Management App.

    If you’re using your PBO as your LMO, you’re all set. The LMA is automatically installed for you.

    Note

  4. Create an App Analytics Admin permission set that includes create and read access on the AppAnalyticsQueryRequest object. Assign this permission to any non-Admin users so that they can create App Analytics requests. Read Create Permission Sets in Salesforce Help if you need instructions.
  5. Set up the CLI using the Salesforce CLI Setup Guide. If you need a CLI refresher, take the App Development with Salesforce DX Trailhead module.
  6. Enable CRM Analytics in your Salesforce org.
  7. Create a CRM Analytics app named PartnerIntelligence.
  8. To request and retrieve a sample package usage log, create an AgentExchange App Analytics query request using the CLI. Save the CSV data file as RawPackageLogFile.csv.
  9. To request and retrieve package usage logs automatically, create an automation. Which automation method you choose depends on your business specifications and which data volume you’re automating.
    • For smaller datasets, such as package usage summaries, Apex scales well for automation. This GitHub repo has the details.
    • For larger datasets, such as package usage logs, automate using an Amazon Web Services (AWS) stack.
    • You can also use the free Salesforce Labs app, App Analytics. It offers great functionality to retrieve and automate data collection and to get started with recipes and dashboards. Salesforce Labs apps are developed by Salesforce employees and are unsupported.