Salesforce Summer 26 Admin Checklist
Most orgs get surprised by Salesforce releases. Not because the dates are hidden — they are published months in advance — but because the checklist for actually preparing keeps getting skipped until something breaks in production. Summer ’26 sandboxes start upgrading around May 9. Here is a practical six-step admin prep list so that date does not catch you off guard. Summer ’26 — Main Upgrade Weekends ~May 9 Sandbox preview orgs upgradeVaries by instance — check trust.salesforce.com for your exact date ~June 5 First non-preview sandbox weekendMost non-preview sandboxes on NA and EU instances ~June 12 Second non-preview sandbox weekend + Production beginsProduction orgs start upgrading — varies by instance The six steps worth completing before May 9 Step 1: Find your instance and exact upgrade date Not all Salesforce instances upgrade on the same weekend. Your specific upgrade date depends on the instance your org runs on, and there are three main release weekends across May and June. Find your instance in Setup under Company Information, then check the Salesforce Trust maintenance calendar for the exact date. This matters because ‘around May 9’ could mean May 9 or it could mean June 12 depending on your instance. Knowing your actual date changes how urgently the rest of this checklist needs to happen. Salesforce Trust maintenance calendar Step 2: Review the Summer ’26 release notes for your specific stack The full release notes are long. The useful shortcut is to search for ‘enforcement’ in the notes, because enforcement items are the changes that will be applied automatically — including to orgs that have not opted in to anything. Two items affect most orgs: the accessibility enforcement for components at 200 percent zoom, and the X (Twitter) Auth Provider callback URL change that requires manual reconfiguration. Both are breaking changes for the orgs they affect. Neither fixes itself after the upgrade. Salesforce Summer ’26 release notes Step 3: Audit your Connected Apps and External Client Apps status Summer ’26 tightens the External Client Apps enforcement that began in Spring ’26. If your org has Connected Apps your team created — not vendor-installed managed package apps, but apps your own admins or developers built — check whether they have been migrated. Apps that have not been migrated will face increasing enforcement pressure in Summer ’26. Connected Apps migration guide Step 4: Decide between preview and non-preview sandbox Preview sandboxes opt in to the Summer ’26 upgrade early, giving you more time to test before the production release. Non-preview sandboxes stay on the Spring ’26 release longer, giving you more time with a stable environment. Neither choice is universally correct — it depends on how many customisations you have to test and how much development work is currently in flight. The Salesforce Sandbox Preview Guide explains how to make the switch if you want to opt your sandbox into preview before the window closes. Summer ’26 Admin Prep — 6 Steps Before May 9 Complete before upgrade 1 Find your instance and exact upgrade date Setup → Company Information → note your instance (e.g. NA87). Check trust.salesforce.com/status/maintenance for your exact date. “Around May 9” could mean May 9 or June 12 depending on your instance. 5 minutes 2 Search “enforcement” in the Summer ’26 release notes Enforcement items are auto-applied — you do not opt in. The two that affect most orgs: accessibility enforcement for components at 200% zoom, and the X (Twitter) Auth Provider callback URL change that requires manual reconfiguration. Breaking changes 3 Audit your Connected Apps and ECA migration status App Manager → filter by Connected App → identify apps your org created (not vendor managed packages). If any have not been migrated to External Client Apps, Summer ’26 tightens enforcement further. Act now if pending 4 Decide: preview sandbox or non-preview? Preview gives you more testing time before production upgrades. Non-preview gives you a longer stable window during active development. The Salesforce Sandbox Preview Guide covers how to opt in. Window closes before May 9. Decision needed 5 Review Scheduled Flows that process large record volumes Summer ’26 introduces custom batch size control for Scheduled Flows. The default of 200 is now configurable. Flag any flow where governor limit errors are a known risk — set appropriate batch sizes before the first run on the new release. New control available 6 Bookmark the Release Manager beta opt-in New in Summer ’26: three release channels — Standard (stable), Accelerated (production-ready, not yet in major release), Dev (in active development). Opt in now for earlier visibility into what comes after Summer ’26. New capability Step 5: Review Scheduled Flows that process large record volumes Summer ’26 introduces custom batch size controls for Scheduled Flows. The default batch size of 200 records is now configurable. Any flow processing large record volumes where governor limit errors are a known risk should be reviewed before the upgrade lands, so you can set appropriate batch sizes from the first run on the new release rather than after the first failure. Step 6: Bookmark the Release Manager beta opt-in New in Summer ’26, the Salesforce Release Manager gives admins and developers access to three feature channels: Standard for stable production behaviour, Accelerated for production-ready features not yet in a major release, and Dev for features in active development. This is a significant shift toward continuous delivery. Opting in now gives your team earlier visibility into what is coming after Summer ’26, rather than discovering it in the next release notes drop. Six steps, one week. Admins who work through this before May 9 spend the upgrade weekend watching things work. Everyone else spends it finding out what broke. Already testing Summer ’26 features in your sandbox? If your org needs a second pair of eyes before the upgrade, our team at truesolv.com does exactly that. Follow us on LinkedIn for release-critical updates every week.
Salesforce Summer 26 Release
Summer ’26 sandboxes start upgrading around May 9. Release notes dropped April 22. If you have not looked at them yet, the window before your sandbox looks different and your customisations start behaving unexpectedly is narrow. This is the short version of what is actually changing — not the full list of every feature, but the things admins and developers should know about before the upgrade arrives. Consideration Preview Sandbox Non-Preview Sandbox When it upgrades Early — around May 9 Upgrades ahead of production release Later — June 5 or June 12 Stays on Spring ’26 longer Testing window for Summer ’26 Longer — you have weeks to validate customisations before production upgrades Shorter — less time between sandbox and production upgrade Stability during active development Lower — your sandbox is on new code while dev work is still in progress Higher — dev work continues on stable Spring ’26 release Best for orgs with Many customisations to validate, time-sensitive compliance testing, proactive release teams Active development sprints, tight deadlines, small teams without dedicated release bandwidth How to opt in Follow the Salesforce Sandbox Preview Guide — window closes before May 9 No action required — non-preview is the default What is in Summer ’26 that admins need to know Agentforce woven into CRM surfaces Summer ’26 moves Agentforce from a standalone layer to something embedded in daily Sales Cloud and Service Cloud workflows. AI summaries, deal coaching suggestions, and automated research appear directly in the views reps already use. For admins, this means any customisations built against these surfaces — record detail layouts, list views, service console components — may need testing against the new Agentforce-aware UI before the upgrade lands. Flow UI improvements: collapsible fault paths and readable data tables Large production flows are hard to maintain when the canvas is an unnavigable tangle of fault paths and unformatted data. Summer ’26 adds collapsible fault paths and a significantly improved data table display inside Flow Builder. These are cosmetic in that they do not change flow behaviour, but the maintenance benefit is real for any org with complex automations. Additionally, Summer ’26 extends Agentforce-powered natural language editing to Screen Flows, having added it to Record-Triggered and Scheduled Flows in Spring ’26. This remains an early-access feature and requires review before applying suggestions to production flows. Accessibility enforcement at 200 percent zoom Salesforce is enforcing accessibility standards for UI components at 200 percent browser zoom in Summer ’26. For orgs with custom Lightning components, custom page layouts, or Visualforce pages, this may produce unexpected layout behaviour that needs testing before the upgrade. Standard Salesforce Lightning components are already compliant. Custom-built components need to be checked. External Client Apps migration enforcement tightens Spring ’26 disabled new Connected App creation across all orgs. Summer ’26 tightens the enforcement further. If your org has Connected Apps that have not been migrated to External Client Apps and your integration depends on them, this is the release where that becomes an active problem rather than a pending one. The Connected Apps that require action are the ones your org created and manages. Managed package apps from vendors are not affected. X (Twitter) Auth Provider callback URL change If your org uses X (formerly Twitter) as an OAuth provider for login or integration, the callback URL configuration requires manual reconfiguration in Summer ’26. This is a small but breaking change for orgs that use it — it will not fix itself automatically. Find it in Setup under Auth. Providers. AI Content Summarizer component available in Lightning App Builder A new AI Content Summarizer component can be dropped onto any Lightning record page directly from App Builder without writing Apex. For admins who want to surface Agentforce value to end users quickly and without a full development engagement, this is the most accessible on-ramp in the Summer ’26 release. Salesforce Summer ’26 release notes ⚠ ECA enforcement tightens in Summer ’26 — what breaks if you skipped Spring ’26 prep Spring ’26 change New Connected App creation was disabled across all orgs by default. A Salesforce Support request could re-enable it — temporarily. Summer ’26 change Enforcement tightens further. The Support workaround is being phased out. Orgs with unmigrated Connected Apps face an increasing compliance and functionality risk. What breaks Integrations that depend on Connected Apps you built and manage — not managed package vendor apps — will face disruption if migration is not completed. Managed package apps are not affected. Action needed Open App Manager → filter by Connected App type → identify apps your org created → confirm migration status. Apps not yet migrated need to move to External Client Apps before enforcement completes. Have questions about anything in the Summer ’26 release notes that could affect your org? That is exactly the kind of thing our team digs into every release cycle. Reach out through truesolv.com. Follow us on LinkedIn for weekly Salesforce release breakdowns.
TDX 2026 Salesforce Recap
Salesforce co-founder Parker Harris asked the question right before TDX 2026: “Why should you ever log into Salesforce again?” What got announced on April 15 in San Francisco was a structural redesign of how the entire Salesforce platform works. Here is the short version of everything that actually matters. 🌐 Headless 360Platform as API Every Salesforce capability is now an API, MCP tool, or CLI command. AI coding agents can build and act in your org without a browser. GA at TDX 60+ new MCP tools · 40% dev cycle time reduction 🎛️ Agentforce Vibes 2.0Org-aware AI dev IDE Vibe coding with full org metadata awareness. Four modes: Agentic, Plan, Ask, Debug. Runs on Claude Sonnet, GPT-5, and open source models. Preview May ’26 Multi-model · Paid tier required 🔄 AgentExchangeAppExchange renamed AppExchange, Slack Marketplace, and Agentforce ecosystem unified into one AI-searchable catalog. One-click activation. $50M Builders Fund. GA at TDX 13,000+ solutions · 1,000+ agents & MCP servers 📋 Agent ScriptOpen-sourced Deterministic scripting language for AI agents — fixed rules + LLM reasoning in between. Full spec, parser, and compiler now on GitHub. Open source Compliance-readable · Agent Fabric integration Headless 360: the browser is now optional For most of Salesforce’s history, building on the platform meant working inside it — browser open, Setup menu navigated, page layouts configured. Headless 360 draws a line under that era. Every capability on the Salesforce platform is now reachable as an API, an MCP tool, or a CLI command. Sixty new MCP tools and thirty preconfigured coding skills shipped at launch. The practical implication is that AI coding agents can now build and act inside your Salesforce org without a browser open anywhere. Salesforce cited a 40% cycle time reduction for development workflows as an early benchmark. The DevOps Center MCP brings programmatic access into any CI/CD pipeline, and Natural Language DevOps lets developers describe what they want to deploy rather than configuring it step by step. Agentforce Vibes 2.0: org-aware AI development Most AI coding tools write code that looks correct but does not know what objects, fields, profiles, flows, or integrations exist in your specific org. Agentforce Vibes 2.0 solves that. It uses the Salesforce Unified Catalog to provide context-aware suggestions from the first prompt. Four work modes ship with Vibes 2.0. Agentic mode for autonomous task completion. Plan mode for back-and-forth review before any code is written. Ask mode for questions about how the org or its code works, without triggering changes. Debug mode for inspecting what is happening in production and proposing a fix before applying it. Multi-model support is included: Claude Sonnet, GPT-5, and open source models. For organisations with model commitments or data residency requirements, that is material. Vibes 2.0 enters preview in May 2026. The free tier is being removed; a paid subscription is required. AgentExchange: one marketplace for everything AppExchange launched in 2006 and became the marketplace that nearly 90 percent of Salesforce customers used to extend the platform. It just became AgentExchange. The rename reflects a structural consolidation: AppExchange, the Slack Marketplace, and the Agentforce ecosystem are now unified into a single AI-searchable catalog. Ten thousand Salesforce apps, 2,600 Slack apps, and over 1,000 agents and MCP servers from partners including Google, DocuSign, and Notion now live in one place. One-click activation replaces the previous multi-step install process. A $50M Builders Fund provides investment, engineering support, and go-to-market backing for ISVs and partners building in the new ecosystem. Partner results from the announcement: DocuSign cut time to signature by 60 percent after listing on the new marketplace. Notion reduced its average sales cycle from four months to three weeks. Agent Script goes open source Agent Script is the scripting language Salesforce built to solve a specific problem: AI agents are probabilistic. They reason their way through scenarios and can arrive at unexpected outcomes because that is how LLM reasoning works. For enterprise deployments, that unpredictability is often a blocker. Agent Script adds a deterministic layer on top: you define the fixed logic and the LLM handles the reasoning in between the defined steps. At TDX 2026, Salesforce open-sourced the full specification, including the parser and compiler, on GitHub. The open-source move is a platform bet. Salesforce is inviting the broader developer ecosystem to build agent authoring tools on top of a shared language specification rather than a proprietary SDK. Furthermore, it makes Agent Script readable and auditable by compliance teams who do not write code. “Why should you ever log into Salesforce again?” Parker Harris, Salesforce Co-Founder Said before TDX 2026 — not a provocation, but the product roadmap. Every Salesforce capability is now reachable as an API, MCP tool, or CLI command. What this means for your org right now The honest answer is: less than the announcement energy suggests, and more than you can safely ignore. For orgs that are not yet using Agentforce at all, TDX 2026 reduced the distance between a prototype and a deployed agent. The infrastructure, APIs, MCP tools, Agent Script, a governed marketplace, is now in place. The question is no longer whether you can build on it; it is whether your org’s metadata, data quality, and team readiness support doing so reliably. For orgs already running Agentforce in production, Headless 360 and Agent Script are the most immediately relevant announcements. Headless 360 changes how integrations and CI/CD pipelines interact with the platform. Agent Script changes how you define and govern agent behavior at scale. Role Most relevant TDX announcement What to do now Salesforce Admin External Client Apps enforcement tightening in Summer ’26 alongside the sandbox upgrade. AgentExchange consolidation changes how you install managed packages. Act now Audit Connected Apps before May 9. Review AgentExchange for any solutions your org has been looking at. Developer Headless 360 ships 60+ MCP tools and enables AI coding agents to work directly inside Salesforce orgs. Agentforce Vibes 2.0 previews in May with org metadata awareness and four work modes. Plan for Assess your metadata hygiene — Vibes
How to Use GEO in Salesforce Experience Cloud
SEO is not dead, but it has a new layer on top of it. Spring ’26 added Generative Engine Optimization to Salesforce Experience Cloud — a single toggle in Experience Builder that tells AI engines like ChatGPT, Perplexity, and Gemini how to read your portal content directly from the source. If your customers are starting their searches in AI chat instead of Google, this matters more than you might think. Here is what the feature does, how to turn it on, and which types of Salesforce sites benefit most. What Generative Engine Optimization actually does When a user asks ChatGPT or Perplexity a question about your product or service, the AI engine looks for publicly available content to ground its answer. If your Experience Cloud site is not set up to accommodate that process, the engine either ignores it or generates an answer from indirect sources — which may not reflect your current content accurately. GEO changes that by allowing AI bots to request a structured content snapshot of your public site pages. The snapshot gives the AI a clean, source-verified version of your content to work with, rather than a cached or scraped approximation. The result is that your portal becomes citable: when someone asks an AI assistant a question your help center or community site answers, there is a higher chance the answer comes from your actual content. This is the core difference from traditional SEO. Traditional SEO tells Google’s web crawler how to index your page for search ranking. GEO tells AI language model crawlers how to read and reference your page when generating answers. Dimension Traditional SEO GEO Target audience Google, Bing, and other traditional search engine crawlers AI-powered answer engines: ChatGPT, Perplexity, Gemini, Google AI Overviews Goal Rank higher in search results pages Be cited accurately in AI-generated answers Core mechanism Crawlable HTML, meta tags, backlinks, structured data, page speed Structured content snapshots that AI bots can request and process What it optimises for Click-through from a results list Accuracy and attribution when the user never sees a results list Where users see the result A link in a list of search results they click through An answer that cites your content directly in the AI interface Requires publishing Crawled on Google’s schedule, not yours Snapshot reflects your content as of the last site publish How to enable in Salesforce SEO settings: page title, meta description, canonical, sitemap Experience Builder → Settings → SEO → enable GEO toggle → republish Replaces the other? No — parallel tracks for parallel channels. Both are worth managing. Where to find the toggle and how to enable it The GEO setting lives in Experience Builder under the SEO settings panel. The path is: Experience Builder → Settings → SEO → Provide content snapshots of public site pages when requested by AI bots Enable the toggle, then republish the site. The setting takes effect on the next publish. It applies to both Aura and LWR sites and is available in Enterprise, Performance, Unlimited, and Developer editions. There is no additional configuration required at the page level. The toggle works across all public-facing pages on the site. Pages behind authentication are not included — GEO only applies to content that is publicly accessible without a login. How to Enable GEO in Experience Builder Spring ’26 — 3 steps 1 Open your Experience Cloud site in Experience Builder Navigate to the site you want to update. You need Admin access or a profile with Experience Cloud site management permissions. Setup → All Sites → Builder 2 Go to Settings → SEO and enable the GEO toggle In the left panel, open Settings. Select SEO. Find the option labelled “Provide content snapshots of public site pages when requested by AI bots” and enable it. Settings → SEO → AI bots toggle → ON 3 Publish the site The GEO setting takes effect on the next publish. Click Publish in Experience Builder to apply the change. The setting then applies to all public-facing pages on both Aura and LWR sites. Publish → Confirm Available in Enterprise, Performance, Unlimited, and Developer editions. Applies to public pages only — authenticated content is not included. What a content snapshot actually is A content snapshot is a static HTML version of your page that AI crawlers can request and process. It is optimised for machine reading rather than browser rendering — it strips out the dynamic elements, JavaScript-rendered content, and navigation chrome, and returns the core textual content of the page in a clean format. For AI engines, this is more reliable than attempting to crawl a JavaScript-heavy page where the main content only appears after client-side rendering. Furthermore, it means the snapshot reflects what is actually published in your Salesforce CMS, not a cached version from weeks ago. The practical implication is accuracy. If your help center article says your product supports a specific integration, the snapshot contains that exact statement. The AI engine citing your content has a verified source, rather than a reconstructed one. Which Salesforce portals benefit most from enabling GEO Which Salesforce Portals Benefit Most from Enabling GEO Public pages only 📖 Self-service help centers and knowledge bases Articles, FAQs, and troubleshooting guides are exactly the content AI engines look for when answering product questions. GEO makes your help content the cited source instead of a paraphrased approximation. Highest impact 🤝 B2B partner portals with public documentation Product docs, integration guides, and pricing pages are actively searched by B2B buyers using AI research tools. A GEO-enabled portal appears in that research process; one without it does not. High impact 💬 Community sites with publicly visible content Community answers to product questions are high-value for AI engines because they reflect real usage. If your community is publicly viewable without login, GEO makes that content accessible in the right format. Good candidate 🏢 Customer-facing product or service information sites Any Experience Cloud site where prospects or customers look up your features, plans, or support
Connected Apps Are Being Retired in Salesforce
Starting with Spring ’26, Salesforce disabled the creation of new Connected Apps by default across all orgs. Your existing ones still work for now. But the direction is clear: External Client Apps are the future, and the clock is running. This guide covers what changed, why Salesforce made this move, what External Client Apps actually give you, which apps are and are not affected, and a step-by-step migration walkthrough through App Manager. The second half is a structured checklist for the audit before you migrate and the testing after. The TLS certificate changes happening in the same release are covered at the end, because both come from the same security-first motivation. Spring ’26 Migration Timeline & TLS Certificate Phase-Down Connected Apps → External Client Apps 1 Winter ’26 New Connected App creation disabled by default in new orgs Opt-in 2 Spring ’26 New creation disabled across all orgs — Support request required Enforced 3 Summer ’26 Expected enforcement deadline — plan migration before this Deadline 4 Summer ’26 Triple DES for SAML SSO stops working completely Hard Stop TLS Certificate Lifespan Phase-Down (CA-signed certificates only) A Until Mar 14, 2026 Max lifespan 398 days (previous standard) B Mar 15, 2026 Max lifespan drops to 200 days Now C Mar 15, 2027 Max lifespan drops to 100 days Plan for D Mar 15, 2029 Max lifespan drops to 47 days — automation required Automate Why Salesforce is making this change Connected Apps have been part of Salesforce for over a decade. If you have ever set up OAuth for a third-party integration, configured Data Loader, or connected a custom web application to the Salesforce API, you have used one. They are everywhere, and most of them work fine. The problem is not the apps that are configured properly. The problem is the ones that are not, and the architecture that makes unsafe configurations easy to create. By default, Connected Apps allow any API-enabled user in an org to self-authorise a connection to an external application, without admin approval. That is how phishing and vishing attacks that targeted Salesforce orgs worked: trick a user into authorising a malicious Connected App, and the attacker has API access to the org’s data. Salesforce responded by tightening this behaviour, but the structural issue remained. External Client Apps take a different starting position. They adopt a closed security posture by default. Access is not granted unless an administrator explicitly permits it. Furthermore, the architecture separates developer configuration from admin policy, which means a developer building an integration cannot inadvertently override security settings that the admin put in place. What changed in Spring ’26, specifically The rollout has been gradual. In Winter ’26, Salesforce disabled Connected App creation by default in new orgs, with an option for admins to re-enable it manually. Spring ’26 tightened that further: new Connected App creation is now disabled across all orgs, including existing ones. Getting the ability back requires a Salesforce Support request, and Salesforce has been clear that this option will eventually disappear entirely. Two categories of Connected Apps are not affected by this change. Connected Apps created as part of a managed package continue to work and can still be created in that context. Connected Apps used for Slack in the legacy Agentforce Builder are also excluded. Everything else follows the new default. Any new integration from Spring ’26 onward must be built as an External Client App. ⚠ What happens if you try to create a new Connected App without a Support request The New Connected App button no longer appears in App Manager — the option is gone from the UI entirely. Attempting to create one via the Metadata API returns an error. There is no workaround inside the platform. Any new integration built after Spring ’26 that requires its own OAuth client must use an External Client App instead. If a specific business case genuinely requires a new Connected App, you must open a Salesforce Support case and explicitly request the capability. Salesforce may or may not grant it, and this option will be removed in a future release. What External Client Apps offer that Connected Apps do not External Client Apps are not just Connected Apps with a new name. The differences are architectural, and several of them matter a lot depending on how your org is set up. Separation of developer settings and admin policies In a Connected App, the developer configuration and admin security policies live in the same record. A developer with edit access to the Connected App can change the OAuth scopes, the IP restrictions, and the session policies. In an External Client App, those roles are separated. Developers manage the technical settings; admins manage the access policies. Neither can override the other without the appropriate permission. For ISVs and AppExchange partners, this matters enormously. It means the admin installing your package can control how it behaves in their org without touching the underlying app configuration. Second-generation packaging support External Client Apps are designed specifically for second-generation packaging, or 2GP. Connected Apps technically work with 2GP, but the process required manual steps that were fragile and time-consuming. ECAs package cleanly, distribute correctly, and integrate naturally with source control and CI/CD pipelines via the Metadata API. For admins managing integrations rather than building packages, the practical difference is that ECAs behave more predictably in sandboxes and scratch orgs. Scratch Org support for External Client Apps was added in Spring ’26, which makes the developer testing cycle considerably cleaner. Closed security posture by default A new External Client App is not accessible to any user until an administrator explicitly grants access. There is no self-authorisation pathway by default. This is the core security difference from Connected Apps, and it is the reason Salesforce is moving in this direction. What ECAs do not yet support Two important gaps remain. External Client Apps do not support the Username-Password OAuth flow. If any of your existing Connected Apps use this flow, you cannot migrate them
Agentforce Sales 2026 Is Live: What Every Director Needs to Know
Saleforce just gave every sales rep a digital coworker that never sleeps, never forgets a follow-up, and never loses a lead.
Salesforce Spring ’26 release top features by TrueSolv
Spring 26 is the kind of release that changes Monday morning operations more than it changes your homepage for good. We at TrueSolv noticed fewer gaps between intent and execution, stronger defaults around integrations, and better tools to keep automation and data governance under control. The fastest way to get value is to treat Spring 26 as a portfolio of operational upgrades. Pick a few that reduce friction for revenue and service teams, pick a few that reduce risk for security and integration owners, then make them part of your quarterly delivery plan. Here’s top new features that we found the most interesting and useful so far. Sales Cloud and revenue teams Sales Workspace plus account and prospecting enhancements Sales Workspace is a new hub that brings together guidance, analytics, and execution so reps spend less time hunting for context. Account Management and Prospecting updates focus on keeping accounts current and keeping pipeline full, including prioritized prospects visible in CRM and Slack. Engagement improvements with review controls Engagement Enhancements add the Review Before Send workflow and the ability to send emails from a seller’s address, which is useful when you want scale without letting automation send risky messaging unchecked. Revenue Management improvements Spring ’26 also brings updates across revenue related capabilities such as omni channel selling enhancements and billing service assistance, aimed at reducing manual handling of routine billing questions and quote flows. Service operations Proactive service and signal based management Proactive Service is designed to catch issues earlier and scale resolution guidance before escalation. Customer Signals in Command Center brings monitoring into the place where service leaders already manage operations. Knowledge upkeep that does not rely on hero admins Self Learning Knowledge analyzes service interactions to surface knowledge gaps and suggest updates, so the content stays usable as your support volume and channels grow. IT service starter pack The IT Service Domain Pack includes customizable agents, 100 plus workflows, and 100 plus service catalog items, which can shorten time to value for IT service management patterns. Data 360 and enterprise search Faster path from connection to activation Agentic Setup and Data Management is positioned to orchestrate the Data 360 pipeline with suggestions and more guided setup, aimed at speeding up connection to activation while maintaining control. Data lineage you can actually use in governance conversations Salesforce Unified Lineage provides a visual view of data movement and dependencies from source to activation, which helps when metrics change and leadership asks where the number came from. Enterprise Search and connector expansion Agentic Enterprise Search is designed to surface information across the enterprise from inside the CRM search bar. Data 360 Connector Enhancements include Zero Copy connectors for live warehouse data and connectors for unstructured sources like Box, Guru, YouTube, and Confluence. Security and integrations New Connected Apps creation restricted by default Starting with Spring 26, creation of new Connected Apps is disabled by default. Salesforce is steering new inbound integrations toward External Client Apps. Existing Connected Apps continue to function, but your integration governance model needs an update. What leaders should take from this This is not a UI tweak. It changes how new vendors, internal tools, and partner systems will authenticate going forward, and it forces a healthier inventory of who has access to what. The Salesforce architecture guidance frames this as a security and stability modernization, alongside reducing legacy authentication patterns. What this changes for your business Faster execution in core workflows. Sales and service features focus on removing manual steps and tightening operational loops. Better control over risk. Connected Apps restrictions and security modernization reduce the surface area of unmanaged integrations and legacy auth. Cleaner governance conversations. Unified Lineage and export disclaimers make it easier to answer the two questions leadership always asks, where did this number come from and how do we prevent data mishandling. How to find and enable the key items Start with release readiness and Release Updates Use Setup and search for Release Updates to review items that need preparation or testing in sandbox before enforcement. Enable Error Console Go to Setup, then User Interface, then enable the Error Console option for Lightning Experience error reporting. Add report export disclaimers and dashboard table alignment Go to Setup, then Reports and Dashboards Settings, enable the custom disclaimer for exported reports, and enable applying report settings to dashboard tables. Turn on Sales Workspace Sales Workspace can be turned on from Salesforce Go accessed via the gear icon, then search for Sales Workspace and complete the guided steps. Plan External Client Apps for new inbound integrations In Setup, search for External Client Apps and review External Client App Settings. Salesforce documentation indicates turning on the Allow creation of connected apps setting when needed, while shifting new integrations toward External Client Apps. Use Named Query API where standard queries keep getting rebuilt In Setup, go to Integrations, then Named Query API, define the query, and use the REST resource documentation for external consumption. To make Spring 26 pay off, pick a handful of changes, roll them out with ownership, and measure the impact the same way you measure revenue and service outcomes. We share practical release breakdowns, implementation tips, and short playbooks for Salesforce leaders across our channels. Follow TrueSolv on our social media to learn more about how to make your Salesforce work for your profit. And if you want to feel more confident with your Salesforce we at TrueSolv ready to help you, just drop us a message and we’ll contact you.
Salesforce Code Builder – New Productivity Tools
Salesforce announced new tools for developers and admins that can help to innovate faster than ever by building scalable, modern apps through a combination of clicks and code without ever having to sacrifice user experience or crucial security measures. Code Builder Code Builder is a web-based development environment fully optimized for Salesforce development and powered by Microsoft’s Visual Studio Codespaces. Code Builder is a full-featured version of Visual Studio Code running completely in the browser and backed by a powerful cloud-hosted developer environment. In just one click, you have a full environment without any setup or configuration. Code Builder comes with everything you need to build applications on the Salesforce Platform: Including Salesforce Extensions The Salesforce CLI Git integration It’s authenticated to your current Salesforce org. Every instance of Code Builder is backed by its own powerful Virtual Machine. This means Code Builder will allow you to do everything from simple code edits to Lightning Web Component development and advanced Apex debugging. Salesforce Functions Salesforce Functions is a service that lets developers write code that integrates with their data and events on the Salesforce Platform, and run it on-demand with elastic scale in a serverless environment. It empowers development teams to focus on delivering apps and business logic fast, instead of managing infrastructure. To accelerate app building, developers have the flexibility to innovate using languages they already know. They can quickly build, test, and debug Functions locally using the Salesforce developer tools. Admins or other users can extend their business processes by calling Functions from existing Apex code or low-code tools like Flow or even distribute them as part of AppExchange packages. DevOps Center DevOps Center allow admins and other declarative developers build against source control, collaborate better with programmatic developers, release apps faster, and do so with modern workflows like continuous integration and delivery. DevOps Center allows organizations to continue to prioritize release velocity, simplifying how apps are progressed through development environments from concept to launch, and boosting both the speed and quality of deployments. And since DevOps Center allows you to develop in your traditional sandboxes, you can also take advantage of additional capabilities like Data Mask that anonymize sensitive data in your testing environments — delivering speed without sacrificing trust. Code Builder Features Lightning Web Components Developers can now write, debug, and deploy LWC directly from the browser. Code Builder provides modern development features like code completion, inline documentation, refactoring, linting, and much more. Apex With Code Builder you can do everything in the browser, including using the rich Apex debugging capabilities. Org metadata Code Builder provides access to the full metadata of an org. Using the Org Browser you can open any metadata type for inspection and editing. Once you make changes to your metadata, the change is saved instantly to your org. Application Lifecycle Management Code Builder allow you to connect or create multiple orgs This means that it isn’t limited to the simple editing of org metadata. You can use it to script deployments between multiple orgs and test changes in scratch orgs. SOQL queries SOQL Query Builder allow you to write and execute SOQL queries with an easy to use graphical interface while also allowing for editing the query syntax directly for more advanced features. A powerful developer environment Code Builder is a powerful cloud-hosted developer environment. You can access the command line to run tools like the Salesforce CLI and save files to the disk which are persisted for the next time you come back. Code Builder is in Pilot June 25, 2020 with a limited group of customers. If you’re interested in learning more, please reach out to your Account team at Salesforce. If you’re interested in our articles, follow us on the Linkedin page.
10 helpful Salesforce Summer ’20 Features
In accordance with the current situation in our life, everything has slowed down. Salesforce, being on the crest of the wave, delivers new features on time. Here are 10 things that I think are particularly interesting.
Modify Fields Onsubmit In Lightning Record Edit Form
Problem Sometimes you need to execute code before submitting the form and set or modify some fields on sObject. For example, you have the following lightning-record-edit-form for Account sObject. Solution To modify some fields you can use onsubmit handler. You can get created/updated sObject from the event object. After the modifications, you need to submit the form. I and our TrueSolv team can help you with any questions related to Salesforce custom development. Contact us.
