Customers / Administrator’s Point of View

1. Major Release Notification Emails Are Streamlined: – To reduce the number of emails you receive, the Release Is Live email is updated, and the Features Enabled email is discontinued. When a major release upgrade is complete for your instance, you receive an email with a subject line that starts with “Release Is Live.” That email now includes updated language about the timing of feature availability. Previously, you received a separate email with a subject line that started with “Features Enabled” that outlined feature availability for the release.
2. Schedule Video Appointments with Amazon Chime: – Salesforce Scheduler now provides integrated Amazon Chime for video calls. The feature operates in the Bring-Your-Own-Application (BYOA) model and requires an Amazon Chime account. After you enable and configure video call settings, Salesforce Scheduler uses Amazon Chime for all its video appointments. Salesforce Scheduler also provides Virtual Appointment Email Templates that you can use to send notifications to unauthenticated users for their upcoming video appointments. This feature is available in the Salesforce Lightning Console and Experience Cloud sites but isn’t available for APIs.
3. Stay Informed on Dashboard and Report Subscriptions: – You’re no longer in the dark about which reports, dashboards, or other analytic assets your users are subscribed to. Manage data access by determining what kind of attachments are sent, who receives them, and who the running user is. Stay on top of scheduling and limits with a quick report showing when subscriptions run and who set them up. Create a custom report type on Analytic Notifications to view the source, owner, running user, and schedule of subscriptions.
4. Edit Queries That Contain Interactions: – Queries that have interactions (bindings) are now editable. Rather than rebuilding the query, you can open a query to view it as a lens and validate results or add format changes, such as conditional formatting for emphasis.
   
   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.
5. Add Salesforce Payments to B2B Checkout: – Give your customers a smooth payment experience for B2B stores created with the LWR template. Use Salesforce Payments to provide credit card support for the template’s checkout component.
6. Activate Segments for Google or Meta Advertising Platforms: – Activate audience segments securely in the Customer Data Platform to use in targeted Google and Meta advertising campaigns. Use out-of-the-box activation connectors to send audience lists to Google and Meta with just a few clicks.
7. Pin Important Content on the Right Side of Record Pages: – Use the new Pinned Right Sidebar (3 regions) template to create record pages in which you can show important information, such as customer details and chats, on the right side of their pages. Your users, such as customer service representatives, can then verify customer identity over various channels, such as web chat, and access customer chats from one place and avoid switching between subtabs or pages.
8. Set Up Amazon DynamoDB External Data Sources with Fewer Clicks: – Use the new setup wizard to define an external data source for Amazon DynamoDB. The wizard walks you through connecting an Amazon DynamoDB data source and integrating the data in Salesforce. Use the guided interface to select the DynamoDB table to map and create an external object in Salesforce from a table with representative sample data.
9. Take Action More Quickly in the Dynamic Activity Composer: – The dynamic activity composer gives reps activities at the click of a button and offers more choices than the tabbed activity composer.
   1. Users click the buttons to perform the action, or they can click the dropdown menus for more actions.
   2. The dropdown menus offer new features. In the Email dropdown, if a user has more than one email address, they can choose from up to three addresses to send the email. Users can also get to their email preferences quickly. And users can easily add email to their to do list.
10. Return Characters in a String in Reverse Order: – Use the Reverse function when building formulas to return the characters of a source text string in reverse order.
11. Open Support Cases with the Contact Support Form Component in LWR Sites: – Use the Contact Support Form in your LWR sites to let users efficiently create cases and easily contact support. The form’s preconfigured fields reduce your cost-to-serve by streamlining the collection of information about the user’s request. The form contains several custom fields you can configure to your company’s preferences.
    1. Previously, you could only use the Contact Support Form component for Aura sites.
12. Require Granular Flow Permissions for Experience Cloud Guest Users Release Update): – In Winter’22, Salesforce discontinued the Run Flows permission for the Guest User and Experience Cloud External User profiles in new orgs. In Spring ’23, Salesforce removes Run Flows from the Guest User profile in all orgs. The change improves site security by requiring explicit guest user permissions to run Flows. To give your users the detailed access they need, use the more granular permission structure embedded in Flows. To avoid future access issues, update your sites to the new permission structure before the enforcement date. This update was first available in Summer’22 and is enforced in Spring’23.
13. Get the Impact of In-Day Optimization With the Optimization Hub Dashboards: – In-day optimization requests continuously optimize your team’s schedule, for one or more service territories, during the day of service. When rapidly responding to last-minute schedule upsets, use the Optimization Hub dashboards to measure improvements in the organizational KPIs following the in-day optimization changes. For example, track improvements in response time to service appointments and in the mobile workers’ workload.
14. Track Asset Performance with Asset Attributes: – Improve asset management and help your mobile workers efficiently repair and maintain assets by defining attributes that represent asset health and performance. Enable asset managers to shift to proactive, and ultimately predictive, service models that promote higher equipment uptime and compliance. Track and analyze multiple asset attributes by defining thresholds using recordset filter criteria. For example, define a threshold based on attribute values, such as engine temperature, engine pressure, engine oil level, engine air influx, and engine RPM. You can then check the engine for faults by monitoring these attributes. Customers who participated in the pilot and beta program must re-create attribute definitions, asset attributes, and recordset filter criteria monitors.
15. Track File Downloads in Near Real-Time with FileEvent (Beta): – With FileEvent in Salesforce Real-Time Event Monitoring, you now get real-time notifications when a user downloads a file containing sensitive information. File Event supports transaction security policies.
16. Set a Cache Duration for CMS Content Served in Salesforce CDN Channels: – You have the flexibility to define how long the Salesforce CDN for Digital Experiences stores CMS content served in a channel. This change can help you optimize content delivery.
    1. To configure the cache duration, open the channel settings, and then enter a value. Set the duration for as little as 1 hour and as many as 8,760 hours, which is 1 year. In a public channel or a site channel, use a long cache duration for images and documents that change infrequently, like your company logo. The default is 720 hours, which is 30 days. In a public channel, for other content types that change frequently and that you want to render soon after you publish, use a short duration. The default is 1 hour.
17. Improve Contact Center Operations with Efficient Shift Scheduling: – Assign agents where and when they’re needed so that customers receive the best support possible from your teams. Shift scheduling includes tools so that your planners can match agents to work shifts effortlessly based on scheduling rules, constraints, and business objectives.
    1. After you set up Salesforce for Shift Scheduling, your planners define the criteria for scheduling decisions, such as Match Territory and Match Skills scheduling rules. Your planners then create shifts to represent the locations and types of work to be done. They can then use the scheduling tools to match agents to shifts.
    2. For example, if you need agents who speak Spanish to handle calls weekdays from 8:00 AM to 5:00 PM, your planners create shifts for those days and times. The shifts use a job profile that specifies Voice and Spanish skills. Your planner can then use the tools—mass shift update, batch assign, or get candidates—to find agents in the right location who have those skills.
18. Learn Who Can Access Records and Why: – Understanding who can access a record is critical to securing record access in your organization. Check out a record’s sharing hierarchy to view who it’s shared with. You can also see the user’s reason for access and find out if a user’s access is blocked by a restriction rule.
    1.  To see a list of users who have access, click Sharing Hierarchy from the Action Menu on the desired record. To see why the user has access to the record or why access is blocked, click View next to the user’s name.
    2. If a restriction rule blocks access to the record, a message appears to confirm that access is blocked.
19. Receive Inbound Files with an Enhanced Bot: – Enhanced bots can now receive files from your customers, so you can reduce agent handle time by collecting files before an agent joins the conversation. For example, a bot can request documentation related to an insurance or a reimbursement claim. Or a bot can prompt a customer for additional information about a possible issue, such as a screenshot of an error message. An agent can then review the files, which are attached to the messaging session and stored in the Files page of Setup. 
    1. In the Bot Builder, on the Dialogs page, drag the File dialog step onto the canvas. In the Step Properties panel, in the File Interaction field, select Receive File. Then enter a message to the customer, specify a variable to save the file reference, and enter file upload success and optional failure messages.
20. Salesforce for Outlook Is Retiring in June 2024: – Full product retirement for Salesforce for Outlook is scheduled for June 2024. For the latest integration with Microsoft Outlook, we recommend moving to our next-generation products, the Outlook integration and Einstein Activity Capture.
21. Limit Increased
    1. Get more actionable reports and dashboards delivered to your inbox on schedule and with the latest data. Each user in an Unlimited Edition org can now subscribe to up to 15 reports and 15 dashboards. The previous limit was 7 reports and 7 dashboards.
    2. Limit the Maximum Number of Loaded Lightning Console Tabs in a Session.

1. Manage and Release Changes with DevOps Center (Generally Available): – Salesforce DevOps Center provides an improved experience around change and release management that brings DevOps best practices to your development team, regardless of where team members fall on the low-code to pro-code spectrum. All developers and builders can work together to deliver value to customers in a repeatable and scalable way.
2. Use Lightning Web Security Enablement for Orgs with No Custom Components: – Lightning Web Security (LWS) for Lightning web components (GA) and LWS for Aura (beta) is enabled by default for orgs that don’t contain custom Lightning web components or Aura components. This enablement continues the gradual rollout of the LWS architecture announced in Spring ’22. If your org has no custom components, this enablement has no impact unless you subsequently add Lightning web components or Aura components or install a managed package that contains Lightning web components or Aura components.
   1. Use the lockerServiceNext boolean in scratch org definition files to enable and disable LWS in your scratch orgs. For example, add these lines to the definition file to disable LWS in your scratch org.
      Copy Code Copied Use a different Browser

      
      "settings": {
           "securitySettings": {
               "sessionSettings": {
                  "lockerServiceNext": false
                 }
            }
      }
      

3. Query DOM Elements with Refs: – Now you can use refs to access elements in shadow DOM and light DOM. Refs locate DOM elements without a selector and only query elements contained in a specified template. Previously, you could only use querySelector() to locate specific DOM elements.
   1. First, add the lwc:ref directive to your element and assign it a value. To call that reference, use this.refs. In this example, the <div> element has the directive lwc:ref="myDiv", which this.refs references to access the <div> at runtime.
      Copy Code Copied Use a different Browser

      
      <template>
          <div lwc:ref="myDiv"></div>
      </template>
      

   2. Copy Code Copied Use a different Browser

      
      export default class extends LightningElement {
        renderedCallback() {
          console.log(this.refs.myDiv);
        }
      }
      

4. Use the Improved Conditional Directives: – The lwc:if, lwc:elseif, and lwc:else conditional directives supersede the legacy if:true and if:else directives.
   1. With the lwc:if, lwc:elseif, and lwc:else conditional directives, the property getters are accessed only one time per instance of the directive.
      Copy Code Copied Use a different Browser

      
      <!-- conditionalExample.html -->
      <template>
          <template lwc:if={isTemplateOne}>
              This is template one.
          </template>
          <template lwc:else>
              This is template two.
      </template>
      

   2. Both lwc:elseif and lwc:else must be immediately preceded by a sibling lwc:if or lwc:elseif. Pass in an expression to lwc:if and lwc:elseif, but not to lwc:else. If expression1 returns a truthy, none of the other property getters are accessed.
      Copy Code Copied Use a different Browser

      
      <!-- example.html -->
      <template>
          <template lwc:if={expression1}>
              Statement 1
          </template>
          <template lwc:elseif={expression2}>
              Statement 2
          </template>
          <template lwc:else>
              Statement 3
          </template>
      </template>
      

5. View Debug Information for Your Wired Properties: – Access debug information for wired properties and methods on a component via custom formatters in Chrome DevTools.
   1. Consider a wired property that looks like this.
      Copy Code Copied Use a different Browser

      
      import { LightningElement, wire } from 'lwc';
      import getContactList from '@salesforce/apex/ContactController.getContactList';
      
      export default class ApexWireMethodToProperty extends LightningElement {
          @wire(getContactList) contacts;
      }
      

   2. To start debugging your wire adapter:
      1. Enable debug mode in your org.
      2. Open Chrome DevTools, and then enable custom formatters.
      3. Find your code in the Sources panel.
      4. Next, inspect your component using this or inspect the rendered custom element. To inspect the rendered custom element, click the <c-apex-wire-method-to-property> element in the Elements panel of Chrome DevTools.
      5. After you click the element, open the Console panel and enter $0 to return the debug information.
6. Synchronize Component Data Without a Page Refresh Using RefreshView API (Beta): – Whether user-driven or app-invoked, the ability to synchronize data without reloading an entire page is a key user experience requirement. The new lightning/refresh module and RefreshView API provide a standard way to refresh component data in LWC and Aura. Previously, LWC lacked a data refresh API, and Aura only supported the legacy force:refreshView, which doesn’t meet the requirements of modern web development. RefreshView API’s detailed control of refresh scope lets developers create refined user experiences while maintaining backward compatibility.
7. Find Which Apex Classes Implement an Interface (Generally Available): –ApexTypeImplementor is now generally available and is updated since the beta release. Use the object to find Apex classes that directly or indirectly implement an interface. Using a SOQL query, you can get information about public or global Apex implementors.
   1. This example demonstrates how an interface allows flexibility in a configuration, record, or user-driven selection of the rounding strategy to apply. The multiple implementations of the interface can be discovered using ApexTypeImplementor and the specific implementation chosen based on user requirements.
      Copy Code Copied Use a different Browser

      
      // Common interface that all rounding strategies will implement
      public interface RoundingStratergy {
          Decimal round(Decimal toRound);
      }
      
      public abstract class RoundingStrategies {
          public class Ceiling implements RoundingStratergy {
              public Decimal round(Decimal toRound) {
                  return toRound.round(System.RoundingMode.CEILING);
              }
          }
          
          public class HalfDown implements RoundingStratergy {
              public Decimal round(Decimal toRound) {
                  return toRound.round(System.RoundingMode.HALF_DOWN);
              }
          }
          
          public class TwoDecimalPlaces implements RoundingStratergy {
              public Decimal round(Decimal toRound) {
                  return toRound.setScale(2, System.RoundingMode.HALF_UP);
              }
          }
      }
      
      List<ApexTypeImplementor> interfaceImpls = [
                  SELECT ClassName, ClassNamespacePrefix
                  FROM ApexTypeImplementor 
                  WHERE InterfaceName = 'RoundingStratergy' and IsConcrete=true];
              
      // For example, an Admin could be presented with a list of Apex classes 
      // that could be applied. Simulated selection of 2 decimal places
      ApexTypeImplementor selectedRoundingStratergy = interfaceImpls[2];
      System.assertEquals('RoundingStrategies.TwoDecimalPlaces',
          selectedRoundingStratergy.ClassName);
              
      // Create an instance of the class that implements the interface
      RoundingStratergy rs = (RoundingStratergy)   Type.forName(selectedRoundingStratergy.ClassNamespacePrefix,
          selectedRoundingStratergy.ClassName).newInstance();
              
      Decimal rounded = rs.round(7.1459);
      System.assertEquals(7.15, rounded);
      

8. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Bring External Data into Flow Builder Without Code (Beta): – Automate processes with external data by creating Flow Builder actions that call web-based service APIs using HTTP Callout. After you add the details of the API, Flow Builder generates a reusable action that you can use right away in Flow Builder and across Salesforce. Set up direct integrations as needed without code or a middleware service, such as Mulesoft. Read this article for more information.
      
   2. Build Screens with Interactive Components (Beta): – Configure supported components or your custom Lightning Web Components to react to changes in other components on the same screen. Previously, components on the same screen couldn’t talk to each other, so if you needed one component to influence another, you placed them on separate screens. Now you can build screens that feel like single-page applications and reduce the number of screens for your user.
      1. Opt into the Beta program from this setting in the Process Automation Settings page from Setup.
      2. By checking “Opt in to Reactive Screens Beta,” you agree that the Unified Pilot Research Agreement governs use of this Beta feature in this Org. View Agreements
      3. Add the needed components to your screen. Refer to Record Fields on Flow Screens for complete information on how to set up your components.
      4. Ensure that the output components have API names set.
      5. In the other component, set the appropriate input to an output from the component you set previously. Save and run the flow as usual. Notice that the input component reacts to changes from the output component.
   3. Add Lookup Fields to Your Flow Screens with Ease: – Easily add Lookup fields to flow screens and create a record directly from the Lookup field with Dynamic Forms for Flow. On the Records tab, hover over a Lookup field from your record resource, and then drag in your desired Lookup field. Read this article for step-by-step instructions.
      
   4. See Element Descriptions on the Flow Canvas: – Now you can easily see what each element is doing within a flow in Auto-Layout. Previously, to see the user-provided description, you opened the element.
   5. Select a Value from a List of Choices with the Choice Lookup Component (Beta): – Prompt your users to search for and select an option from a set of choices on a flow screen. With the Choice Lookup (beta) flow screen component, your users can select from a list of external data values, picklist values, static values, or records that you filtered when you configured the flow. For example, rather than asking users to scroll through a long picklist to select a value, use the Choice Lookup (beta) component to enable users to search for values. The Choice Lookup (beta) component supports all choice resources, including collection choice sets and picklist choice sets. Read this article for step-by-step instructions.
   6. Use Flow Screen Components with Flow in Slack (Generally Available): – Screens in flows that run in Slack can contain the following flow screen components: Checkbox, CheckboxGroup, Currency, Date, Date & Time, Display Text, Long Text Area, Number, Picklist, Radio Button, and Text.
      1. In Flow Builder, build a screen flow that includes only screen components supported in Slack. When you save the flow, select the Make Available in Slack checkbox in the Advanced area of the Save the flow dialog box.
   7. Make Paused Flow Interviews Resume in the Same Context (Release Update): – With this update enabled, paused autolaunched flows resume in the same context as when they were paused. Also, for each flow that runs in API version 57.0 or later, user permission to run the flow is verified before an interview resumes. If your Process Builder processes launch flows that contain Pause elements, we recommend configuring those flows to run in API version 57.0 or later. Otherwise, this update can change the context of resumed interviews. Instead of resuming in system context without sharing, the process-launched flows resume in the context specified in the flow version properties. This update was first available in Winter ’21 and enforcement was scheduled for Winter’22. We then postponed the enforcement date to Spring’23 and postponed again to Winter’24.
      
   8. Use More Flow Elements: – The limit of 2000 flow elements was removed. Other limits still apply. In API version 56.0 and earlier, flows could have a maximum of 2000 flow elements.
      
9. Flow Orchestrator: – There are several enhancements in Flow Orchestrator as follows:
   1. Use Advanced Settings for an Orchestration: – Exercise more control over the usage and execution of your orchestration with advanced settings. You can also turn your orchestration into a template and use it as a starting point for creating other orchestrations in Flow Builder.
      1. In Flow Builder, click Save As, and then click Show Advanced.
   2. Enable Sharing for Flow Orchestration Objects (Release Update): – After Enable Sharing for Flow Orchestration Objects is selected, the Manage Flow user permission no longer grants users access to Flow Orchestration objects. The Manage Orchestration Runs and Work Items user permission, along with sharing rules and role hierarchies, control user access to Flow Orchestration objects. Users who run orchestrations and execute work items must still have the Run Flows user permission.
   3. Create a Record-Triggered Orchestration on the Core Tab: – Want to create a record-triggered orchestration? Look no further than the Core tab in the New Flow window to get started.
10. Use the System.enqueueJob Method to Specify a Delay in Scheduling Queueable Jobs – A new optional override adds queueable jobs to the asynchronous execution queue with a specified minimum delay (0–10 minutes). Using the System.enqueue(queueable, delay) method ignores any org-wide enqueue delay setting. The delay is ignored during Apex testing.
    1. Here are some cases where it can be beneficial to adjust the timing before the queueable job runs. 
       1. If the external system is rate-limited and can be overloaded by chained queueable jobs that are making rapid callouts.
       2. When polling for results, and executing too fast can cause wasted usage of the daily async Apex limits.
    2. This example adds a job for delayed asynchronous execution by passing in an instance of your class implementation of the Queueable interface for execution. There’s a minimum delay of 5 minutes before the job is executed.
       Copy Code Copied Use a different Browser

       
       Integer delayInMinutes = 5;
       ID jobID = System.enqueueJob(new MyQueueableClass(), delayInMinutes);
       

11. Dynamically Pass Bind Variables to a SOQL Query: – With the new Database.queryWithBinds, Database.getQueryLocatorWithBinds, and Database.countQueryWithBinds methods, the bind variables in the query are resolved from a Map parameter directly with a key rather than from Apex code variables. As a result, it’s not necessary for the variables to be in scope when the query is executed.
    1. In this example, the SOQL query uses a bind variable for an Account name. Its value (Acme Corporation) is passed in using the acctBinds Map.
       Copy Code Copied Use a different Browser

       
       Map<String, Object> acctBinds = new Map<String, Object>{'acctName' => 'Acme Corporation'};
       
       List<Account> accts = 
           Database.queryWithBinds('SELECT Id FROM Account WHERE Name = :acctName',
                                   acctBinds, 
                                   AccessLevel.USER_MODE);
       

12. Discover the Source SObject of a DescribeFieldResult Instance: – Use the new getSObjectType() method to get the SObjectType of a Schema.DescribeFieldResult object. The returned type is that of the source sObject describe object that was originally retrieved, eliminating the need for additional mechanisms to determine parent relationships.
    1.  This example uses the getSObjectType() method to create a Salesforce object of the same type as the passed in field’s originating object and then dynamically populates the field’s value.
       Copy Code Copied Use a different Browser

       
       public class ObjectCreator {
       
           public static sObject createAndSet(Schema.sObjectField field, object fieldValue) {
               Schema.DescribeFieldResult fieldDescribe = field.getDescribe();
               Schema.sObjectType sourceType = fieldDescribe.getSObjectType();  
               sObject newObj = sourceType.newSObject(null, true);
               newObj.put(field, fieldValue);
               return newObj;
           }
       }
       

    2. Here’s how to call the sample createAndSet() method.
       Copy Code Copied Use a different Browser

       
       sObject o = ObjectCreator.createAndSet(Account.Industry, 'Development');
       Assert.isInstanceOfType(o, Account.class);
       Assert.areEqual('Development', ((Account)o).Industry);
       

13. Restrict Anonymous Apex Access to Core Users: – By using the RestrictCommunityExecAnon preference, admins can restrict anonymous Apex execution to core users, such as Standard and CsnOnly users. The feature is enabled by default in new orgs but disabled in existing orgs to avoid disrupting customer usage. When enabled, noncore users can’t execute anonymous Apex regardless of any other user permissions that are set, such as Author Apex. Noncore users include these user types: PowerPartner, Partner, PowerCustomerSuccess, Guest, and CSPLitePortal.
    1. From Setup, in the Quick Find box, enter Apex Settings, and then select Restrict non-core users from executing anonymous Apex.
14. Choose Any Name for a Global Value Set: –When you create a custom global value set in API version 57.0 or later, the developer name is appended with the suffix __gvs. You can now create a global value set with any name that doesn’t conflict with a standard entity of the same name.
    1. This change is transparent except when you:
       1. Use a Metadata API CRUD-based call on the GlobalValueSet metadata type. When you make any CRUD-based call, such as createMetadata(), you must append the suffix __gvs to the fullName field.
       2. Use a CRUD-based call on the GlobalValueSet Tooling API type. When you make any CRUD-based call using SOAP API or REST API, you must append the suffix __gvs to the FullName field.
15. Limit User Profile Access for Packages Installed via Metadata API: – When you use Metadata API to install a managed package, you can specify which user profiles in the org can access the package. Use the new securityType field on the InstalledPackage metadata type, and select either all users or admins only. If a security type isn’t specified, the default behavior provides access to the package to all user profiles in the org.
16. Monitor and Analyze System Performance with Scale Center (Beta)): – Scale Center provides self-serve and near real-time access to your Salesforce performance metrics, helping you build and scale apps with confidence. With Scale Center, you can monitor production health and performance metrics, identify scale hotspots and view detailed diagnostics during performance testing, resulting in high-performing apps on the Salesforce platform.
    1. You can enable Scale Center in sandboxes and in production on first-party infrastructure (1P) and Hyperforce.
    2. From Setup, in the Quick Find box, enter Scale Center, and then select Scale Center. To join the Scale Center beta release, contact your Program Architect and Account Executive.