Salesforce Spring ’26 Release On Demand
Salesforce Spring ’26 brings a long list of updates, but most teams don’t have the time, or the need, to digest every line of the release notes. What matters is understanding which changes will affect your platform and which ones can wait.
In this session, Salesforce MVP Hall of Fame member Keir Bowden joined Ziipline Head of Technology Stuart Barber to talk through the release from a delivery perspective. This is a hands-on discussion based on real projects, focused on topics that could affect your architecture and plans in the next few months.
What this session covers
Platform changes that need planning
Spring ’26 introduces updates that require review, not just awareness. We cover legacy force.com URL redirections, restrictions on new connected apps and the move to External Client Apps, SOAP API login retirement timelines, and the shift to a multiple configuration SAML framework. These are the areas that need action to avoid disruption.
AI moving into delivery
Agentforce continues to expand across Sales and Service. We highlight improved AI draft accuracy in Flow Builder without consuming generative credits, modifying existing flows with Agentforce, inbound lead and nurturing agents, and enhanced case summaries with translation. The focus is practical application and governance.
Automation with stronger control
Flow enhancements improve oversight and maintainability. We look at version comparison, performance monitoring on the Flow canvas, screen flow improvements such as file preview and URL launching, and new approval components that reduce custom build.
Clearer reporting and insight
Reporting and analytics updates strengthen visibility. This includes custom disclaimers on exported reports, CRM Analytics bulk actions and dashboard downloads, and improved tracking of AI adoption in Service. The emphasis is measurable impact rather than feature volume.
So what should you actually do?
A release on its own doesn’t change much. What matters is what you choose to do next.
When we look at new Salesforce functionality, we’re thinking about how it fits into the shape of your existing platform. Does it simplify things? Does it introduce risk? Does it solve a problem you actually have? If the answer isn’t clear, it’s probably not a priority.
It is also worth paying attention to what is still in beta. Not because every beta feature will make it to general availability, but because it shows where Salesforce is heading. A specific capability may evolve or even disappear, but the underlying problem space rarely does.
Engaging early creates the opportunity to give feedback and help influence how a feature takes shape. Waiting until GA often means those decisions are already fixed. Having visibility of beta functionality also means you are better prepared when it goes live.
If Spring ’26 has raised questions about where to focus, or how emerging capabilities may shape your roadmap, we’re happy to talk it through.