
Salesforce Summer ’25: What’s Changing, Why It Matters, Hint: Its going to break stuff
By Hitesh Malhotra
Salesforce’s Summer ’25 release is here — and it’s not just another update. It’s a structural shift that impacts security, performance, and future compatibility. If your org uses AngularJS-based Omniscripts or older pipelines, this change will affect you.
1. The Current Situation
Many organizations still rely on AngularJS-based Omniscripts built years ago. They work — for now — but they rely on a framework that is no longer supported by Google and no longer patched by Salesforce. Your pipelines may also still be pinned to older Node.js versions or build tools, leaving you vulnerable to security flaws and slower deployments.
2. What’s Changing
AngularJS Omniscripts Are Deprecated
All Omniscripts must be converted to Lightning Web Component (LWC)-based Omniscripts.Advanced Apex Permission Checks
Salesforce has introduced the PerformAdvancedCheck flag to enforce permission checks using Permission Sets and Permission Set Groups, offering a more robust security model.Updated OmniOut and Build Tool Requirements
Node.js must now be 18.20.4 – 22.11.0
Build Tool version must be 1.17.11+
Puppeteer is upgraded to improve testing reliability
3. Why This Is Important
Security – AngularJS is unpatched, making it a potential attack surface. LWC closes that gap and runs in a secure Locker-compliant environment.
Performance – LWC components load faster, reduce JavaScript bundle size, and improve responsiveness for users.
Future-Proofing – Waiting means risking broken functionality when Salesforce fully retires AngularJS support in future releases.
4. What’s Going to Break
Any Omniscript still using AngularJS is at risk of failing after platform updates.
Custom navigation or validation logic may behave unpredictably in new runtime environments.
Build and deployment pipelines that rely on outdated Node.js versions may stop compiling correctly.
Apex classes with insufficiently scoped permissions may throw errors when advanced checks are enabled.
5. What It Affects
End-user experience – slower pages, broken flows, frustrated agents or customers
Compliance – inability to enforce least-privilege security models
Deployment cycles – higher failure rates if toolchain is out of date
Total cost of ownership – delayed upgrades = higher emergency remediation costs later
6. Why Organizations Should Use PS Advisory
PS Advisory brings industry-specific expertise to this transition:
Inventory & Risk Assessment – We catalog your AngularJS Omniscripts, identify unsupported features, and prioritize by business impact.
Migration Execution – We rebuild scripts as LWCs, refactor custom logic, and regression-test them.
Security Hardening – We configure advanced permission checks and run access tests to prevent lockouts or data leaks.
Pipeline Modernization – We upgrade your Node.js and build tool versions, implement CI/CD best practices, and speed up deployment.
Performance Tuning – We measure load times before and after migration, then optimize for faster execution.
Self-Assessment Checklist
Use this checklist to determine if you’re impacted by Summer ’25 changes:
Do you have any active AngularJS-based Omniscripts?
Are you using custom templates or scripts that were built before LWC support?
Is your CI/CD pipeline running Node.js older than 18.20.4 or Build Tool older than 1.17.11?
Do you rely on profile-based permissions rather than Permission Sets or Groups?
Do you have compliance requirements that demand least-privilege access control (HIPAA, SOX, GDPR)?
Have you run performance tests on your Omniscripts in the past 6 months?
If you answered “yes” to any of the first four or “no” to the last two, this release directly affects you — and action should be taken immediately.
Your Next Step
The move to LWC and advanced security checks is not optional — it is required to maintain a secure, performant, and supportable Salesforce org.
Schedule a Migration Readiness Assessment with PS Advisory to get a clear inventory, prioritized migration plan, and a roadmap for secure, fast, and future-proof Salesforce operations.
Links:
Deprecation and End of Support for AngularJS-Based Omniscripts
About the author:
Hitesh Malhotra has over 20 years of experience in the Salesforce ecosystem and holds 25+ certifications. He has delivered solutions across Europe, South Africa, and the United States, consistently translating complexity into clarity and ensuring scalability for clients’ growth. You can connect with Hitesh on LinkedIn