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
How Does AgentExchange App Analytics Data Flow?
How Should I Plan My App Analytics Query Strategy?
Recommendations
Small-Sized Partners
Medium-Sized Partners
Large-Sized Partners
Where Do I Go for More Information About AgentExchange App Analytics Queries?
Package Usage Summaries
Package Usage Logs
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.

Small-Sized Partners

Small-sized partners have manageable subscriber bases and one or two managed packages. A small partner’s total daily usage data across all managed packages is 5 GB or less. Also, small partner’s queries complete well under the 15-minute processing time limit.
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

Given how manageable smaller partners’ data is, after you run your regular queries one time, we recommend that you run a daily catch-up query as your main query. Sweep in all data for all your managed packages for the last 30 days.

Data Type How to Get Started How to Schedule Catch-Up Queries
Subscriber Snapshots An initial query to retrieve data from when App Analytics was enabled for your managed package.
  • One daily catch-up query.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to 30 days ago.
  • Omit EndTime.
  • Each day advance StartTime and AvailableSince by 1 day.
Package Usage Summaries An initial query to retrieve data from when App Analytics was enabled for your managed package.
  • One daily catch-up query.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to the first of the previous month.
  • Omit EndTime.
  • Each day advance AvailableSince by 1 day.
  • Each month advance StartTime to the first of the previous month.
Package Usage Logs An initial query to retrieve data from when App Analytics was enabled for your managed package.
  • One daily catch-up query.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to 30 days ago.
  • Omit EndTime.
  • Each day advance StartTime and AvailableSince by 1 day.

Example

Most of your customers use your package on an NA or EU instance, so you run your queries at 18:00 UTC. You have a couple customers on an AP instance, so you create catch-up queries to ensure that you capture data from around the world.

  • On March 31 at 18:00 UTC, run your regular queries.

    Subscriber Snapshot

    Package Usage Summary

    Package Usage Log

  • On April 1 at 18:00 UTC run these three catch-up queries.

    Subscriber Snapshot Catch-Up Query

    Package Usage Summary Catch-Up Query

    Package Usage Log Catch-Up Query

  • On April 2 at 18:00 UTC, run the same catch-up queries, but advance the subscriber snapshot and package usage log AvailableSince and StartTime date by 1 day each. Advance the package usage summary AvailableSince by 1 day.

    Subscriber Snapshot Catch-Up Query

    Package Usage Summary Catch-Up Query

    Package Usage Log Catch-Up Query