A practical framework for managing sandbox previews and testing quarterly Salesforce releases (opens in a new tab)
Readers will learn how to structure their quarterly release cycle using targeted sandbox strategies, filtered release notes, and systematic testing to prevent production issues.
Salesforce ships three releases a year, and the article argues that release readiness should become a routine habit rather than a scramble. It explains the feature lifecycle: Pilot features go to a small opted-in group, Beta features are broadly available for testing with limited support, and Generally Available features are formally part of the release. The author stresses that admins act as product managers for their org, deciding whether to adopt, wait on, or flag each feature. The recommended routine has four steps: plan and learn, get hands-on, test, and communicate.
The planning step covers tracking key release dates, completing the Release Trailhead module, and getting into a pre-release org early. During the roughly four-week sandbox preview window, the author advises keeping a mix of preview and non-preview sandboxes, with non-preview sandboxes forming the deployment path to Production. Deploying from a preview sandbox straight into non-preview Production is the path to avoid, because new metadata such as permissions may not exist there yet and deployments fail. Release Notes are too long to read in full, so the author suggests filtering them with AI tools while keeping a human check on the results, and reviewing Release Updates in Setup well before their enforcement dates.
The hands-on step means exploring features in a pre-release org or preview sandbox, involving power users early, and identifying configuration prerequisites such as page layouts and field-level security. The testing step calls for regression testing in preview sandboxes, ideally with automated tools, verifying suspected bugs in non-preview sandboxes, and opening Salesforce Support cases when problems are confirmed. The author also recommends evaluating new features for business value and compatibility with existing customizations. The final step is communication: sharing knowledge with admins and developers through sessions, preparing training and in-app guidance for users, and meeting people where they already work. The article closes by advising readers to improve one weak step each release.
Read the original at Salesforce Admins Blog (opens in a new tab)