As has become my tradition, here are my Summer '25 release highlights - one last look back before Winter '26!
- Refresh individual dashboard components: Have you noticed the new little round arrow in the top right corner of every dashboard component? This now lets you refresh individual components. Could be helpful if one component’s data changes more frequently than the rest of the dashboard - please let me know your use cases.
- List View improvements - did you notice that when you wrap text, the header now wraps, too? (Huge improvement!); some Long Text Area fields are inline editable; Lookup fields render as hyperlinks; Accessibility improvements. There are other minor changes to list views, as they now work via LWC, rather than Aura component.
- Dynamic Related Lists previously worked only on desktop - now also available for Mobile. (IdeaExchange Idea delivered). These let you filter (AND only), name, choose list or tile (max 4 fields), max records to show, and more.
New Nonprofit Cloud (NPC):
(These are in the next generation of Salesforce for nonprofits - not for NPSP):
4. Volunteer Management data model. Automation and other features coming in future releases.
5. Planned Giving functionality https://help.salesforce.com/s/articleView?id=release-notes.rn_fundraising_new_changed_objects.htm&release=256&type=5
So many Flow enhancements:
6. UI changes: Copy, Cut, Delete, and Fault Path actions on “⋮” menu on each element; descriptions moved to an info bubble that appears when you hover over the element; single click on a component to open its configuration panel; zoom level is preserved when selecting elements (preventing unexpected zoom resets)
7. Debugging results can now be filtered and searched; copy debug log to clipboard; summary on each element; panels can be expanded up to 80% width so more fits on the screen
8. Better experience for configuring Send Email Action
9. Get related records within a Get Records element (previously had to use loops and additional Get Records elements to gather related records)
10. “Time” data type now supported
11. In the Configuration Panel for any Action or Subflow element, see what the outputs will be in the new View Output Resources section; hover to see output’s name, label, type, and description.
12. Better UI for putting callouts to external systems in a Record Triggered Flow on asynch path
13. Tab out of picklist choice, see “pill” showing picklist label instead of API name.
14. “Expand Search” in resource picker component (beta)
15. For orgs paying for Einstein 1 or Einstein add-ons, admins can enter a natural language prompt, and Einstein can generate a flow. Einstein can also summarize an existing flow. Can also invoke an agent from flow (previously, agents could run a flow but flow could not invoke agents).
16. Flow Approval Processes are getting more and more functionality.
Screen Flows
17. Screen Actions: autolaunch subflow (beta in Spring ‘25, now GA) - on button click or automatically when events happen on the screen. New in GA version: Use conditions to limit when screen actions run and control whether it runs when screen is revisited https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screen_flow_screen_actions.htm&type=5
18. Add an SLDS icon for Choice Resources (not for Record Choice Sets, Picklist Choice Sets or collection Choice Sets). Also, add icons to Choice Lookups - one icon for each option.
19. Set “Preview Size” to “Medium” for modals or “Small” for mobile or utility bar. (Previously, to see how a component configuration would render in a smaller screen, had to debug or activate the flow for the other environment.
20. Directly control the width (out of a 12-column grid) and vertical alignment of multi-column layouts. (Control of sections was previously limited; components were not quite the same size.)
Other time-sensitive items:
21. “Salesforce for Outlook” is Being Retired in December 2027. If you are still using this, replace it with the “Outlook Integration”
22. Legacy (*.force.com) host names are being retired, and redirects are coming to a close in an upcoming release. To avoid disruption, start taking steps now.
23. API Versions 21.0 thru 30.0 are retired in Summer ‘25. Client applications API calls using API versions 21.0 thru 30.0 will fail. Upgrade them to the latest API version. (API versions 21.0 thru 30.0 were deprecated with the Summer ‘22 release, with retirement announced for Summer ‘23 release. Retirement was subsequently deferred to Summer ‘25 release.)
24. User Access Policies became GA in Summer ’24 - these let you auto assign (or revoke) permission set licenses, permission sets, permission set groups, package licenses, queues, and public groups based on criteria - for existing users or for users you create in the future. https://help.salesforce.com/s/articleView?id=platform.perm_user_access_policies.htm&type=5
See all the details on these and much more in the Release Notes (choose Summer '25 at top right):
https://help.salesforce.com/s/articleView?id=release-notes.salesforce_release_notes.htm&release=256&type=5For broader reach, you might want to start a new post for your question. My impression is that the alert will still be there even if there are no old host names. Unless Salesforce is tracking those redirects, it wouldn't know if they are still happening. And if there was a list, I would think they would share it. I'm thinking you need to think about any integrations you have - any forms on your website or tools that interface with Salesforce. If you've checked everything and it's all using your domain, then you may be good to go. But I'm not an expert. Please let me know if you learn something different!
