Scratch Orgs and Package Development

Scratch orgs are temporary Salesforce orgs intended for development and automation. They enable source-driven deployments of Salesforce code and metadata. A scratch org is fully configurable, allowing developers to emulate different Salesforce editions with various features and preferences.

You can use a scratch org to develop the app you want to package, and you can also create scratch orgs to test out your package. Scratch orgs also help with continuous integration (CI) processes to automate package development steps. For example, you could write a script that creates a package version, creates a scratch org, installs the package version into the scratch org, runs Apex tests, and emails the test results to the release manager.

To use Data Cloud components in scratch orgs or to add these components to a package, Data Cloud for Scratch Orgs must be enabled. Log a case with Salesforce Partner Support and request that Data Cloud for Scratch Orgs be enabled on your Partner Business Org. Data Cloud for Scratch Orgs is only available to scratch orgs associated with the Dev Hub in your Partner Business Org.

• Get Access to Scratch Orgs That Have Agentforce

  Agentforce is a set of tools to create and customize AI agents that are deeply and securely integrated with customers’ data and apps. Agentforce brings together humans with agents to transform the way work gets done. Start your journey with Agentforce by testing it in a scratch org.

• Scratch Org Allocations for Salesforce Partners

  To ensure optimal performance, Salesforce partners are allocated a set number of scratch orgs in their Partner Business Org (PBO). These allocations determine how many scratch orgs you can create daily, and how many can be active at a given point.

• Manage Scratch Orgs from the Dev Hub Org

  You can view and delete your scratch orgs and their associated requests from the Dev Hub org.

• Supported Scratch Org Editions for Partners

  Create partner edition scratch orgs from a Dev Hub partner business org.

j

First-Generation Managed Packages

Why Switch to Second-Generation Managed Packaging?

Move to 2GP: Migrate Your Managed Packages with Ease

Register a Namespace for a First-Generation Managed Package

Create a First-Generation Managed Package Using a UI

Create a First-Generation Managed Package using Salesforce DX

Enable Dev Hub and Second-Generation Managed Packaging

Limited Access License for Package Developers

Add a Limited Access User to Your Dev Hub Org

Link a Namespace to a Dev Hub Org

Scratch Orgs and Package Development

Get Access to Scratch Orgs That Have Agentforce

Scratch Org Allocations for Salesforce Partners

Manage Scratch Orgs from the Dev Hub Org

Supported Scratch Org Editions for Partners

Build and Release Your App with Managed Packages

Packaging Checklist

Deploy the Package Metadata to the Packaging Org

Create a Beta Version of Your App

Install the Package in a Target Org

Create a Managed Package Version of Your App

View Information About a Package

Components Available in First-Generation Managed Packages

Editable Properties After Package Promotion or Installation

Behavior of Specific Metadata in First-Generation Managed Packages

Package and Test Your First-Generation Managed Package

Update Your First-Generation Managed Package

Publish Upgrades to First-Generation Managed Packages

Manage Licenses for Managed Packages

Manage Features in First-Generation Managed Packages

AgentExchange App Analytics for First-Generation Managed Packages

Developing and Distributing Unmanaged Packages

Previous Versions