Salesforce Summer Release 2024

This latest release is packed with powerful new features and enhancements designed to elevate your Salesforce experience and drive business success.

Our Salesforce Development Manager, Pavan Patal gives us his take on Summer Release ’24

Prefer to view it in slide format? Checkout Pavan’s presentation here

GENERAL

1. Better Error Handling for Outdated Pages in Lightning Experience:

Experience a smoother workflow with more precise error handling if your page falls out of sync with the Salesforce server. Previously, an outdated page immediately triggered an error and a forced refresh. Now, the server attempts to process the outdated page.
If successful, the page shows a warning message that reminds you to refresh the page when convenient. Rarely, the server can’t process the outdated page. In this case, an error message prompts you to refresh the page, which resyncs the page to the server.

Where: This change applies to Lightning Experience in all editions.

When: This change is applied on a rolling basis starting in Summer ’24

Auto-Enabled
Priority: Low

GENERAL

2. Get a Summary of a User’s Permissions and Access

If you’ve wondered what permissions, public groups, or queues a user is assigned, you’re in luck. With the User Access Summary you can see this information directly from the user’s detail page, saving you time, clicks, and effort. There’s no need to run queries or look through each profile, permission set, public group, or queue when troubleshooting or managing access.
This change applies to Lightning Experience and Salesforce Classic (not available in all orgs) in all editions.
From Setup, in the Quick Find box, enter Users, and then select Users. Select a user, and then click View Summary.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Med

GENERAL

3. See What’s Enabled in Permission Sets and Permission Set Groups

It can be tricky to track all the permissions included in your permission sets and permission set groups.
To make managing your users’ access easier, you can now see all enabled object, user, field, and custom permissions on one page.
You can also see which permission set groups include the permission set and vice versa.
This feature, now generally available, includes some changes since the beta release. The summary page has an improved interface, and Salesforce added the ability to see included custom permissions and permission sets in permission set groups.

Where: This change applies to Lightning Experience and Salesforce Classic (not available in all orgs) in all editions.

Steps To Implement:

From Setup, in the Quick Find box, enter Permission Sets, and then select Permission Sets. Or, enter Permission Set Groups, and then select Permission Set Groups. Select a permission set or permission set group, and then click View Summary.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Med

GENERAL

4. Enable Unauthenticated Users to Modify Service Appointments

Unauthenticated users can now modify or cancel the service appointments that they created.
Salesforce Scheduler provides customizable email templates that include links that redirect users to dedicated pages, allowing them to modify their appointments with ease.

Where: This change applies to Lightning Experience in Enterprise and Unlimited editions with Salesforce Scheduler enabled.

How: Click the link in the email notification that launches the flow to modify a service appointment for unauthenticated users.

Auto-Enabled: For Admin, Requires Admin config
Priority: Low

GENERAL

5. Set Conditional Visibility for Individual Tabs in Lightning App Builder

Customize tab visibility in the Lightning App Builder according to your business needs.
You can set the conditions to dynamically show or hide an individual tab in the Tabs component.
This change applies to tabs on LWC-enabled record pages.

Where: This change applies to Lightning Experience in Professional, Enterprise, Unlimited, Pro Suite, and Developer editions.
How: For a complete list of LWC-enabled objects, see LWC Migration for Record Home Pages.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Med

GENERAL

6. Organize and Find Records Easily with Personal Labels

Users may now create and apply their own labels to records to help organize and locate the records they need. Users maintain their own labels (no admin setup required!)

Where: These labels can be added to:

Account
Cadence
Cadence Step Tracker
Call Script
Campaign
Contact
Case
Email Template
Lead
Opportunity
Orchestration Work Item
Task

Auto-Enabled: For All
Priority: Med

GENERAL

7. 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. 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.This change applies to Lightning Experience and Salesforce Classic in all Editions, except Database.com.
This update was introduced with Summer ’24 and Salesforce is scheduled to enforce it in Winter ’25
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.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: High

GENERAL

8. 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.

Where: This change applies to Lightning Experience in all editions.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: High

GENERAL

9. Add New Custom Fields to Dynamic Forms-Enabled Pages

Quickly and easily add a new custom field to your Dynamic Forms-enabled pages by using a new step in the custom-field creation wizard.

Where: This change applies to Lightning Experience in Group, Professional, Enterprise, Performance, Unlimited, and Developer editions.

How: Create a custom field as usual in Setup. After setting field-level security, you see the new step to select which Lightning record pages to add the field to.

The new field is added to each record page you select as the last field in the first field section on the page.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority:Med

GENERAL

10. Prepare for Restrictions on Salesforce Cookie Use

To test custom functionality and code that relies on a Salesforce session cookie before browsers fully block third-party cookies, enable a new My Domain setting. For example, you enabled third-party cookies to use Lightning Out (beta) without a custom domain or token-based authentication.
Also, to load your authenticated Visualforce page in an iframe on a third-party website, the process relies on a Salesforce session cookie. Previously, to test the impact of this change on the use of Salesforce cookies, you set flags and settings in your browser, and those steps vary by browser.

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

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.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: High

GENERAL

11. See Where a Public Group Is Used

Quickly find where a public group is used and the level of access its users get without running queries or clicking multiple features. For a specific public group, you can view the sharing rules an object is referenced in and the list views it’s shared with in the new Public Group Access Summary. You can also see the report and dashboard folders that the public group can access and the other public groups it’s included in.

Where: This change applies to Lightning Experience and Salesforce Classic in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
How: From Setup, in the Quick Find box, enter Public Groups, and then select Public Groups.
Select a public group, and then click View Summary.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

GENERAL

12. Use Blank Spaces to Align Fields on Dynamic Forms-Enabled Pages

Customize field alignment in Dynamic Forms field sections with the new Blank Space component. Find it on the Fields tab when viewing Dynamic Forms-enabled Lightning record pages in the Lightning App Builder. You can use a blank space on its own to separate fields vertically inside a field section.
To further enhance the alignment of your field section content, you can also use a blank space in conjunction with the field sectionproperty Align fields horizontally.

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

How: A blank space component is considered a field and counts against the limit of 100 fields per region. It doesn’t count against the component page limit.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

GENERAL

13. Limit Who Receives Notifications About Certificate Expiration

By popular demand, you now have more control over who gets certificate expiration email notifications. Assign the new Receive Certificate Expiration Notifications user permission only to the admins who manage certificates. Also, notification emails now include more details about how to update certificates before they expire.

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

How: With this change, most admins see fewer certificate-related emails in their inboxes. And admins who you designate to receive expiration notifications are better informed about how to handle impending certificate expirations.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: High

EINSTEIN

Improve Search with Insights from Search Analytics (Pilot):

Analyze search-related data with the built-in dashboard or build your own dashboard. Use insights to make search engine changes, optimize content, and train users.
For example, Search Analytics tells you when your users can’t find results for certain search terms. You can then add content to address gaps or modify the search engine to include those search terms in synonym groups.

Where: This change applies to Lightning Experience in all editions.

Note: This feature is not generally available and is being piloted with certain Customers subject to additional terms and conditions. It is not part of your purchased Services. This feature is subject to change, may be discontinued with no notice at any time in Salesforce’s sole discretion, and Salesforce may never make this feature generally available. Make your purchase decisions only on the basis of generally available products and features. This feature is made available on an AS IS basis and use of this feature is at your sole risk. Who: To use Search Analytics, you need a Data Cloud license and Data Cloud credits.

How: From Setup, in the Quick Find box, enter Einstein Search, and then select Settings.

Auto-Enabled: Requires Admin setup
Priority: Low

SALES BASICS

Use Screen Flows as Cadence Steps in Cadence Builder 2.0

Now sales managers can specify a screen flow as a cadence step in Cadence Builder 2.0. Use screen flow steps to let reps create a case, event, or task or to perform another action. The screen flow runs when the sales rep initiates the step for a target from their To Do List, Work Queue, or the Sales Engagement component on target records. Use the Cadence Step Flow process type to create screen flows for cadence steps, or use the included flow templates.

How: In the Flow Builder, create a screen flow from the Cadence Step Flow process type. Three flow templates are included with Sales Engagement. Flow templates must be activated before being cloned.

Create an Event
Create a Task
Create a Case

Then add a screen flow step in Cadence Builder 2.0 (1) and choose a screen flow (2).

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Med

ANALYTICS

1. Access Any Analytics Collection in Lightning Pages

Provide analytics where your users work with embedded collections on Lightning pages. In the Lightning App Builder, you can now select any Analytics collection to be a component of your page. Previously, only the first collection was available for embedding. A collection can include CRM Analytics dashboards and lenses, Lightning reports and dashboards, and Tableau dashboards.
Provide analytics where your users work with embedded collections on Lightning pages. In the Lightning App Builder, you can now select any Analytics collection to be a component of your page. Previously, only the first collection was available for embedding.

Where: This change applies to Lightning Experience in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. This change applies to CRM Analytics in Lightning Experience and Salesforce Classic. CRM Analytics is available in Developer Edition and for an extra cost in Enterprise, Performance, and Unlimited editions.

How: In the Lightning App Builder, add the CRM Analytics Collection component to your page (1). Select an available collection from the Collection lookup in the configuration panel (2).

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

ANALYTICS

2. Amplify Visual Impact In Waterfall Charts with Conditional Formatting

Help users quickly spot areas of interest and get deeper exploration of their data by adding conditional formatting to waterfall charts. Previously, your data had to be configured with other supported chart types that weren’t as compelling with displaying how positive and negative changes impacted initial data values.

Where: This change applies to CRM Analytics in Lightning Experience and Salesforce Classic. CRM Analytics is available in Developer Edition and for an extra cost in Enterprise, Performance, and Unlimited editions.

How: Open or create a dashboard with a waterfall chart. Click Formatting and open Conditional Formatting.
Apply a conditional formatting rule to a field. For example, highlight when available container inventory is lower than demand. Click Done.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

ANALYTICS

3. Embed CRM Analytics Dashboards in LWR Sites (Generally Available)

Let your customers view and interact with CRM Analytics dashboards in your Lightning Web Runtime (LWR) site by adding the CRM Analytics Dashboard component.
For example, customers can view visualizations of account data alongside their account information.
This change applies to CRM Analytics in LWR sites accessed through Lightning Experience and Salesforce Classic.
CRM Analytics is available in Developer Edition and for an extra cost in Enterprise and Performance editions, and requires an Experience Cloud license.

<Steps to implement>
Use the new CRM Analytics Dashboard Lightning web component in your Experience Cloud pages. From the component palette of an object detail page in Experience Builder, drag the dashboard component to the page.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

1. Update Records Using External IDs in REST API

When: This change affects API version 61.0 and later.

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

How: To prevent creating a new record if the target record can’t be found or doesn’t exist, add the updateOnly parameter to a URL that executes an upsert operation. You can also use URLs with the updateOnly parameter in composite REST API and composite graph REST API.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

2. Use Cursors for Expanded SOQL Query Result Support (Beta)

With Apex cursors, you can break up the processing of a SOQL query result into pieces that can be processed within the bounds of a single transaction.
Cursors provide you with the ability to work with large query result sets, while not actually returning the entire result set.
You can traverse a query result in parts, with the flexibility to navigate forward and back in the result set.
Package developers and advanced developers can use cursors effectively to work with high-volume and high-resource processing jobs.
Cursors are an alternative to batch Apex and address some of batch Apex’s limitations.
Cursors are also more powerful because they can be used in a chain of queueable Apex jobs.

Where: This change applies to all editions.

Sample code:

public class QueryChunkingQueuable implements Queueable { private Database.Cursor locator; private integer position;

public QueryChunkingQueuable() { locator = Database.getCursor ('SELECT Id FROM Contact WHERE LastActivityDate = LAST_N_DAYS:400'); position = 0; }

public void execute(QueueableContext ctx) { List scope = locator.fetch(position, 200); position += scope.size(); // do something, like archive or delete the scope list records if(position < locator.getNumRecords() ) { // process the next chunk System.enqueueJob(this); } } }

Auto-Enabled: For Admin/Developers
Priority: Low

DEVELOPER

3. Ensure More Secure Compilation of Apex Classes

Run the Compile all classes option on the Apex Classes page in Setup to achieve more reliable compilation. Compiling all classes from Setup now produces consistent compilation output as compared with other compilation mechanisms, such as metadata deployment or on-demand compilation.

Where: This change applies to all editions.

How: Previously, in some scenarios the Compile all classes option could compile classes that reference Salesforce entities that your organization doesn’t have access to. Attempts to compile Apex classes that contain such references now result in compilation errors, such as Invalid Type: SomeEntity.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

4. Evaluate Dynamic Formulas in Apex (Beta)

Dynamic formulas in Apex now support using an Sobject as the context object.
Use the new Formula.builder() method to create an instance of the FormulaBuilder to configure the formula.
Get a list of the field names as referenced in a formula using the getReferencedFields() method.
Formula evaluation in Apex is bound by the character limit, but not the compile size limit.

Where: This change applies to all editions.

How: This example uses an SObject type as the context object in the withType() method to build and evaluate a formula.

FormulaEval.FormulaInstance likelyBuyer = Formula.builder() .withType(Account.SObjectType) .withReturnType(FormulaEval.FormulaReturnType.BOOLEAN) .withFormula('AnnualRevenue > 10000 AND ISPICKVAL(Industry, "Biomechanical")');

Auto-Enabled: For Admin/Develooers
Priority: Low

DEVELOPER

5. Run the Lightning Knowledge Migration Tool

Get the latest Knowledge features when you migrate from Knowledge Classic to Lightning Knowledge, like Einstein Article Recommendations, Einstein Search for Knowledge, Flow support, and bots.
The Classic Knowledge data model retirement phase is in progress.
To prepare for this retirement and take advantage of updated features, run the Lightning Knowledge Migration Tool.
After running the Lightning Knowledge Migration Tool, you can still use Classic Knowledge in the Classic UI. We aren’t retiring the Classic UI for Knowledge

Where:-This change applies to all Salesforce customers using Classic Knowledge.

How:-Run the Lightning Knowledge Migration Tool before the deadline to migrate to the Lightning Knowledge data model.
After the migration tool is run, Lightning Knowledge works in these ways in Salesforce Classic.
– Because Lightning Knowledge uses record types instead of article types, you can no longer filter by article type.
– You can’t set a default record type in Salesforce Classic.
– Some actions, such as Change Record Type, aren’t available from the knowledge article record page in Salesforce Classic.
– Picklist values assigned to one record type in Knowledge aren’t visible on records in Salesforce Classic.
-If you have custom solutions for your Classic Knowledge implementation, such as Visualforce components or pages, refactoring them to work with the Lightning Knowledge data model is sometimes required. Especially if your custom solution relies on article types, refactor it to work with record types. Use a sandbox to test your custom solutions before running the migration tool in production.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: High

DEVELOPER

6. Support for Five-Level Parent-to-Child Relationship SOQL Queries in Apex

Apex now supports SOQL relationship queries that traverse up to five levels of parent-child records. Each parent-child relationship subquery counts towards the number of aggregate queries processed in an SOQL query statement.

Where: This change applies to all Salesforce customers using Classic Knowledge.

In API version 61.0 and later, SOQL parent-child relationship queries in Apex can contain a parent root as the first level of the query and child relationships up to four levels deep from the parent root. Track the number of aggregate queries processed in an SQL statement with the Limits.getAggregateQueries() method. The Limits.getLimitAggregateQueries() method returns a value of 300, which is the total number of aggregate queries that can be processed with SOQL query statements.

How:-Sample code
List accts = [SELECT Name, (SELECT LastName, (SELECT AssetLevel, (SELECT Description, (SELECT LineItemNumber FROM WorkOrderLineItems) FROM WorkOrders) FROM Assets) FROM Contacts) FROM Account];

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

7. Class and Style Attributes Render with Extra Whitespaces

More components render with extra whitespaces in the class and style attributes. In Spring ’23, we announced an improved rendering time for your Lightning web components as a result of an optimization on how the framework handles static elements. That change influenced how the class and style attributes of your static nodes are rendered in the DOM. Extra whitespaces or unexpected characters sometimes appear in values for those attributes.

How: Sample code
Example: An element with class values can render with an extra space. For example, consider this element with the highlight and yellow class values.

We recommend updating code that uses style or class attributes. Previously, you could query elements with an exact class name.
// Don’t do this document.querySelector('[class="highlight yellow"]’) Revise the query to use a selector that ignores whitespace changes. // Do this instead document.querySelector('.highlight.yellow')

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

8. Navigate to a URL-Addressable Lightning Web Component

Make your component available via a URL using the lightning__UrlAddressable target. To create a URL addressable component, you no longer have to embed your Lightning web component in an Aura component.

Where: This change applies to custom Lightning web components in Lightning Experience and all versions of the Salesforce mobile app. This change also applies to Lightning console apps in Enterprise, Performance, Unlimited, and Developer editions. This change isn’t available in Experience Builder sites because it interferes with custom domain and CDN support.

How: Sample code
Example:- To generate a URL for your Lightning web component and make it available via a URL, include the lightning__UrlAddressable target in your component’s .js-meta.xml configuration file. Set the tag to true. The tag has no impact on this feature and can be set to an earlier or later version.

59.0 true lightning__UrlAddressable To navigate to the custom component, use the lightning/navigation module with the standard__component page reference type. // navToComponentWithState.js import { LightningElement } from 'lwc'; import { NavigationMixin } from 'lightning/navigation'; export default class NavToComponentWithState extends NavigationMixin(LightningElement) { navigateToComponent() { this[NavigationMixin.Navigate]({ // Pass in pageReference type: 'standard__component', attributes: { componentName: 'c__myComponent', }, state: { c__propertyValue: '2000', }, }); } }

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

9. Call Component Lifecycle Hooks Using Native Browser APIs

In LWC API version 61.0 and later, components fire lifecycle hooks using only native browser APIs. Native element lifecycle hooks align with modern browser standards, and they fix common memory leaks caused by disconnectedCallback() firing inconsistently. This change mostly impacts test code, so we recommend you review and update your tests. In earlier versions, LWC uses a synthetic polyfill system to fire these hooks.

How:-Native lifecycle hooks behave differently than synthetic polyfill ones. If your components fire lifecycle hooks and use the latest version of LWC, review them for these changes and revise them as needed.

Now the connectedCallback() and disconnectedCallback() lifecycle hooks dispatch errors globally. In LWC API version 60.0 and earlier, these hooks dispatch errors locally.

To fire connectedCallback() in LWC API version 61.0, a component has to be connected to the DOM. In earlier versions of LWC, disconnected components can trigger this hook.

In the latest version of LWC, elements render only when they’re connected to the DOM. If you don’t append an element to the DOM, sometimes its shadow root is null. In earlier versions, you can render components that were detached from the DOM.

Now, when you remove elements from the DOM and then reinsert them, connectedCallback() and disconnectedCallback() fire for each element. If the data bindings inside the component change too, renderedCallback() also fires. In earlier versions of LWC, these callbacks don’t fire after reordering.
connectedCallback() and renderedCallback() now fire in the standard DOM depth-first tree traversal order. In earlier versions, these hooks traverse element trees according to the synthetic lifecycle polyfill.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

10. Build Custom Forms with the ElementInternals Web API

Custom components using LWC API version 61.0 and later can use the standard ElementInternals web API to build custom form controls that work like standard HTML forms.

How: Sample
To create an ElementInternals object, call the this.attachInternals() method, which gives you access to methods and properties for form controls.
export default class extends LightningElement { constructor() { super(); const internals = this.attachInternals(); internals.role = 'button'; internals.ariaLabel = 'My button'; } }

To use the FACE lifecycle callbacks, add a formAssociated property, which identifies the Lightning web component as a form control.
export default class extends LightningElement { static formAssociated = true; formAssociatedCallback(form) { console.log('Form:', form); } }

You can call the this.attachInternals() method only one time. It throws an error if you call it twice. Avoid calling this.attachInternals() in a lifecycle hook that can be called multiple times, such as in connectedCallback or renderedCallback.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

11. Build Custom Forms with the ElementInternals Web API

Custom components using LWC API version 61.0 and later can use the standard ElementInternals web API to build custom form controls that work like standard HTML forms.

How: Sample
To create an ElementInternals object, call the this.attachInternals() method, which gives you access to methods and properties for form controls.
export default class extends LightningElement { constructor() { super(); const internals = this.attachInternals(); internals.role = 'button'; internals.ariaLabel = 'My button'; } }

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

12. Enable LWC Stacked Modals (Release Update)

As part of the Salesforce internal migration from Aura to LWC, more modals in Lightning Experience now render using LWC. This update provides improved performance, especially when working with a large number of fields on a record create or edit modal. You can now also use Dynamic Forms in a modal that’s opened from a Create from Lookup field on most LWC-enabled record pages. When you enable this update, you can expect minor changes to modal behavior. This update is available starting in Summer ’24.

Where: This change applies to custom Lightning web components in Lightning Experience, Experience Builder sites, and all versions of the Salesforce mobile app. This change also applies to Lightning web components in open source.
If you use custom quick actions, consider these guidelines.
LWC quick actions—When using the lightning/navigation module, the newer modal overlays and stacks on the previous modal by default. To automatically close the previous modal when navigating, set replace to true.
Aura quick actions—If you used force :createRecord or force:editRecord, Salesforce recommend updating your code to use lightning:navigation so that you can control post-save navigation behavior. To use post-save navigation on record save, specify navService.navigate(pageRef, true); where the replace property is true.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

DEVELOPER

13. Monitor Setup Methods Using ApexTestResult

ApexTestResult rows are now generated for Apex tests run with the @testSetup annotation. A new IsTestSetup column is set to true for these annotated tests to distinguish them from other test methods. Also, a new TestSetupTime column on ApexTestRunResult tracks the cumulative time of all setup methods for the given ApexTestRunResult, similar to how TestTime tracks the cumulative time of all its test methods. Previously, information about limits and cumulative run time was available only by parsing the appropriate method sections in the debug log.

How: ApexTestResult is updated by default for all setup methods. You can opt out in one of these ways.

From Setup, in the Quick Find box, enter Apex Settings, and then select Do not create Apex test results for @TestSetup methods.
To disable this feature programmatically with Metadata API, use the enableTestSetupSkipTestResults option in ApexSettings.

Auto-Enabled: For Admin, Requires Admin, Contact SFDC
Priority: Low

FLOW

1. Run Flows in Bot User Context (Release Update

With this update enabled, a flow initiated by a bot runs in user context. The user profile and permission sets associated with the bot, as well as any sharing rules, determine the object permissions and field-level access of the flow. This update prevents flows initiated by a bot from creating, reading, updating, or deleting records that the bot doesn’t have permission to access or modify. Previously, a flow initiated by a bot ran in system context and had permission to access and modify all data. This update was first made available in Summer ’23.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

FLOW

2. Enable LWC Stacked Modals (Release Update)

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

FLOW

3. Have Unlimited Paused and Waiting Flows

Salesforce has removed the per-org usage-based limit for paused and waiting flow interviews. While there’s no limit now for paused and waiting flow interviews, the number of paused and waiting flows can still be limited by the amount of storage available to your org. If you need more storage, call your Salesforce account rep.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

FLOW

4. Use Threading Tokens in Emails

Now even automated emails support the new token-based threading. To securely link email replies to the correct record, place a threading token in the email’s subject or body.

How: Go to the Send Email core action in Flow Builder. When you’re setting input values, choose to add a threading token to the email subject or body. Be sure to include a Related Record ID.
If the related record is a case, Email-to-Case processes email replies automatically. Salesforce now also supports threading for other types of objects. To process incoming emails containing tokens that aren’t cases, create an Apex Email Service and use the EmailMessages.getRecordIdFromEmail function to find the record that matches the token. For example, if you’re implementing approval processing and you’ve provided a Related Record ID of a PurchaseRequest custom object record, use the Apex Email Service to retrieve the recordId and pass it to an autolaunched flow.

Auto-Enabled:For Admin, Requires Admin, Contact SFDC
Priority: Low

If you would prefer to view it in slide format, then checkout Pavan’s presentation here

Are you ready to elevate your business?

Salesforce Summer Release 2024

1. Better Error Handling for Outdated Pages in Lightning Experience:

2. Get a Summary of a User’s Permissions and Access

3. See What’s Enabled in Permission Sets and Permission Set Groups

4. Enable Unauthenticated Users to Modify Service Appointments

5. Set Conditional Visibility for Individual Tabs in Lightning App Builder

6. Organize and Find Records Easily with Personal Labels