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
How to Read App Analytics Package Usage Log Data
Determine What Packaged Component Was Accessed
Identify Who Interacted with Your Packaged Component
Identify How a User Interacted with Your Packaged Component
Custom Object and External Object Interactions
Lightning Interactions
Apex Interactions
Visualforce Interactions
CRM Analytics Asset Interactions
Custom Interactions
Package Usage Logs Schema
Subscriber Snapshots
Test Custom Integrations
AgentExchange App Analytics Developer Cookbook
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.

Determine What Packaged Component Was Accessed

To analyze a package usage log record, always start with your packaged component.
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

In App Analytics package usage logs, the name of each packaged component is represented by the custom_entity field and its type is represented by the custom_entity_type field. Your managed package likely contains multiple packaged components.

To identify each packaged component uniquely, combine these fields.
  • package_id
  • package_version_id
  • managed_package_namespace
  • custom_entity
  • custom_entity_type