Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Managed Packages
Components Available in Managed Packages
Behavior of Specific Metadata in Second-Generation Managed Packages
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

Newer Version Available

This content describes an older version of this product. View Latest

Protected Components in Managed Packages

Developers can mark certain components as protected. Protected components can’t be linked to or referenced by components created in a subscriber org. A developer can delete a protected component in a future release without worrying about failing installations. However, after a component is marked as unprotected and is released globally, the developer can’t delete it.

Developers can mark these components as protected in managed packages.

  • Custom labels
  • Custom links (for Home page only)
  • Custom metadata types
  • Custom objects
  • Custom permissions
  • Custom settings
  • Workflow alerts
  • Workflow field updates
  • Workflow outbound messages
  • Workflow tasks

Considerations for Protected Custom Objects in Subscriber Sandboxes

When a subscriber creates a partial copy sandbox, protected custom objects don’t display in the list of objects to copy. Data contained in the records of protected custom objects is never copied to sandboxes, regardless of sandbox type.