# Winter '26 Abridged

---

The [Salesforce Discord Collective](https://join.sfxd.org) Presents:  
**[THE WINTER 26 RELEASE NOTES - ABRIDGED](https://cloud.bessereau.eu/s/EAiDxP86zjN3jwF/download/BlendSalesforce.mp4)**  
RELEASENOTES\_Redacted as the Summary was not found in the Summary Allowlist

---

**CRITICAL STUFF**

- Honestly [nothing](https://thejoywithin.org/wp-content/uploads/2019/06/how-to-be-at-peace-with-myself.jpg) for most users. [Good news](https://static.wikia.nocookie.net/enfuturama/images/4/46/Crimes_of_the_Hot_%28Main_Episode%29_-_87.png/revision/latest?cb=20211005090155) !
- Avoid users getting weird warnings, and potential dysfunctions, by [updating your Referrer Policy](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_other_update_referrer_policy.htm&release=258&type=5). Because who doesn’t love a good surprise [warning](https://www.osha.gov/sites/default/files/inline-images/types_16.jpg) popup?
- For the rare customers who use Bring Your Own Channel, [Breaking Changes require you to update stuff](https://help.salesforce.com/s/articleView?id=release-notes.rn_messaging_byoc_bitvector.htm&release=258&type=5). All three of you, consider yourselves warned.

**GENERAL STUFF**

*Is big this release because lots of sections were too small to stand alone*

- Setup pages get hosted behind the new [salesforce-setup domain](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_allow_setup_domain.htm&release=258&type=5) in Prod orgs starting this release. This shouldn’t be a problem because you’ve had a year to test and review that your IT doesn’t block said domain. (You did test this, [right? Right?](https://www.youtube.com/watch?v=WLh8F6lAooA)). As long as you’re at it, you might want to check the [Cloudfront URLs as well](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_lex_cdn_cloudfront.htm&release=258&type=5) who [took over from Akamai two releases ago](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_lex_cdn_cfront.htm&release=254&type=5)
- If your data loader isn’t working after r 2, it’s probably because [they deactivated Device-based auth](https://help.salesforce.com/s/articleView?id=release-notes.rn_data_loader_oauth_change.htm&release=258&type=5) due to all the connected app attacks. Update to the new DL version [from github](https://github.com/forcedotcom/dataloader) (lol, such a great place for enterprise software - at least Microsoft owns it now so it’s *technically* enterprise?) and use a User-based auth flow
- [Permission Set Licenses get removed automatically after unassigning a related Permset/Group](https://help.salesforce.com/s/articleView?id=release-notes.rn_permissions_psl_unassign.htm&release=258&type=5)\* (\* conditions apply. User Access Policies still irrelevant due to shortcomings.)
- The Role and Subordinates thing has either changed or has now been edited to indicate that [the Role and Internal Subordinates nomenclature happens even in new orgs as soon as you turn on Experiences](https://help.salesforce.com/s/articleView?id=release-notes.rn_sharing_secure_roles_enforced.htm&release=258&type=5). I stupidly thought they were just replacing the old one with this, but no, now you have [a nice little cleanup](https://en.wikipedia.org/wiki/Spring_cleaning) to do before you start your experience cloud project. Neat ! :-(
- External Client Apps get [Push and Mobile](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_external_client_apps_mobile_notifications_push_plugins.htm&release=258&type=5) features, [Credential Rotation](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_stage_rotate_eca_credentials.htm&release=258&type=5)
- Verification Link Expiration [no longer prevents user from setting up password after initial click if it’s re-clicked within 7 days](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_password_reset_issue.htm&release=258&type=5) which has [happened to me wayyy too often](https://www.google.com/search?q=shame+bell&uact=5#fpstate=ive&vld=cid:ceee177e,vid:1GiPcP30cFc,st:0)
- They changed the Setup home page to <s>make you more efficient</s> [recommend features and tasks for which you *totally have licences for* ](https://help.salesforce.com/s/articleView?id=release-notes.rn_customization_general_setup_home.htm&release=258&type=5).
- List views can now be sorted by [multiple columns](https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views_multi_column.htm&release=258&type=5) (GA from Beta), get [Keyboard-friendly aids to edit them faster](https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views_type_ahead_search.htm&release=258&type=5)
- Field history tracking gets better [compliance support](https://help.salesforce.com/s/articleView?id=release-notes.rn_customization_fht_enhancements.htm&release=258&type=5) and is available for the [User object](https://help.salesforce.com/s/articleView?id=release-notes.rn_field_history_tracking_beta.htm&release=258&type=5) (beta)
- Metadata Deployments get [information about the deployment size](https://help.salesforce.com/s/articleView?id=release-notes.rn_meta_view_deployment_details.htm&release=258&type=5), presumably because they’ll [try to bill for large deployments in 2035](https://cdn.arstechnica.net/wp-content/uploads/2017/01/getty-money-party.jpg) or something, and also [metadata corruption is apparently a thing](https://help.salesforce.com/s/articleView?id=release-notes.rn_meta_new_deploy_states.htm&release=258&type=5). If you use Agents [the MDAPI name changes](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_topic_action_suffix.htm&release=258&type=5) so watch out lest you create duplicates.
- On the email side, [SFO is definitely retired in 2027](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_sfo_retiring.htm&release=258&type=5), as well as [Lightning Sync](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_ls_update_from_ews.htm&release=258&type=5) and [Activity360 Reporting/Metrics/etc](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_eac_reports_retire_prepare.htm&release=258&type=5). TL;DR "[use EAC](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_eac_migrate_to_sync_email.htm&release=258&type=5)", which gets [potential Contact/Lead suggestion](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_eac_potential_contacts.htm&release=258&type=5) from emails and a [threaded view](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_eac_email_threading.htm&release=258&type=5) which looks nice but isn’t available ([Soon™](https://media1.tenor.com/m/a7aeZxrntk8AAAAd/intensifies-sooning.gif)). On that note, Microsoft is retiring EWS, so [if you’re using EWS to sync, you need to migrate to Graph API](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_eac_update_from_ews.htm&release=258&type=5). The year is 2027 and [we’re still figuring out email sync](https://i.redd.it/0hyqoqd7473a1.png).
- Experience Cloud LWR sites can be [upgraded to Enhanced LWR](https://help.salesforce.com/s/articleView?id=release-notes.rn_experiences_lwr_upgrade.htm&release=258&type=5) which sadly removes the `/s` from the URL, so you won’t be able to know by URL only if a site’s on SF. Press S to pay respects.
- Forecasting on Opportunity Line Item Splits is now possible [if you have a ServiceDate](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_forecasts_pipeline_oli_product_dates.htm&release=258&type=5) on the OLIS, and Consumption Forecasting [now doesn’t force a Gregorian calendar](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_forecasts_consumption_custom_fiscal_year.htm&release=258&type=5)
- Reports on Case Team Member can [now leverage Roles](https://help.salesforce.com/s/articleView?id=release-notes.rn_cases_case_team_member_reporting.htm&release=258&type=5) so you can see why people interact on cases.
- Cases get [Rich Text Comments](https://help.salesforce.com/s/articleView?id=release-notes.rn_cases_rta_case_comments.htm&release=258&type=5) which I’m sure will get gutted over the years as they realize people abuse images (can’t wait for the Comic Sans epidemic), and [Time to Next Milestone in List Views](https://help.salesforce.com/s/articleView?id=release-notes.rn_entitlements_prioritize_cases.htm&release=258&type=5) which is pretty great.
- [SLA Management replaces Entitlement Management with a new Setup](https://help.salesforce.com/s/articleView?id=release-notes.rn_entitlements_sla_simplification_ga.htm&release=258&type=5) which is good because Entitlements [sucked](https://tv.getyarn.io/yarn-clip/d64795f5-bcf2-4e16-a2db-6e9119235809/gif)
- Chat gets [in-chat video support](https://help.salesforce.com/s/articleView?id=release-notes.rn_messaging_video.htm&release=258&type=5), and [markdown support](https://help.salesforce.com/s/articleView?id=release-notes.rn_markdown.htm&release=258&type=5), probably linked to [more filetype support](https://help.salesforce.com/s/articleView?id=release-notes.rn_900_file_types.htm&language=en_US&type=5&release=258)
- Omnichannel gets [sorting directly in the Work Attribution box](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnichannel_search_sort.htm&release=258&type=5), and [abandoned Work Items](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnichannel_abandoned_work.htm&release=258&type=5) reporting to see when users got too frustrated and quit
- Dashboards get [localized Titles and Descriptions](https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_multilanguage_translation_reports_dashboards_labels.htm&release=258&type=5), [reference values display](https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_reference_line_dashboard_charts.htm&release=258&type=5), and [configuration based on Report Settings for tables](https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_retain_report_table_settings.htm&release=258&type=5). There’s also a setting to disable [formulas in exported reports](https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_disable_formulas_exported_reports.htm&release=258&type=5) to avoid “unintended code execution”… from the very complex formulas that are allowed in Salesforce… in your org… in your excel. Yes, someone tried to inject code via report formulas. No, we’re not surprised either.
- Tableau Next [still is a thing](https://help.salesforce.com/s/articleView?id=release-notes.rn_tua.htm&release=258&type=5) that is seeing so many updates that it’s obviously still “work in progress”
- Time-based Workflows [Now called Time-Based Automation](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_mgmt_time_based_automations.htm&release=258&type=5), RIP reference to outdated technology.
- [RIP in pieces, Optimizer](https://help.salesforce.com/s/articleView?id=004980242&type=1). One thing where GenAI could have actually said “yeah this is important to fix or not” and instead, it got killed because “the app’s original purpose was to help migration to LEX”, which is horseshit as it mostly reported on performance and best practice. Pour one out for our fallen homie.

**MARKETING**

- Marketing Cloud Next gets [mobile notifications](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_mam.htm&release=258&type=5), better [template and contentblock management](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_channels_msgs.htm&release=258&type=5), better [landing page configuration](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_channels_lead_gen.htm&release=258&type=5), [Sandbox support](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_sandboxes.htm&release=258&type=5) (lol I can’t believe this is a release note instead of just “yeah it’s the minimum acceptable feature” - imagine launching without sandbox support and calling it enterprise software), better [Identity Resolution](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_setup.htm&release=258&type=5), etc. If this seems like a lot, it’s because it’s brand new and as such getting all the love. We’ll see in roughly 2 years whether it’s actually become something great, or joined the list of[ stale-ass stuff that SF has forgotten](https://killedbygoogle.com/) like Pipeline Inspection, Einstein Automated Contacts, their promise that Agentforce uses anonymized data, or CPQ.
- Marketing Cloud Engagement (ex-ExactTarget) gets a [slew](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_journeys.htm&language=en_US&release=258&type=5) [of](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_whatsapp.htm&language=en_US&release=258&type=5) [minor](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_einstein.htm&language=en_US&release=258&type=5) [but powerful](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_query_optimizer.htm&language=en_US&release=258&type=5) [updates](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_automations.htm&language=en_US&release=258&type=5) which seem to indicate product involvement and upkeep, meaning that contrary to CPQ, you’re not scheduled for the thousand cuts yet.

**FLOWS**

- Quick reminder that you [really should set up via Permission Set who can run your Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_restrict_user_access.htm&release=258&type=5). Yes, we know you haven’t done this yet. No, we won’t stop nagging you about it.
- [Transaction Control](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_transaction.htm&type=5) means you can now force [new transactions](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_actions_transaction_control.htm&release=258&type=5) for callouts (at the cost of no more debugging tools - a small price to pay for… *checks notes* …being able to make callouts). Also default behavior from previous state has changed, so test all ya flows tyvm.
- You can now [Compare Versions](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_mgmt_compare_versions.htm&release=258&type=5) of Flows, bringing an easy way to debug why your “minor change” broke prod without having to stare at each element while your manager breathes down your neck asking “is it fixed yet?”
- Debug [continues to evolve](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_debug_improvements.htm&release=258&type=5) with some changes like the [positioning of the window](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_screen_flow_debugger.htm&release=258&type=5) needing adaptation, but makes for a more coherent viewing in general.
- [Flow Approvals now also support Debug](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_debug_flow_approval_processes.htm&release=258&type=5), [have a polling feature to get triggered from external systems](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_ext_sys_change_triggered.htm&release=258&type=5), have [more tolerant assignee picker](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_assignee_resource_type_changes.htm&release=258&type=5), support [groups and queues as firstapprovers](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_other_changes.htm&release=258&type=5)
- The Data Cloud Transformation modules [comes to normal Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_actions_transform_data_directly.htm&release=258&type=5) to map data to Actions
- The SendEmail component [groups the collection and single variable inputs into a single input](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_actions_send_email_recipient_version_changes.htm&release=258&type=5)
- Flow Approvals get [better Send for Approval Action](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_actions_request_an_approval_update.htm&release=258&type=5)
- Visually, the [Resource Menu](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_find_resources_faster_winter_26.htm&release=258&type=5) has changed, presumably to have a more unified experience with the new Debug modules, and [focused items are now highlighted in Blue](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_easily_track_your_keyboard_focus_in_flow_builder_ui_elements.htm&release=258&type=5). You can also [preview Flows with Branding sets](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_preview_style_with_lightning_and_exp_cloud_site_branding.htm&release=258&type=5) and [style text better than before](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_make_text_in_display_text_components_accessible_with_paragraph_styles.htm&release=258&type=5), also [images from static resources for beauty reasons](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_use_static_resource_images_in_display_text_components.htm&release=258&type=5)
- If you didn’t like [Assigning variables to sObject variables before create](https://developer.salesforce.com/docs/atlas.en-us.salesforce_vpm_implementation_guide.meta/salesforce_vpm_implementation_guide/vpm_designer_resources_sobject_variable.htm), [you can now reference the Create Records as a sObject variable after it has run](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_access_new_records_immediately.htm&release=258&type=5) which will lead to errors if you don’t factor that in while updating API versions. Update your API versions, you cowards!
- The DOGE from last release now becomes useful - if you [get with related objects](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_get_related_records.htm&release=256&type=5) you can now use those related objects to do [nested FOR loops without extra GETs](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_get_related_records_nested_loops.htm&release=258&type=5) which was previously hard to do.
- You can now create LEX pages for [Flow Objects](https://help.salesforce.com/s/articleView?id=release-notes.rn_lab_salesforce_flow_record_page_layout_updates.htm&release=258&type=5) just like [for other objects](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_new_lab_salesforce_flow_default_record_pages.htm&release=258&type=5), including components such as the [Orchestration](https://help.salesforce.com/s/articleView?id=release-notes.rn_lab_view_details_about_orchestration_runs.htm&release=258&type=5) one - hope specific components for stuff that should be modular won’t become a habit.
- Event-triggered Flows now allow you to trigger [when a File is attached to a Record](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_mfi_automate_flows_with_file_attachments.htm&release=258&type=5)
- [Persistent Logging](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_mgmt_persistent_logging.htm&release=258&type=5) means “shove your logs into Data Cloud so you can review them more easily” - I’m supposing this is “free because Foundations”, but not really *free*.

**FIELD SERVICE**

- Scheduling and Optimization gets a huge upgrade with [dynamic scaling](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_eso_dynamic_scaling.htm&release=258&type=5) solving [high-complexity schedules](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_complex_work.htm&release=258&type=5) previously being super annoying, better [travel-time management when breaks are factored in](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_eso_lunch_breaks.htm&release=258&type=5)
- Visual Remote Assistant now supports [four guests in a single call](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_vra_multiparticipant.htm&release=258&type=5) because what we needed was another slack replacement and [timestamps for notes](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_vra_bookmarking.htm&release=258&type=5)
- One LLM usage I actually like, Data Capture uses LLMs to have [Agents dictate meeting notes and fill fields automatically](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_258_data_capture_voice_to_form.htm&release=258&type=5)

**COMMERCE**

- [Unified Template](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_unified_template.htm&release=258&type=5) covers both B2B and B2C stores on a single codebase. I’m assuming this is why we get [parameter-based storefronts](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_shareableurl.htm&release=258&type=5) which sound cool but are also a tad old.
- Localized [Markets can now be done for B2B Internal Users as well as guests](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_marketsforb2bauth.htm&release=258&type=5), and Localized [Email Templates](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_multilanguageemailtemplates.htm&release=258&type=5) can be dynamically selected based on store locale. Also [Localisation doesn’t require you to copy paste the source text into the Source Language translation file](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_multiple_languages.htm&release=258&type=5) anymore.
- “We have a GitHub with ready-to-use component templates” was an easier [title than this](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_open_source_components.htm&release=258&type=5). Did the writer get paid by the word?
- You can now refund people to [a different payment method than the original](https://help.salesforce.com/s/articleView?id=release-notes.rn_om_unreferenced_refunds.htm&release=258&type=5)
- If you edited your Cancel Item flow previously, you might want to take [this new update allowing easier cancellation of eligible items](https://help.salesforce.com/s/articleView?id=release-notes.rn_om_cancel_all.htm&release=258&type=5)
- [Partial SKU Search](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_partial_sku.htm&release=258&type=5) allows people to find subgroups of products faster if you use logical grouping by SKU.
- You can now leverage [BACS, BECS, SEPA, and ACH via the Commerce API ](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_third_party_payment.htm&release=258&type=5)

**DEVELOPMENT**

- [CA cert lifetime changes impact Salesforce a bit (in 2027 for real impact)](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_certificate_lifespans.htm&release=258&type=5) - here’s to hoping this means we get CLI access to certs and rotations, or even letsencrypt support. (Narrator: They did not get letsencrypt support)
- Local Dev [gets better for single components](https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_single_component_preview.htm&release=258&type=5) and [updates on save for LWR sites](https://help.salesforce.com/s/articleView?id=release-notes.rn_experience_local_dev.htm&release=258&type=5)
- If you haven’t migrated to [SLDSv2](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds_updates.htm&release=258&type=5) yet, the [SLDS Linter](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds_linter_ga.htm&release=258&type=5) which you can [install from here](https://github.com/salesforce-ux/slds-linter) helps you find issues in your code and uplift your repo to v2. The [SLD Validator](https://marketplace.visualstudio.com/items?itemName=salesforce.salesforce-vscode-slds) will help you ensure you do good quality components from VSCode directly. ([now GA](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds2_ga.htm&release=258&type=5), and yes I just copypasted the last release because I didn’t feel like rewriting this). Also [DarkMOde ](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds_dark_mode.htm&release=258&type=5)and [density-aware components](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds_density_hooks.htm&release=258&type=5) for SLDSV2, [also usable in VF](https://help.salesforce.com/s/articleView?id=release-notes.rn_slds_visualforce.htm&release=258&type=5)
- A new [Tooling API Endpoint](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_tooling_unified_testing.htm&release=258&type=5) allows [Test (Apex and Flow) Execution and Retrieval](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_unified_testing.htm&release=258&type=5)
- Abstract and Override methods cannot be used in [private access modifiers](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_access_modifier.htm&release=258&type=5) anymore
- I’m psyched but surprised SF is letting this out the door what with the potential for abuse, but you can [create LWCs that leverage Local Actions (browser stuff)](https://developer.salesforce.com/docs/platform/lwc/guide/use-flow-local-actions.html) and [use those in Screen Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_lc_lwc_local_actions.htm&release=258&type=5). Can’t wait to see what creative chaos the community unleashes with this one.
- Speaking of Flows, if you do Invocable Actions, the new [Extension Metadata Type](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_extend_extended_metadata_invocable_action.htm&release=258&type=5) allows you to configure input order, group and visibility so your custom stuff looks good to Users. Also using [Where Actions are Used](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automation_app_action_hub.htm&release=258&type=5) allows you to find your custom actions in Flows across the org.
- [Lightning Out 2.0](https://help.salesforce.com/s/articleView?id=release-notes.rn_lc_lwc_lightning_out.htm&release=258&type=5) allows you to put LWCs and Flows in random websites ! Great stuff or DoA like Lightning Out 1 ? We’ll see !
- A good thing about AI is that it finally forced Salesforce to [care about structured Comments in Code](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_apexdoc.htm&release=258&type=5) which leads to this new standard so Agentforce can hallucinate good code based on your human-generated slop ;)
- External Services get [higher limits](https://help.salesforce.com/s/articleView?id=release-notes.rn_ext_services_limits.htm&release=258&type=5), [image/file support](https://help.salesforce.com/s/articleView?id=release-notes.rn_ext_services_binary_file_support.htm&release=258&type=5), made possible by [this change in how CD manipulation is handled in APEX](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_ext_services_binary.htm&release=258&type=5), but document upload size is still only 16MB.
- For Flows, you can now add [APEX-Defined Collections to DataTables](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_apex_support_screen_flow.htm&release=258&type=5). You already could in LWCs, but now it’s Flow-compatible.

**DATA CLOUD**

- You can get [Commerce Data even if from another org](https://help.salesforce.com/s/articleView?id=release-notes.rn_comm_datacloudone.htm&release=258&type=5) and [segment it into its own data space](https://help.salesforce.com/s/articleView?id=release-notes.rn_om_data_spaces_return_insights.htm&release=258&type=5)
- Using a "[DevOps Data Kit](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-deploy_data_kit_components.html)" ™ you [can migrate Data Cloud config from Sandbox to Prod](https://help.salesforce.com/s/articleView?id=release-notes.rn_cdp_2026_winter_deploy_production_hotfix_to_sandbox.htm&release=25) which is [also doable via CLI](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-deploy_data_kit_using_cli.html) (also using said data kit)

**AGENTFORCE**

- You can [Expose AuraEnabled methods to Agents](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_auraenabled_actions.htm&release=258&type=5) (depending on a your licensing scheme, requires some mulesoft api thing, hallucinations not guaranteed)
- Agents hallucinating URLs will now [send URL REDACTED to customers](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_agentforce_urls.htm&release=258&type=5) if you set up the URL allowlists, truly an experience that we all aim to deliver to our prized customers.
- Agents can now use custom display cards that SF calls [Lightning Types](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_clt.htm&release=258&type=5) so information looks better on screen.
- To help you debug an Agent, turning on [Session Tracing](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_session_tracing.htm&release=258&type=5) stores everything from engine decisions to actions in Data Cloud for review. Same stuff for [RAG Tracking](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_retrieval_quality.htm&release=258&type=5) to see how content is used.
- After getting SF Support to turn it on, you can use the [Generative KA](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_bots_knowledge_dialog.htm&release=258&type=5https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_bots_knowledge_dialog.htm&release=258&type=5) action to generate AI slop on demand within a Chat. Woooo.
- Salesforce gives you [more flexibility into where Models are run](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_models_azure_openai_disable_fallback.htm&release=258&type=5) and [which](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_models_amazon_nova.htm&release=258&type=5) [models](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_models_openai_o_series.htm&release=258&type=5) you run
- Flow [Agentforce decisions](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_use_dynamic_decisions.htm&release=258&type=5) are… not something I hate. I think it’s great for things where criticality is low-to-medium and a human will benefit from even data that is statistically not perfect all the time. [Structured Outputs](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_use_structured_output_with_custom_agent_actions.htm&release=258&type=5) also look nice, forcing Agentforce to answer into pre-configured objects in Flow.
- For Service, Agentforce [looks for similar cases](https://help.salesforce.com/s/articleView?id=release-notes.rn_sp_similar_cases.htm&release=258&type=5) via Semantic Search, and [quotes Knowledge Articles](https://help.salesforce.com/s/articleView?id=release-notes.rn_sp_citations.htm&release=258&type=5), will also [Ground itself in Chatter](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_case_feed_grounding.htm&release=258&type=5) (and will bug out if you don’t [assign a new permission set](https://help.salesforce.com/s/articleView?id=release-notes.rn_sp_release_update.htm&release=258&type=5) because enterprise users LOVE instability)
- Early Adopter’s curse: [Article Answers](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_bots_aa_retirement.htm&release=258&type=5) requires migration to Generative Knowledge Answers before Dec. 31st, otherwise no worky. As said in Deployments, [the API name of agent stuff changes as well](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_topic_action_suffix.htm&release=258&type=5) so you can update your repos to prevent chaos.
- Email handling Agents can now [Reply All](https://help.salesforce.com/s/articleView?id=release-notes.rn_email_reply_all.htm&release=258&type=5)

**DOGELAND**

- [:doge:](https://imgur.com/QyoMzOl) [Einstein Next Generation](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_generate_accurate_draft_flows_with_einstein_next_generation_beta.htm&release=258&type=5) can create draft flows that suck less, because the previous iteration was ass.
- [:doge:](https://imgur.com/QyoMzOl) [Spaghett](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_new_perms_for_managing_autolaunched_fap.htm&release=258&type=5)
- [:doge:](https://imgur.com/QyoMzOl) [Why don’t you just strip ZWSP](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_username_validation.htm&release=258&type=5)
- [:doge:](https://imgur.com/QyoMzOl) [If the case is Closed, our Agent can Close it for you ](https://help.salesforce.com/s/articleView?id=release-notes.rn_cases_close_case_agentforce_employee_agent.htm&release=258&type=5)! At least they found a way to make LLMs deterministic.

---

This abridged version was graciously written up by the **SF Discord**

We have a nice wiki: [https://wiki.sfxd.org/](https://wiki.sfxd.org/)

And a LinkedIn page: [https://www.linkedin.com/company/sfxd/](https://www.linkedin.com/company/sfxd/)

Join the ~18000 members in the most active chat-based community around Salesforce these parts of the web at [http://join.sfxd.org/](http://join.sfxd.org/)

---