Salesforce Winter’25 Release Notes | General Enhancements – Page 3 – Salesforce Training Articles & Latest News

Test Restrictions on Salesforce Cookie Use

To support users that block third-party cookies, prevent potential issues with custom functionality and code that use Salesforce session cookies to preview content, emails, products, and more while Salesforce updates those features for blocked third-party cookies by enabling the new My Domain setting, Allow cross-domain use of Salesforce cookies on the preview domain . This setting is enabled by default when My Domain setting Require first-party use of Salesforce cookies is enabled

Why: Chrome and other major web browsers block third-party cookies by default. Users can configure browsers to allow these cookies however, that practice can introduce security risks. Third parties can’t access Salesforce cookies directly. And when your Setup pages are served on the salesforce-setup.com domain, Classic pages can be loaded in Setup without an additional step. However, custom code or functionality that uses a Salesforce session cookie can still be affected when browsers block third-party cookies

How: To prevent third-party use of Salesforce cookies, from Setup , in the Quick Find box, enter My Domain, and then select My Domain . In the Routing and Policies section, click Edit . Enable Require first-party use of Salesforce cookies , and save your changes. Allow cross-domain use of Salesforce cookies on the preview domain setting allow features that use Lightning to frame the preview domain to work and is automatically enabled whenever the Require first-party use of Salesforce cookies setting is enabled

Important If the browser already blocks third-party cookies, both settings have no effect. Also, these settings only affect Salesforce cookies. To test calls from Salesforce that use a third-party cookie, including third-party applications embedded in Salesforce, disable third-party cookies in your browser

Add the New Setup Domain

Ensure that Setup pages in Lightning Experience load content correctly when browsers block third-party cookies. If your users have general access to the internet, no action is required. If your company controls users’ or servers’ access to the internet through firewalls or allowlists, your IT department must add *.salesforce-setup.com to the company’s list of allowed domains. Salesforce Setup pages are now hosted on that domain

When: Setup pages move to the *.salesforce-setup.com domain through a staggered rollout. The rollout began in Spring ’24 and continues through Summer ’24 and Winter ’25. The change is first enabled in sandboxes and nonproduction orgs, and then in production orgs

Create and Verify Your Default No-Reply Organization-Wide Email Address to Send Email (Release Update)

To comply with increased email security standards, orgs are required to create and verify a Default No-reply address in Organization-Wide Email Address settings

When: This update was introduced with Summer ’24 and Salesforce is scheduled to enforce it in Winter ’25. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab

Why: The verified Default No-Reply organization-wide email address is used to send emails from your org. This update allows increased accountability for email deliverability

How: In order to comply with increased email security standards, some emails will fail to be sent when lacking a customer defined Default No-Reply Organization-Wide Email Address

Verify Your Return Email Address for Sender Verification (Release Update)

After Spring ’25, to comply with increased email security standards, you’re required to verify the Email Address in My Email Settings

When: Salesforce enforces this update in Spring '25. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab

Why: A verified email address is used to send emails from your account. This update allows increased accountability and security for email deliverability

How: To comply with increased email security standards, emails fail to send from the return email address in My Email Settings until the address is verified. Instruct all users to visit their My Email Settings. Users can manually verify their email addresses by selecting Resend Verification Email and clicking the link in the email. If the resend option is unavailable, the return address is already verified. Users receive a verification email once per release until Spring ’25. The email includes the verification link

Get Flexible Access to Custom Apps with the Salesforce Platform Login License

The Salesforce Platform Login license allows you to assign access to custom apps built on Platform for internal users without the requirement to buy a seat-based license. With the Salesforce Platform Login license, you can pay per daily unique login for users who need infrequent or occasional access

Where: This change applies to Enterprise, Performance, Unlimited, and Developer editions

When: The Salesforce Platform Login license is available October 15, 2024

Inbound Email Limit Increased

The number of inbound emails that can be queued after the daily email limit is reached are now equal to the daily email rate limit. After this limit is reached, any inbound emails will bounce. Email services should be reviewed and Requeue Message failure response option should be used only for high-priority services

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Professional, Unlimited, and Developer editions

Why: For example, if you have 10 Salesforce licenses, you can receive 10,000 inbound emails before you reach your daily limit. When you reach that limit, additional inbound emails are queued for processing if the failure response option on the email service is Requeue Message. After 10,000 emails are queued, all additional inbound emails for that day bounce

Review Your Integrations for a Change to Email Handling

To comply with the latest Request for Comments (RFC) standards, the local-part of contact email addresses (part before the @ symbol) must be surrounded by quotation marks if that part contains invalid dots (more than one consecutive dot or a trailing dot)

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Professional, Unlimited, and Developer editions

How: This change preserves your ability to send emails to addresses that contain invalid dots in the local-part. To accommodate this, email addresses are converted to a legal format by surrounding the local-part with quotation marks

Examples

consecutive..dots@example.com is now "consecutive..dots"@example.com

trailingdot.@example.com is now "trailingdot."@example.com

Allow the Required Domain for Maps and Location Services

*.forceusercontent.com domain must be added to any existing allowlists for your network, firewalls, and proxies in order to allow the creation of visualforce maps and help users enter new addresses with autocomplete by using maps and location services via Google Maps

Where: This change applies to Lightning Experience, Salesforce Classic (not available in all orgs), and all versions of the mobile app in Professional, Enterprise, Performance, and Unlimited editions

Previously: this domain was erroneously included in the list of domains used only in orgs without enhanced domains

Sender ID Deprecated for Email Security Compliance

As part of a system-wide optimization of email security performance, Sender ID is no longer offered in Email Deliverability settings

Why: For Salesforce orgs created in Winter ’25 or later, Sender ID compliance cannot be enabled in Email Deliverability Settings. Technological enhancements and operational efficiency simplify email authentication processes and replaced Sender ID functionality. This change is a result of RFC7208 (Request for Comments), published in 2015

How: If you’re using Sender ID, you don’t need to make any changes. Integrations that use Sender ID continue to work after Summer ’24. Sender ID records are identified by their v=spf2.0 prefix. A record that starts with this prefix can’t be used

Enable Send ID Compliance option in orgs created before Winter '25

Enable Send ID Compliance option in orgs created Winter '25 or later

Salesforce Winter’25 Release Notes | General Enhancements

Salesforce Signs Definitive Agreement to Acquire Own Company

Salesforce Delivers Next-Generation AI Models to Power Agentforce

Antonis Melakis

Salesforce Delivers Next-Generation AI Models to Power Agentforce

Leave a Reply Cancel reply

Recent Posts

Recent Comments

Welcome Back!

Retrieve your password

Salesforce Winter’25 Release Notes | General Enhancements

3. Create and Verify Your Default No-Reply Organization-Wide Email Address to Send Email (Release Update)

Salesforce Signs Definitive Agreement to Acquire Own Company

Salesforce Delivers Next-Generation AI Models to Power Agentforce

Antonis Melakis

Salesforce Delivers Next-Generation AI Models to Power Agentforce

Leave a Reply Cancel reply

Recent Posts

Recent Comments

Tags

Welcome Back!

Retrieve your password