Start a conversation Sign in
Start a conversation
  1. CloudSense Support
  2. General category
  3. Public Articles

Compatibility of CloudSense Packages with Salesforce Summer '25 Release

Overview

The customer was concerned about the compatibility of CloudSense packages with the Salesforce Summer '25 release, particularly regarding API version changes. They noted that many Apex classes and triggers were using API versions lower than 21. It was confirmed that Salesforce's API deprecation policy does not affect Apex classes or triggers, and the customer's packages are at recommended versions, ensuring no service disruption.

Information

Issue: Concern about compatibility of CloudSense packages with Salesforce Summer '25 release due to API version changes.

Resolution:

  1. Understanding API Deprecation:
    • Salesforce deprecates external API versions (REST, SOAP, Bulk, Metadata, Tooling, Streaming & Pub/Sub APIs).
    • Apex classes and triggers are not affected by API deprecation.
  2. Current Package Versions:
    • Customer's packages: cspofa 33.6.11 and csam 33.0.2.
    • These versions are recommended and compatible with the Salesforce Summer '25 release.

Important: Apex code will continue to function with older API versions, and there is no forced upgrade or deactivation based on API deprecation.

Frequently Asked Questions

How do I know if my Apex classes and triggers are affected by Salesforce API deprecation?
Salesforce's API deprecation policy does not apply to Apex classes or triggers. Your Apex code will continue to run even if it uses older API versions.
Do I need to upgrade my CloudSense packages for the Salesforce Summer '25 release?
No upgrade is necessary if you are using the recommended package versions (cspofa 33.6.11 and csam 33.0.2), which are compatible with the Salesforce Summer '25 release.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments