Second-Generation Managed Packaging Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
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
Package Agentforce Metadata Components
Develop and Package Agent Templates Using Scratch Orgs
Package Data Cloud Metadata Components
Protected Components in Managed Packages
Set Up a Platform Cache Partition with Provider Free Capacity
Metadata Access in Apex Code
Permission Sets and Profile Settings in Packages
Protecting Your Intellectual Property
Call Salesforce URLs Within a Package
Namespace-Based Visibility for Apex Classes in Second-Generation Managed Packages
Work with Services Outside of Salesforce
Package Connected Apps in Second-Generation Managed Packaging
Test and Respond to the New Order Save Behavior
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 AppExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Set Up a Platform Cache Partition with Provider Free Capacity

Salesforce provides 3 MB of free Platform Cache capacity for security-reviewed managed packages. This is made available through a capacity type called Provider Free capacity and is automatically enabled in all Developer edition orgs.
Follow the steps here to allocate the Provider Free capacity to a Platform Cache partition before adding it to your managed package.

If a Platform Cache partition is already part of your managed package, you can choose to edit the existing partition and allocate the Provider Free capacity to it.

Note

Create a partition from the Platform Cache page and then set it up to use the Provider Free capacity

  1. From Setup, in the Quick Find box, enter Platform Cache, and then select Platform Cache.
    As the Provider Free capacity is automatically enabled in all Developer edition orgs, the Org’s Capacity Breakdown donut chart shows the Provider Free capacity.
  2. Click New Platform Cache Partition.
  3. In the Label box, enter a name for the partition. The name can contain alphanumeric characters only and must be unique in your org.
  4. In the Description box, enter an optional description for the partition.
  5. In the Capacity section, allocate separate capacities for session cache and org cache from the available Provider Free capacity.
  6. Save the new Platform Cache partition.
You can add this new Platform Cache partition to your managed package. When a security-reviewed managed package with Platform Cache partition is installed on the subscriber org, the Provider Free capacity is allocated and automatically made available to the installed partition. The managed package can start using the Platform Cache partition; no post-install script or manual allocation is required.

If the managed package is not AppExchange-certified and security-reviewed, the Provider Free capacity resets to zero and will not be allocated to the installed Platform Cache partition.

Note

When a Platform Cache partition with Provider Free capacity is installed in a subscriber org, the Provider Free capacity allocated is non-editable. The provider free capacity of one installed partition can’t be used for any other partition.

After you install a Platform Cache partition with Provider Free capacity, you can edit the partition and make additional allocations from the available platform cache capacity of the org.

Tip