Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Running Apex
Debugging, Testing, and Deploying Apex
Debugging Apex
Testing Apex
Deploying Apex
Apex in Managed Packages
Managed Package Types
Develop and Distribute Apex for Managed Packages
Apex Versioning in Managed Packages
Version Apex Code Behavior
Apex Code Items That Aren’t Versioned
Deprecate Managed Apex
Testing Versioned Behavior in Apex Code
Prevent Field Name Collisions in Managed SOQL Queries
Best Practices for Using Global Apex in Managed Packages
Design Managed Apex for Agentforce
Use Apex Referenced by Managed Packages
Safely Upgrade Packages from Developer and Subscriber Perspectives
Apex Reference
Appendices
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.

Deprecate Managed Apex

Use the @Deprecated annotation to specify Apex identifiers that can subscribers can no longer reference in subsequent releases of the managed package. Deprecation is useful when you’re refactoring code in managed packages as the requirements evolve.

Apex identifiers include methods, classes, exceptions, enums, interfaces, and variables. After you upload another package version as Managed — Released, new subscribers that install the latest package version can’t see the deprecated identifiers. However, the identifiers still function for existing subscribers and API integrations. As the package developer, you can still reference deprecated identifiers internally.

You can’t use the @Deprecated annotation in Apex classes or triggers in unmanaged packages.

Note

You can use Managed — Beta package versions for evaluation and feedback with a pilot set of users in different Salesforce orgs. If you deprecate an Apex identifier, and then upload a version of the package as Managed — Beta, subscribers that install the package version still see the deprecated identifier in that package version. If the package developer then uploads a Managed — Released package version, subscribers will no longer see the deprecated identifier in the package version after they install it.