Customers / Administrator’s Point of View

1. Prepare for the New Setup Domain: – Salesforce plans to host Setup pages on a new domain in a future release. To prepare for this change, add *.salesforce-setup.com to your allowlists.
   1. This change applies to Lightning Experience and Salesforce Classic in all editions.
2. Set a Password or Expiration Date on a Public Link to a Salesforce File: -In Lightning Experience, when you create a public link to share a file, you can choose to set a date when the link expires. You can also protect access to the file with a password. By default, link expiration is enabled and set for 30 days. Use the password default settings to determine if protection is on or off by default. When password protection is toggled on, an auto-generated password shows in the dialog. Public links to folders don’t have password protection or link expiration.
   1. This change applies to Lightning Experience in all editions. 
   2. <<Steps to Implement>>
      1. To set password defaults for Salesforce Files, edit the content deliveries settings. From Setup, in the Quick Find box, enter Salesforce Files, and then select Content Deliveries and Public Links. Select a password default
3. Connect to Google Analytics 4 (Generally Available): – Migrate to Google Analytics 4 to continue loading your Google Analytics data and take advantage of Google’s new event-based GA4 property framework. Google Analytics 4 uses first-party and Google data to understand and analyze multiple sites and apps together. Google Analytics 4 has replaced Universal Analytics. On July 1, 2023, all standard Universal Analytics properties stopped processing data.
   1. 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.
   2. <<Steps to Implement>>
      1. Create a Google Analytics 4 connection using the Data Manager. Add your Google Analytics property ID to the advanced properties for each connected object.
4. View Slack Channel Recipients in Subscription Reports: – Quickly see the Slack channels where subscriptions and notifications are sent. In addition to monitoring schedules, conditions, recipients, and actions, a custom subscription report can now include a recipient column containing Slack channel names. Previously, this column showed ID numbers.
   1. This change applies to Lightning Experience in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. The CRM Analytics for Slack app is available for use where approved by a workspace admin and installed in Slack.
   2. <<Steps to Implement>>
      1. Add the Recipient Collaboration Room column to the Action block in your custom subscription report. For channels created in Winter ’24 and later, the column is populated with the Slack channel names where subscriptions and notifications are sent. For channels created before Winter ’24, the channel ID appears in the column.
      2. Channel names are saved when added to a subscription or notification. If the name of a channel is changed, the name isn’t automatically updated in the report.
5. Open Reports and Dashboards in Multiple Tabs from the Analytics Tab: – You can now open multiple reports and dashboards in individual tabs. Previously, you could open only one report at a time in the Analytics tab. You get better organization of your work and the ability to work on different analytics at the same time.
   1. This change applies to Lightning Experience in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. Access to CRM Analytics assets is available for an extra cost.
   2. <<Steps to Implement>>
      1. From the App Launcher, find and select Analytics, then click multiple reports and dashboards to view them in separate tabs.
6. Explore Multiple Data Model Objects in Direct Data Using Joins (Generally Available): – It’s now easier to analyze data model object (DMO) records where the data is normalized and related information resides in separate DMOs. To explore and draw insights from multiple DMOs simultaneously, join these objects in a single dashboard query. You can also filter the joined data and highlight the records that matter with conditional formatting. Previously, you wrote custom SQL queries to analyze data in multiple DMOs.  
   1. 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.
   2. <<Steps to Implement>>
      1. For example, to compare sales order data with product and customer’s annual income, in the dashboard designer, create a query on the Sales Order DMO (1).
      2. Then, in the lens mode, click Manage Data Sources (2). Add the related Individual and Product DMOs that you want to use (3), and apply your changes (4).
      3. Build your query on the joined DMOs.
7. Show Salesblazer Content in the Guidance Center: – Inform and inspire your company’s sales professionals with the latest insights, expertise, and pro tips from their peers, delivered in the flow of work in Salesforce. The Guidance Center now includes a Salesblazer section that shows content authored by sales leaders, sellers, and sales operations professionals. Clicking an item in the Salesblazer section opens the content in a new browser tab. Items remain in the Salesblazer section until the source content is refreshed, which occurs weekly on average.
   1. This change applies to Lightning Experience in Starter, Professional, Enterprise, Performance, Unlimited, and Developer editions.
   2. <<Steps to Implement>>
      1.  If the Salesforce Suggestions for End Users option in the Guidance Center page in Setup is on, the Salesblazer section in the Guidance Center is available for all users.
8. Use Custom Logic in Your Expression-Based Visibility Rules: – Visibility rules, available for enhanced LWR sites, are now more flexible. You can now use two operators in the same rule. Previously, you could only add conditions with an AND or an OR operator in a single rule.
   1. This change applies to LWR sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
9. Chart Historical Prospect Changes by Feature: – Review prospect changes at a glance using the new Prospect Change Monitor histogram in the Account Engagement Optimizer. Easily focus on specific feature areas or view all changes across your business unit.
   1. This change applies to all Account Engagement editions.
10. Design Engagement Programs with More Precise Wait Times: – Prospects can now wait in Engagement Studio Program steps from 2 to 8 hours. Previously, wait times were limited to increments of days.
    1. This change applies to all Account Engagement editions.
11. Remove Unconverted Visitor Activity Records: – Free up system bandwidth by removing old visitor records that didn’t convert to prospects. Use the new Stale Unconverted Visitors option in your Business Unit Settings to automatically remove unconverted records older than 365 days.
    1. This change applies to all Account Engagement editions.
12. Capture More Details of Email Deliverability: – Stay informed, troubleshoot, or evaluate the performance of your email easily with enhanced deliverability information in email log reference files. Use the 11 new field values R through AB to learn more about the health of emails that originate from external senders and emails that are sent from Salesforce servers.
    1. This change applies to Lightning Experience and Salesforce Classic in all editions.
13. Prevent Users from Unpublishing Content with Dependencies in Enhanced CMS Workspaces: – When one prominent piece of content, such as a news article, incorporates CMS content, a user can’t unpublish that CMS content because of this dependency. Similarly, CRM content can have dependencies to CMS content that prevent unpublish. Now, the unpublish window shows which records reference the content, and a link icon identifies those records with prominent dependencies. The Content Usage card on the content detail page also provides this information.This change prevents users from unpublishing content that could appear as an error or a broken page in other content.
    1. This change applies to Lightning Experience in Enterprise, Performance, Unlimited, Developer, and Starter editions.
14. View Standard Bot Reports in the Winter ’24 Folder: – Each release, Einstein Bots adds a folder that contains the latest versions of all standard bot reports. In Winter ’24, no changes affect standard bot metric types or individual reports from Summer ’23, but you can access fresh versions of all reports in the Einstein Bot Reports Winter ’24 folder.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. Setup for Einstein Bots is available only in Lightning Experience.
15. Assign Enablement Programs to More Users with Fewer Clicks: – Expand the scope of your company’s Enablement rollout to more users, more quickly. In the program assignment window, you can now filter the users that you want to assign to a program by their profile, role, and public group. With one click, you can select all users that match your applied filters, within your org’s assignment limit. Previously, you could filter users in the assignment window only by public group. And you could assign all matching users only by scrolling enough times to load all users in the window and then selecting the header row checkbox.
    1. This change applies to Lightning Experience in Enterprise, Performance, and Unlimited editions with Sales Cloud, Service Cloud, Financial Services Cloud, Health Cloud, or Salesforce Platform. An Enablement add-on license is required.
    2. The Filters panel includes new fields for selecting a specific profile and role to filter the available users shown in the assignment window.
16. Create Dependencies Between Service Appointments with More Flexibility: – Implement complex work chains easily by selecting a wider variety of lookup fields to create dependencies between service appointments. Previously, you could select only service appointments with the same account or work order.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Unlimited, and Developer editions with the Field Service managed package installed.
17. Save Time with Mass Quick Actions on Related Lists (Generally Available): – Use the power of quick actions on related lists, now generally available, to help your users create and update related records with ease. Streamline data entry by configuring quick actions with predefined field values and action layouts that include only the most important fields. And add quick actions directly on the related lists, right where users need them. Your users can create related records for items in the list without leaving the page. Or they can perform mass updates on up to 100 related records at once.
    1. This change applies to Lightning Experience in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
    2. <<Steps to Implement>>
       1. You can add quick actions on a related list in one of two ways. In this release, only Create a Record and Update a Record quick actions are supported.
          1. To add quick actions from the Lightning App Builder, add or select the Dynamic Related List – Single component on the record page. In the properties pane, select Show list view action bar, and then click Add Action.
          2. To add quick actions using the page layout editor, from the object management settings for the parent object, open the page layout. Double-click to open the related list properties, expand the Buttons section, and select the quick actions that you want to add. Then, from the parent record page in the Lightning App Builder, set the related list type to Enhanced List.
          3. Now the related list includes the quick actions that you added (1), and users can apply the actions to the records that they select (2).
18. Salesforce Object ID Is Refined to Use Three Characters for Server IDs (Release Update): – Previously, a valid Salesforce Object ID had a two-character Server ID or Instance ID as the 4th and 5th characters in the overall 15-18 characters. With this change, Salesforce now generates three-character Server IDs, which are the 4th, 5th, and 6th characters in the Object ID. Existing Object IDs don’t change and neither does the length of an Object ID, which is still 15-18 characters. This update can cause test cases to fail if the test code doesn’t account for the new ID structure. This release update was first available in Summer ’23 is enforced in Winter ’24. This change applies to Lightning Experience and Salesforce Classic in all editions.
    1. This change impacts customers who have custom code or tests that assume the Server ID can be only the 4th and 5th characters of a Salesforce ID rather than the 4th, 5th, and 6th. After the change is enforced, valid test cases can fail and invalid ones can pass.
19. Close Cases Faster with Einstein GPT Work Summaries (Generally Available): – Save agents time with AI-generated case summaries, now generally available. Based on a Chat conversation between an agent and customer, Einstein GPT predicts and fills a summary, issue, and resolution. Agents can then review, edit, and save these summaries.
    1. This change applies to Unlimited editions with Service Cloud Einstein and the Einstein GPT for Service add-on. Einstein GPT is available in Lightning Experience.
    2. <<Steps to Implement>>
       1. Work Summaries requires the Chat channel and the Service Console app.
       2. To get started with Work Summaries, from the Einstein GPT for Service: Work Summaries Setup page, enable Work Summaries. In the Map Outputs to Record Fields section, select the case fields where you want to map Einstein GPT outputs.
       3. To show agents summaries, add the Wrap Up component to the chat transcript page. When agents click Get Einstein Recommendations, Einstein predicts and fills values for the Summary, Issue, and Resolution fields.
20. Stay on Top of Survey Responses by Receiving Custom Notifications: – Get custom notifications based on invitation and merge field data for timely actions. Specify notification recipients using invitation data, participant data, or other data in a data map.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Unlimited, and Developer editions where Feedback Management – Starter or Feedback Management – Growth is enabled.
    2. <<Steps to Implement>>
       1.  To create custom notifications in data maps, users need the Salesforce Advanced Features Starter permission or the Salesforce Surveys Advanced Features permission.
       2. For example, you can create notifications to alert the case owner every time a customer responds to a survey and the response meets certain defined criteria.
21. Renamed: 
    1. Backup and Restore Is Now Salesforce Backup
    2. MuleSoft Composer for Salesforce is now Flow Integration
22. Retired:
    1. Meeting Studio Is Being Retired
    2. Salesforce for Outlook Is Retiring in June 2024
    3. News, Automated Account Fields, and Account Logos Are Being Retired
    4. Salesforce Platform API Versions 21.0 Through 30.0 Retirement (Release Update)
    5. Cadence Wait Steps Are Being Retired
    6. Einstein Account Insights and Opportunity Insights Are Being Retired
    7. Meeting Studio Is Being Retired

1. Dynamically Import and Instantiate Lightning Web Components: – Dynamic component creation can help you avoid loading large modules that you don’t need for all use cases. Also, you can create a component instance when the underlying component constructor isn’t known until run time. Dynamic import is a convenient solution to make a component more customizable. However, it isn’t always the best solution because of the run-time performance overhead it introduces, so don’t overuse it.
   1. This change applies to Lightning Experience in Enterprise, Unlimited, and Developer editions.
   2. <<Steps to Implement>>
      1. To dynamically import and instantiate Lightning web components, enable Lightning Web Security.
      2. LWR Sites for Experience Cloud supports only statically analyzable dynamic imports. For this use case, import(“c/analyzable”) works, but import(“c/” + “analyzable”) doesn’t work because it isn’t statically analyzable.
2. Get the Latest LWC Features with Component-Level API Versioning: – Add an API version on a custom component to inform the LWC framework to behave as it did for the Salesforce release corresponding to the API version for that component. Versioning your custom components allows us to ship new features, bug fixes, or performance improvements and to deprecate legacy features.
   1. This change applies to custom Lightning web components in Lightning Experience, Experience Builder sites, and all versions of the Salesforce mobile app.
   2. <<Steps to Implement>>
      1. Every HTML, CSS, and JS file of a component corresponds to one API version. To specify an API version, use the apiVersion configuration element in the .js-meta.xml file for the component.
         Copy Code Copied Use a different Browser

         
         <?xml version="1.0" encoding="UTF-8"?>
         <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
             <apiVersion>58.0</apiVersion>
         </LightningComponentBundle>
         
         

3. Create Custom Elements with Lightning Web Security Enabled (Beta): – With Lightning Web Security (LWS) enabled, you can create custom elements in your Lightning web components. Custom elements are a key feature of the Web Components standard and another advantage of LWS over Lightning Locker.
   1.  This change applies to Lightning Experience in all editions, LWR-based Experience Cloud sites, and Lightning web components in Aura sites when LWS is enabled in the Salesforce org.
   2. <<Steps to Implement>>
      1. Create custom elements in the standard way using customElements.define() when LWS is enabled. LWS handles the virtual isolation for you.
4. Scan Documents with a Mobile Device using Lightning Web Components: – Use the DocumentScanner API to access native device functionality to scan documents and parse their text content.
   1. This feature is available in the Salesforce Mobile app and the Salesforce Field Service app.
   2. <<Steps to Implement>>
      1. Import DocumentScanner into your component definition.
      2. Run tests to ensure DocumentScanner is available before calling document-scanning functions.
      3. Use the scan() function to scan a document and interact with the extracted text.Using DocumentScanner in your LWC-enabled mobile app is easy:
5. Specify Custom Access Using Permission Sets for User Mode Database Operations (Developer Preview): – The new AccessLevel.withPermissionSetId() method supports database and search operations that are run with permissions specified in a permission set. Apex enforces field-level security (FLS) and object permissions as per the specified permission set.
   1. This feature is available in scratch orgs where the ApexUserModeWithPermset feature is enabled. If the feature isn’t enabled, Apex code with this feature can be compiled but not executed.
   2. <<Steps to Implement>>
      1. For the Developer Preview, you can run the AccessLevel.withPermissionSetId() method with a specified permission set ID. Specific user mode DML operations that are performed with that AccessLevel, respect the permissions in the specified permission set. Previously, you could choose to run DML operations in user mode, enforcing the FLS and object permissions of the running user.
      2. This example runs the AccessLevel.withPermissionSetId() method with the specified permission set and inserts a custom object.
         Copy Code Copied Use a different Browser

         
         @isTest
         public with sharing class ElevateUserModeOperations_Test {
             @isTest
             static void objectCreatePermViaPermissionSet() {
                 Profile p = [SELECT Id FROM Profile WHERE Name='Minimum Access - Salesforce'];
                 User u = new User(Alias = 'standt', Email='standarduser@testorg.com',
                     EmailEncodingKey='UTF-8', LastName='Testing', LanguageLocaleKey='en_US',
                     LocaleSidKey='en_US', ProfileId = p.Id,
                     TimeZoneSidKey='America/Los_Angeles',
                     UserName='standarduser' + DateTime.now().getTime() + '@testorg.com');
         
                 System.runAs(u) {
                     try { 
                         Database.insert(new Account(name='foo'), AccessLevel.User_mode); 
                         Assert.fail(); 
                     } catch (SecurityException ex) { 
                         Assert.isTrue(ex.getMessage().contains('Account'));
                     }
                     //Get ID of previously created permission set named 'AllowCreateToAccount'
                     Id permissionSetId = [Select Id from PermissionSet 
                         where Name = 'AllowCreateToAccount' limit 1].Id;
         
                     Database.insert(new Account(name='foo'), AccessLevel.User_mode.withPermissionSetId(permissionSetId)); 
         
                     // The elevated access level in not persisted to subsequent operations
                     try { 
                         Database.insert(new Account(name='foo2'), AccessLevel.User_mode); 
                         Assert.fail('permset leaked'); 
                     } catch (SecurityException ex) { 
                         Assert.isTrue(ex.getMessage().contains('Account')); 
                     } 
                     
                 } 
             } 
         }
         

6. Iterate Within For Loops More Easily with Iterable: – You can now easily iterate through lists or sets using an Iterable variable in a for loop.
   1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
   2.  This example iterates through a list of strings.
      Copy Code Copied Use a different Browser

      
      Iterable<String> stringIterator = new List<String>{'Hello', 'World!'};
         for (String str : stringIterator) {
            System.debug(str);
      }
      

   3. This example implements an Iterable interface and then iterates through the strings in the returned set of strings.
      Copy Code Copied Use a different Browser

      
      public class MyIterable implements Iterable<String> {
         public Iterator<String> iterator() {
            return new Set<String>{'Hello', 'World!'}.iterator();
         }
      }
      

      Copy Code Copied Use a different Browser

      
      for (String str : new MyIterable()) {
         System.debug(str);
      }
      

7. Set the Maximum Depth of Chained Queueable Jobs (Generally Available): – The Configure Stack Depth of Chained Queueable Jobs feature is now generally available. You can set a maximum stack depth of Queueable jobs, overriding the default limit of five in Developer and Trial Edition orgs. This feature provides a larger safety mechanism to prevent runaway recursive jobs from consuming the daily async Apex limit.
   1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. 
   2. <<Steps to Implement>>
      1. Enqueue jobs by using the new System.enqueueJob() overload. The method overload has an optional AsyncObjects parameter where you can specify the maximum stack depth and the minimum queue delay.
      2. Use these methods in the new System.AsyncInfo class to determine the current and maximum stack depths and to get the minimum queueable delay.
         1. getCurrentQueueableStackDepth()
         2. getMaximumQueueableStackDepth()
         3. getMinimumQueueableDelayInMinutes()
         4. hasMaxStackDepth()
      3. This example uses stack depth to terminate a chained job and prevent it from reaching the daily maximum number of asynchronous Apex method executions.
         Copy Code Copied Use a different Browser

         
         // Fibonacci
         public class FibonacciDepthQueueable implements Queueable {
            
             private integer nMinus1, nMinus2;
                
             public static void calculateFibonacciTo(integer depth) {
                 AsyncOptions asyncOptions = new AsyncOptions();
                 asyncOptions.MaximumQueueableStackDepth = depth;
                 System.enqueueJob(new FibonacciDepthQueueable(null, null), asyncOptions);
             }
                
             private FibonacciDepthQueueable(integer nMinus1param, integer nMinus2param) {
                 nMinus1 = nMinus1param;
                 nMinus2 = nMinus2param;
             }
            
             public void execute(QueueableContext context) {
                
                 integer depth = AsyncInfo.getCurrentQueueableStackDepth();
                
                 // Calculate step
                 integer fibonacciSequenceStep;
                 switch on (depth) {
                     when 1, 2 {
                         fibonacciSequenceStep = 1;
                     }
                     when else {
                         fibonacciSequenceStep = nMinus1 + nMinus2;
                     }
                 }
                
                 System.debug('depth: ' + depth + ' fibonacciSequenceStep: ' + fibonacciSequenceStep);
                
                 if(System.AsyncInfo.hasMaxStackDepth() &&
                    AsyncInfo.getCurrentQueueableStackDepth() >= 
                    AsyncInfo.getMaximumQueueableStackDepth()) {
                     // Reached maximum stack depth
                     Fibonacci__c result = new Fibonacci__c(
                         Depth__c = depth,
                         Result = fibonacciSequenceStep
                         );
                     insert result;
                 } else {
                     System.enqueueJob(new FibonacciDepthQueueable(fibonacciSequenceStep, nMinus1));
                 }
             }
         }
         

8. Connect to Third-Party Key Stores with External Key Management – Encrypt data with keys stored outside of Salesforce and exercise more direct control over keys. With the new External Key Management (EKM) service, use easy on-screen guidance to create a secure connection to AWS Key Management Service (KMS). Salesforce then uses your key stored in AWS KMS to encrypt and decrypt Salesforce data. Key material is only stored as long as is necessary to complete encrypt and decrypt operations.
   1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
   2. <<Steps to Implement>>
      1. Before you start, make sure that you have a key in AWS KMS. Salesforce uses your external key as a root key. In Salesforce Setup, on the Advanced Settings page, turn on External Key Management. On the Key Management page, click Manage Root Keys.
      2. A guided wizard opens to walk you through the process of connecting Salesforce to AWS. Add information about your AWS key, including your identifier, region, and a unique description. EKM generates a code snippet, or statement, that you can easily copy into your key policy in AWS.
      3. Save your updated key policy in AWS, return to Salesforce, and save your work. You can now generate a data encryption key (DEK) in Salesforce and apply it to fields, files and attachments, and any other data you can encrypt with Shield Platform Encryption.
      4. Salesforce uses your root key in AWS to generate a DEK and wrap it for temporary storage in the encrypted key cache. You can review and audit historical key information on the root key Detail view. And as with the Cache-Only Key Service, you can check your connection to AWS for easy troubleshooting and connection maintenance.
9. Access a Mobile Device’s Biometrics Capabilities with Lightning Web Components: – Use the BiometricsService API to access native device functionality to prompt device users to confirm their identity with biometrics.
   1. This feature is available in Mobile Publisher for Experience Cloud applications.
   2. <<Steps to Implement>>
      1. Import BiometricsService into your component definition.
      2. Run tests to ensure BiometricsService is available before calling biometrics-related functions.
      3. Use the feature functions to prompt biometric identity confirmation.
10. Monitor Component Events with the Custom Component Instrumentation API (Beta): – Add observability to your Lightning web components with the Custom Component Instrumentation API (beta). Now you can directly monitor and track events or interactions with custom Lightning web components in your org’s Event Monitoring. Previously, Event Monitoring tools only tracked insights about your application as a whole, like records loaded and page performance. The Custom Component Instrumentation API is designed for Lightning web components and isn’t supported for Aura components.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.
    2. <<Steps to Implement>>
       1. Import log from the lightning/logger module in your component and log data messages to Event Monitoring. The log() function publishes data to a new EventLogFile event type called Lightning Logger Event that structures the event data for use in Event Monitoring.
          Copy Code Copied Use a different Browser

          
          <!-- myComponent.html -->
          <template>
            <lightning-button label="Approve" 
                              onclick={handleClick}>
            </lightning-button>
          </template>
          

          Copy Code Copied Use a different Browser

          
          // myComponent.js
          import { LightningElement } from 'lwc';
          import { log } from 'lightning/logger';
          
          export default class HelloWorld extends LightningElement {
            constructor() {
            super();
            }
          
            let msg = {
                type: "click",
                action: "Approve"
            }
          
            handleClick() {
              log(msg);
            }
          }
          

11. Use JWT-Based Access Tokens to Authenticate for REST API Calls: – You can now use JSON Web Token (JWT)-based access tokens for granting access to REST APIs. Enable connected apps to issue JWT-based access tokens and use these tokens to authenticate REST calls. Make sure you understand the functionality and limitations before you implement JWT tokens.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
12. Select Who Has Access To a Sandbox: – Selective Sandbox Access helps you limit access to a sandbox to only required users when refreshing or creating a sandbox. By default, all active users in the source org have access to the sandbox, but only the user who creates the sandbox has their email address in the original format (without .invalid appended to it). With selective access, a Salesforce admin grants access to specific users through a public group. The email addresses for the users included in the group remain in their original format and don’t need to be modified. Users who aren’t part of the public group have to be unfrozen in the sandbox in order to access it.
    1. This change applies to sandboxes of Professional, Enterprise, Performance, Unlimited, and Database.com editions.
13. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
    1. Build Screen Flows with Reactive Components (Generally Available): – Reduce the number of screens that your users click through, and build screens that feel like single-page applications with reactive flow screen components. Configure supported standard components or custom Lightning web components to react to changes in other components on the same screen in real time. For example, create a Data Table component that lists Opportunity records. On the same screen, add a Radio Buttons component, and set the default value of the component to the stage of the first Opportunity that the user selects. Previously, if you needed a component to react to changes in another component, you placed the components on separate screens.
       1. This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
       2. Check this release notes for detailed information. 
    2. Create Custom Error Messages in Record-Triggered Flows: – Use the new Custom Error Message element to create targeted error messages for your end users to explain what went wrong or how to correct it. The error messages display in a window on the overall record page or as an inline error on a specific field. The associated record change is rolled back. Error messages can be created for before-save and after-save flows. 
       1. This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
       2. <<Steps to Implement>>
          1. Read the below articles for step-by-step instructions  
             1. Custom Validations Using Record-Triggered Flows
             2. Display Custom Error Messages for Record-Triggered Flows
    3. Transform Your Data in Flows (Beta): – Transform collections of data between flow resources with the new Transform element in Flow Builder. Combined with the Action element that makes an HTTP callout, you can build a flow that fully integrates data outside Salesforce with no code. Previously, you built a flow that included the Loop element and the Assignment element. Now you can do it all with the Transform element when transforming data in screen flows, autolaunched flows with no triggers, and record-triggered flows.
       1. This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
       2. Read this article for step-by-step instructions. 
    4. Create Autolaunched Flows Based on Data Changes in Data Cloud: – You can now start a Data Cloud-Triggered Flow based on changes in a data model object or calculated insight object. For example, you can update a Unified Individual’s loyalty status based on changes to their loyalty balance.
       1. This change applies to Lightning Experience and Salesforce Classic in all editions.
    5. Screen Flow Components Retain Values After State Changes: – Screen flows now retain values when a user resumes a paused flow, experiences an input validation error, or returns to an earlier screen. Previously, if you didn’t provide a default value when you configured the Name, Address, Data Table, Email, or other components, the flow removed user-specified values when these events occurred. This change applies only to flows that are running on API version 59.0 or later.
       1. This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
    6. Refresh Values Between Screens for More Components: – You can now refresh the values of choice, Date, Date & Time, Number, Currency, Text, and Long Text Area components when a user navigates to a previous screen and then forward again. For example, a user enters the cost of three services on the first screen. When the user navigates to the next screen, the screen flow displays the total cost. If the user returns to the first screen and changes a value, you can refresh the total cost on the next screen or leave it unchanged. However, if a user navigates to a previous or later screen and then returns to the current screen a second time, the flow doesn’t update the reactive components again.
       1. This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
       2. <<Steps to Implement>>
          1.  Drag a component to a screen. In the component’s properties pane, under Advanced, select an option for Revisited Screen Values.
    7. Use Wait Elements in More Types of Flows: – The Wait for Amount of Time element and the Wait Until Date element are now available in schedule-triggered flows, autolaunched flows, and orchestrations. Previously, these wait elements were available only for journeys.
       1. This change applies to Lightning Experience and Salesforce Classic in all editions.
14. Flow Orchestrator: – There are several enhancements in Flow Orchestrator as follows:
    1. Control Execution of Orchestration Stages and Steps with Requirements: – Each orchestration step uses a selected condition that determines when it can start. And each orchestration stage and interactive orchestration step uses a condition to determine its completion. Previously, when you had complex criteria, you created an evaluation flow to determine when a step can start or a stage or an interactive step can end. Now you can define up to 3 requirements in the Properties panel to control stage and step execution.
       
       1. This change applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions.
    2. Extend Flow Orchestration Objects: – Flow Orchestration objects are now available in Object Manager in Setup. Customize Flow Orchestration Run, Flow Orchestration Stage Run, Flow Orchestration Step Run, and Flow Orchestration Work Item objects for your needs by adding custom fields and custom relationships.
       1. This change applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions.
15. Update U2F Security Keys to Support WebAuthn Authentication: – To work with Salesforce, U2F security keys must be updated to use WebAuthn authentication. The update process works seamlessly behind the scenes. For new security keys, the update occurs automatically when a user registers it for their Salesforce account. For U2F security keys that were registered prior to Summer ’22, users simply need to log in with their key before Winter ’24. Doing so automatically updates the key. If a user misses this window, they can still update their key after Winter ’24 by re-registering it for their Salesforce account.
    1. If any of your users miss the window to update their U2F key before Winter ’24, use these access recovery tips. In both cases, the process of re-registering a U2F key completes the WebAuthn update.
       1. Instruct the user to disconnect and re-register their key from the Advanced User Details page. If the user hasn’t registered an additional verification method that they can use to log in, give them a temporary verification code for access to their account.
       2. Alternatively, remove the security key from the user’s account. Then the user can log in and re-register their key. If the user doesn’t have another verification method, Salesforce automatically prompts them to add one before they can finish logging in. If they log in with a different verification method or a temporary verification code, they can re-register their key from the Advanced User Details page.
16. Authenticate Named Credential Callouts with Client Credentials Flow: – You can now configure named credentials to use OAuth 2.0 client credentials flow for server-to-server integration. If you want to directly share information between two applications and eliminate the need for explicit user interaction, use the OAuth 2.0 client credentials flow. In this flow, the client app exchanges its client credentials defined in a client secret or JWT assertion.
    1. This change applies to Lightning Experience and Salesforce Classic in all editions.
    2. <<Steps to Implement>>
       1. When you create an external credential from the Salesforce UI, select OAuth 2.0 as the authentication protocol, and then select Client Credentials with Client Secret Flow or Client Credentials with JWT Assertion Flow. You can also use the Metadata, Tooling, and Apex ConnectApi APIs to create and edit external credentials.
17. Get Information About Insufficient Access Errors: – Use the new Insufficient Access event type in the EventLogFile object to analyze and troubleshoot account, case, contact, and opportunity record access errors for your users. These events contain information about the record the user attempted to access or transfer, the access level required for this action, and the related error message. 
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. This event is available in the API but not in the Event Monitoring Analytics app.
18. Add Permission Sets to Your Custom Templates and Blocks (Beta): – Bot templates and blocks make it easy to share complex bot functions with powerful actions, such as Apex, external service, and flow. But what good is a custom-built flow if your bot can’t run it? Now when you create a template or block, you can add a permission set that grants access to the required resources. When someone creates a bot from your template or imports your block, they add the permission set to their bot user profile so they can go live with their bot’s new functionality quickly and easily.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. Setup for Einstein Bots is available only in Lightning Experience.
    2. <<Steps to Implement>>
       1. To get started, create a permission set that grants access to the resources required to use your template or block. When you create a template or block, in the Permission Set field, search for and select the permission set you want to add.
       2. When someone creates a bot from your template or imports your block, they’re prompted to add the permission set to their bot user profile.
19. Reach More Customers with Multi-Language Support for Custom Templates and Blocks (Beta): – Now you can create and share bot templates and blocks with full multi-language support, so anyone who uses your templates or blocks can reach more customers in less time. When you create a template or block, you can include support for some or all of the primary and secondary languages supported in the original bot. Previously, custom templates and blocks supported only one language.
    1. This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. Setup for Einstein Bots is available only in Lightning Experience.
    2. <<Steps to Implement>>
       1. In the Bot Builder, when you create a template or block, you’re prompted to select a primary language and any secondary languages you want to support, based on the languages supported by the original bot.
       2. When someone creates a bot from your template, they can specify any language supported by your template as a primary or secondary language for their bot.
       3. When someone imports your block, the block is automatically supported in all languages supported by the block and the destination bot.
20. Transition to the Lightning Editor for Email Composers in Email-to-Case (Beta) (Release Update): – When enabled, this release update replaces the email editor in the docked and case feed email composers. The new email editor is available in Lightning Experience as a beta feature.
    1. This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
    2. Salesforce is replacing the email editor in the docked and case feed email composers and switching to an editor that’s based on the open-source TinyMCE editor. The new editor provides similar functionality in Lightning Experience. New features include:
       1. Full-screen mode
       2. Printing
       3. Undo and Redo buttons
       4. Format painting
       5. Emoji picker
       6. Resizability
       7. A more responsive toolbar
       8. Smart copy-paste functionality
    3. You can drag, as well as copy and paste, file attachments and inline images into the editor.
21. Send Automated Notifications with the Send Conversation Messages Action: – Send important updates to customers with messaging components and a new invocable action. This feature is now available in enhanced WhatsApp channels and Messaging for In-App and Web. Previously, you could send automated notifications only in standard Messaging channels.
    1. This change applies to enhanced WhatsApp and Messaging for In-App and Web channels. View required editions.
    2. <<Steps to Implement>>
       1. To set up automated notifications in enhanced WhatsApp channels, get the WhatsApp Outbound Messages add-on license. Then, create a message template in WhatsApp Business Manager. Templates must fall into one of the three WhatsApp categories: Marketing, One-Time Passwords, and Transactional. After creating a template, create a Notification messaging component in Setup, link it to the template, and create a flow that uses the Send Conversation Messages action to send the messaging component. Sending a notification to a customer consumes one outbound message.
       2. To set up automated notifications in Messaging for In-App and Web, create a Notification messaging component in Setup. Then, create a flow that uses the Send Conversation Messages action to send the messaging component.
22. Improve Customer Service and Agent Training with Conversation Sentiment Analysis: – To evaluate agent performance and identify coaching opportunities, supervisors can view the sentiments of a phone conversation between an agent and a customer inside the recording player. The supervisor can easily spot moments when the customer or agent is not happy, listen to the corresponding recorded call segments, and then provide training. In addition to Sentiment Journey, we added Agent Sentiment Score and Supervisor Sentiment Score fields to the VoiceCall entity for easy reporting. Post-call Sentiment Journey is available for contact centers in North America only.
    1. This change applies to Lightning Experience in Enterprise and Unlimited editions. Available in Salesforce orgs with these telephony models: 
       1. Service Cloud Voice with Amazon Connect
       2. Service Cloud Voice with Partner Telephony from Amazon Connect
    2. <<Steps to Implement>>
       1. In the Call Audio Player component of a Voice Call record, view the overall sentiments of the agent and customer alongside the call recording after the conversation. To view the sentiment scores for the agent and customer, add the fields to the Voice Call page layout or include them in a report.
23. Listen In to an Amazon Connect Voice Call through Salesforce: – To support an agent, supervisors can listen in to a call directly from Salesforce through Omni Supervisor. Previously, supervisors had to listen in from Amazon Connect.
    1. This change applies to Lightning Experience in Enterprise and Unlimited editions. Available in Salesforce orgs with these telephony models: 
       1. Service Cloud Voice with Amazon Connect
       2. Service Cloud Voice with Partner Telephony from Amazon Connect
    2. <<Steps to Implement>>
       1. In Amazon Connect, turn on Enable Multi-Party Calls and Enhanced Monitoring.