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
Use Apex Referenced by Managed Packages
Set Package Versions for Apex Classes and Triggers
Managed Apex Considerations for Package Subscribers
Safely Upgrade Packages from Developer and Subscriber Perspectives
Apex Reference
Appendices
PDF

Managed Apex Considerations for Package Subscribers

As you use managed Apex, keep these considerations in mind.
  • If a package developer deprecates a global Apex identifier in a managed package, you can only reference that identifier if you specify a package version between the creation and the deprecation of the identifier. Identifiers include global Apex methods, classes, exceptions, enums, interfaces, properties, and class variables. This behavior applies to both static and dynamic references, such as identifiers accessed with the Type.forName() method, the instanceof keyword, and the ApexTypeImplementor object.
  • Similarly, if a package developer deletes a schema from a managed package, you can only reference the schema in Apex if you specify a package version before the deletion of the schema. This behavior applies to both static and dynamic references, such as objects and fields accessed with Schema.describe() methods.