Supported Browsers for Salesforce Classic

Salesforce Classic is supported with Microsoft® Internet Explorer® 11 version, Apple® Safari® latest version on macOS. The most recent stable versions of Microsoft® Edge Chromium, Firefox®, and Google Chrome™ are also supported.

Customers/Administrators Point of View

1. Get Zoom Integration Features with Salesforce Meetings: – Zoom Integration features are now available for Salesforce Meetings users when Einstein Activity Capture is enabled. Capturing data about reps’ video calls collects valuable metadata for insights into each Zoom meeting. Plus, reps who use Salesforce Inbox can generate links to Zoom meetings when they schedule meetings using Insert Availability.
2. Power Up Recently Viewed Lists with Customizable Actions: – Now you can add custom actions to your Recently Viewed lists. To be consistent with other list views, Recently Viewed lists now show the actions added to an object’s list view search layout. Some actions, such as Printable View, aren’t available on Recently Viewed lists. This feature originally was available in Spring ’21, then temporarily removed. It’s rereleased now with performance improvements and the option to disable custom actions.
3.  Show Your Users Three Custom Walkthroughs for Free: – Now you can create as many walkthroughs as you want, showing your users up to three at a time. If you want to show them more, subscribe to myTrailhead. Previously, activating custom walkthroughs for your users required a myTrailhead subscription or a free trial.
   • To show more than three custom walkthroughs to users, subscribe to myTrailhead to get the Walkthroughs permission set license and the Access Walkthroughs permission set. Assign the View Walkthroughs user permission to users you want to be able to see walkthroughs. 
4. Control the Visibility of In-App Learning with Trailhead in Your Org: – In-App Learning with Trailhead is on by default in your Salesforce org, so you can dive in and start setting up learning assignments for your users. Until you customize In-App Learning, users see three modules suggested by Salesforce in the learning panel and on Learning Home. You can now turn off In-App Learning from the In-App Learning page in Setup.
5. Install More Custom Fields: – The total hard limit for custom fields per object has been increased to 900, so now you can allocate more fields to the different use cases that you support. 
   • Each Salesforce edition has a limit on the number of custom fields per object that you can create and install. The new 900 limit on custom fields per object allows you to install more fields from AppExchange. For example, for the Unlimited Edition, you can create 800 custom fields on an object and install 100 fields from a managed package. The custom field limit can’t exceed 900, so if you’re approaching the limit, Salesforce recommends that you hard delete or erase custom fields that you no longer need.
   • The new 900 fields hard limit applies only to these objects.
     • Account
     • AccountContactRelation
     • Asset
     • Campaign
     • CampaignMember
     • Case
     • Contact
     • Custom Object
     • Individual
     • KnowledgeArticleVersion
     • Lead
     • Opportunity
     • OpportunityLineItem
     • Order
     • OrderItems (Order Product)
     • Product2 (Products)
     • Solution
     • Users
     • UserRole (Role)
6. Record Calls by Default: – You can now enable default recording for Dialer. Your users can still decide whether to record individual calls. It’s up to users to comply with any privacy rules and regulations.
7. Create, Edit, and Delete Tasks with the Customer Community Licenses: – Update tasks with Customer Community licenses. Users can create, edit, and delete tasks that they own. They can also create tasks for other users and make updates on tasks that are shared with them.
8. Share Records Owned by High-Volume Users with Unauthenticated Guest Users: – Select whether to include records owned by the high-volume community or site users when you create guest user sharing rules. By default, guest user sharing rules include only records that match the rule’s criteria and are owned by authenticated users, guest users, and queues. Because of recent security improvements, this setting is the only way to grant guest users access to records owned by high-volume users. This option isn’t available for owner-based or criteria-based sharing rules.
9. Pre-configure Lightning Templates in Case Support Settings, Web-to-Case, and Case Auto-Response Rules: – Lightning templates are compatible with Support Settings when auto-assigned through Service Setup Assistant, which means agents now have instant access to three powerful tools. Automate the Case Creation and Edit functions, instantly create and send a Customer Satisfaction Survey or Net Promoter Score, and let Salesforce handle notification emails to help boost agent productivity when a case owner changes.
10. Use a Service Account with Microsoft Exchange: – If you use Microsoft Exchange Server 2019, 2016, or 2013, you can connect Einstein Activity Capture with a service account. Service accounts give you more control over which users Salesforce can access data from. Plus, Einstein Activity Capture users don’t connect their own accounts, which simplifies the rollout.
11. Track the Number of Active Licenses in Your Org: – Use the new Active Licenses tab in the Lightning Usage App to monitor your active, assigned, and available licenses. You can track data for user licenses, permission set licenses, and feature licenses. License metrics help you quickly determine if you need more licenses, or if users are assigned licenses they no longer need.
12. Prepopulate Dependent Picklists with Default Values: – You can now prepopulate a record event with default values in dependent picklists. Default values on dependent picklists are available on accounts, opportunities, cases, contacts, leads, and custom objects.
13. Share Financial Deals with Multiple Users or Groups: – Help deal teams easily share financial deals with multiple participants at a time in a compliant manner. When you add the new Manage Participant component to a financial deal record page, they can add multiple users or groups as participants to the record, and also assign roles from within the component. The component also provides them a suggested list of users or groups to add to the record.
14. Measure Forecasts Your Way in Lightning Experience: – Now you can base forecasts on custom fields of the currency or number data types. This change means that you have more flexibility to reflect your business model with Collaborative Forecasts.
    1. Here’s an example. Using the setup flow, create a forecast type based on the Megawatts field on the Opportunity object.
15. Streamline Scheduling by Limiting Rule Validation Checks: – Manage the frequency and triggers of your automatic rule violation checks and let dispatchers validate rules on demand for more efficient scheduling. With custom permissions, dispatchers can manually check rules for service appointments from the Gantt chart or list, or they can use the Check Rules button for all loaded services.
16. Redirect Expired Tabs to a Custom Logout URL: – For Salesforce sessions, you can now redirect all expired tabs in your browser to a custom logout URL. Previously, the redirect URL wasn’t applied to all expired tabs. Instead, only one tab was being redirected correctly, and the other tabs were redirected to Salesforce.com.
17. See the Engagement Success of Each Sales Cadence Step: – Let sales managers see the effectiveness of their sales cadence steps with the new Sales Cadence Engagement component. On sales cadence pages, managers can view engagement rates and totals for each email template or call the script on each step so they can make updates to better drive their pipeline.
18. Get More Clarity and Control on Email Marketing Settings: – Upgrade your mailability model for simplified email marketing settings and more clarity about a prospect’s mailable status. After you upgrade, prospect records include a mailability section showing the factors that determine whether the prospect can receive marketing emails. View their overall mailable status, Do Not Email and Opted Out settings, and bounce information. And edit these settings in Automation Rules, Engagement Studio, and prospect import.
19. Welcome to Service Setup: – Based on customer request Salesforce is now introducing getting started with an out-of-the-box Service app, so the Service Setup Assistant now takes care of even more tasks to make setup easier. The Assistant gives you a default help center, automated case email notifications, and sample data such as macros and flow recommendations to help you get to know Service Cloud best practices. It also completes key setup steps for Knowledge and walks you through giving your team access to the features they need.
20. One-Time Passwords Are Getting Longer in Winter ’22: – In Winter ’22, to improve security, Salesforce is increasing the length of one-time passwords (OTPs) used for identity verification from five digits to six digits. If you have customizations that rely on six-digit OTPs, such as custom Apex implementations for multi-factor authentication (MFA) or passwordless login, change them before the Winter ’22 release.

1. Create Quick Actions with Lightning Web Components: – To save your users time and clicks, create a quick action that invokes a Lightning web component. On a record page, create a screen action that shows the component in a window, or create a headless action that executes with a click.
   1. To set up a Lightning web component as a quick action on a record page, define the metadata in <component>.js-meta.xml. Define a lightning__RecordAction target and specify actionType as ScreenAction for a screen action that opens in a window or Action for a headless action that executes when clicked. Here’s the configuration for a headless action.

      <?xml version="1.0" encoding="UTF-8" ?>
      <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
         <apiVersion>52.0</apiVersion>
         <isExposed>true</isExposed>
         <targets>
             <target>lightning__RecordAction</target>
         </targets>
          <targetConfigs>
         <targetConfig targets="lightning__RecordAction">
           <actionType>Action</actionType>
         </targetConfig>
       </targetConfigs>
      </LightningComponentBundle>

   2. To use a headless action, add an exposed invoke() method to your component.

      import { LightningElement, api } from "lwc";
       
      declare default class HeadlessSimple extends LightningElement {
        @api invoke() {
          console.log("Hi, I'm an action.");
        }
      }

2. Improve Page Performance with Custom Lightning Component Analysis: – Get insights on custom Lightning components on your Lightning record pages. Updates to the Lightning page analysis tool in the Lightning App Builder give you more performance predictions for your Lightning page.
3. Get an Improved Experience from Forecast Types in Setup: – Forecast type administration has a whole new look and feel. Now a setup flow guides you through the steps to create forecast types. Then you manage your forecast types on the Forecast Types page. The Setup redesign makes it easy.
   1. To get started, select Forecast Types from the Setup tree. If you’re using Salesforce Classic, switch to Lightning Experience to find the Forecast Types page. Forecast type administration is now available in Lightning Experience only.
   2. Next, click Create a Forecast Type, and then move through the setup flow to select an object, measure, date type, and hierarchy to forecast on. Optionally, specify a split type or product family grouping. Give the forecast type an appropriate name. And choose the opportunity fields to show as columns in the opportunity list.
4. Create Styling Hooks for Lightning Web Components: – To expose styling hooks for your custom components, use CSS custom properties. CSS custom properties also make code easier to read and update.

    To define a CSS custom property in a component’s style sheet, prefix the property with —. To insert the value of the property, use var()

   :host {
       --important-color: red;
   }
   
   .important {
       color: var(--important-color);
   }

   CSS custom properties are inherited. Inherited properties pierce the shadow DOM. Some CSS properties, like color, are also inherited. Because CSS custom properties are inherited, a consumer can set their values at a higher level in the DOM tree and style your component.

   These CSS custom properties create styling hooks for two themes: light and dark. Pass the fallback value as an optional second parameter to var().

   /* myComponent.css */
   
   .light {
       background-color: var(--light-theme-backgroud-color, lightcyan);
       color: var(--light-theme-text-color, darkblue);
   }
   
   .dark {
       background-color: var(--dark-theme-background-color, darkslategray);
       color: var(--dark-theme-text-color, ghostwhite);
   }

   A consumer can set values for the styling hooks to change the theme colors.

   /* consumerComponent.css */
   
   :host {
       --light-theme-backgroud-color: honeydew;
       --light-theme-text-color: darkgreen;
       --dark-theme-background-color: maroon;
       --dark-theme-text-color: ivory;
   }

5. Identify and Match Event Messages with the EventUuid Field: – Platform event messages now include the EventUuid field, which identifies an event message and is available in subscribers using API version 52.0 and later. Use this field to match published and received event messages by comparing the UUIDs of the received events with those returned in the SaveResult of publish calls. This way, you can find any event messages that aren’t delivered and republish them.
6. Prevent Validation Errors in a Repeat Component: – If you see a validation error when selecting a value in a <apex:selectList> page component that’s within a repeat component, use the new Boolean attribute called skipValidationInRepeat to skip validation of the selected value.
7. Securely Access Aura Components (Update): – This update ensures that an external component with access=”public” is accessible only to other components within its same namespace or to internal Salesforce components. This update is enforced in Winter ’22.
   1. Fixing this issue can reveal other issues that were previously undetected. For example, before this update, a callback that wasn’t wrapped in $A.getCallback() could lose its context but still run successfully. After this update, if a callback loses its context, the access check fails with an error. We recommend performing these testing steps in a sandbox environment to evaluate the release update’s impact and fix any component access errors before it’s auto-enabled in Winter ’22.
      1. From Setup, in the Quick Find box, enter Release Updates, then select Release Updates.
         
      2. For Enable Aura Component Access Fix, enable the release update test run.
         
      3. Test pages with custom components and watch for any error messages such as Access Check Failed! in the console log.
         
      4. Fix any broken components.
         
      5. When manual testing is complete, disable the release update test run and transfer the code changes to production.
         
      6. In production, enable the release update or wait for it to auto-enable in Winter ’22.
8. Attach Actions to Asynchronous Apex Jobs Using Transaction Finalizers (Generally Available): – With Spring ’21, the Transaction Finalizers feature is generally available. The System.FinalizerContext interface contains four methods.
   • getAsyncApexJobId method: Returns the ID of the Queueable job for which this finalizer is defined.
     
   • getRequestId method: Returns the request ID shared by both the finalizer execution and the Queueable job to which the finalizer is attached. This shared ID helps in filtering logs of a Queueable job and its attached finalizer.
     
   • getResult method: Returns the System.ParentJobResult enum, which represents the result of the parent asynchronous Apex Queueable job to which the finalizer is attached. Valid values for the enum are SUCCESS, and UNHANDLED_EXCEPTION.
     
   • getException method: Returns the exception with which the Queueable job failed when getResult is UNHANDLED_EXCEPTION, null otherwise.To attach actions to your Queueable jobs, you must implement the Finalizer interface. Only one finalizer instance can be attached to any Queueable job. You can enqueue a single asynchronous Apex job (Queueable, future, or batch) in the finalizer’s implementation of the execute method. Callouts are allowed in finalizer implementations.
9. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Use Is Changed in Condition Logic for Start Elements and Decision Elements: – Use the new Is Changed operator in your condition logic for Start elements and Decision elements in record-triggered flows. With the Is Changed operator, you can define conditions that check whether certain field values on the record changed in the current transaction.
   2. Use ISCHANGED, ISNEW, and PRIORVALUE in Record-Triggered Flow Formulas: – Record-triggered flows for new and updated records now support the ISCHANGED, ISNEW, and PRIORVALUE formula functions. Copy your Process Builder or workflow rules formulas containing these functions into record-triggered flows. None of these formula functions are available in flows triggered when a record is deleted.
   3. Sort and Limit Data in a Collection: – Now you can use the Collection Sort element to prioritize and limit your collected data. You can also limit the remaining items in the collection variable after the sort. For example, you can sort a collection of user-chosen products by preference and pricing. You can also reduce a record collection variable to only the top 100 priority accounts, ensuring that the flow doesn’t hit the element limit when that collection variable is processed by a large loop. Previously, it wasn’t possible to reorder the values. It also was difficult to separate a collection variable’s highest or lowest values and to avoid hitting flow limits when looping through a large collection.
   4. Directly Update Fields in Record-Triggered Flows: – With a new option in the Update Records element for record-triggered flows, you can directly update the record that triggered the flow. Previously you set filter criteria for the triggering record with a Decision element, but now you can use the Update Records element. The Update Records element only displays fields you can update, and the new option is available in all record-triggered and schedule-triggered flows. These changes mean you can now easily switch between record-triggered flows that run before or after the record is saved. Existing before-save record-triggered flows that use an Assignment element to set values for the record that triggered the flow are unaffected by this change.
   5. Create Scheduled Paths in Auto-Layout (Beta): – Now you can create scheduled paths while in auto-layout. This ability is similar to using scheduled actions in Process Builder or time-dependent actions in workflow rules, but now in auto-layout Flow Builder. Scheduled paths that can run part of a record-triggered flow after its triggering effect were added in Spring ’21.
   6. Place Fields from Your Salesforce Objects Directly on Flow Screens (Beta): – Now you can build screen flows faster by directly adding your existing Salesforce record fields. When you add a record field to a flow screen, the field’s name, data type, help text, requiredness, and existing values are automatically configured for you.
   7. Find Failed Flows Faster: – Skip your inbox and go straight to the new Failed Flow Interviews list view. Now, if your flows have failed interviews, you can find them all in one place. You can create a custom list view that includes paused and failed flow interviews. Previously, you clicked a link in a flow error email to start debugging a failed flow interview.
      1. In Setup, Paused Flow Interviews changed to Paused and Failed Flow Interviews. The Setup page now includes list views for flow interviews that are paused or have failed. The list views include more list view controls such as Sharing Settings and Select Fields to Display.
      2. From Setup, enter flow in Quick Find box, and then select Paused and Failed Flow Interviews. The default list view is Paused Flow Interviews.
      3. To open the flow interview in Flow Builder, click the interview label.
   8. Debug Flows After Pause Elements in Flow Builder: – Now you can continue to debug a flow even after a Pause element is executed. If the pause conditions are met, you can choose a pause configuration that resumes the flow. Only pause configurations that run at a specific time is supported. Previously, you couldn’t resume a flow after a Pause element when you debugged a flow in Flow Builder.
      1. Debug the flow and select Debug pause element behavior.
      2. Choose a pause configuration and continue debugging the flow.
      3. If pause conditions aren’t met for pause configurations that run at a specific time and the flow has no default path to take, the flow doesn’t resume.
   9. Debug a Flow to See When Transactions Are Committed: – Schedule-triggered flows and autolaunched flows that have no triggers can now show debug details for transactions that are committed or that are rolled back due to an error. If a flow fails, you can debug the flow to see whether record changes were permanently saved to the database via committed transactions before the failure.
      1. Debug a flow in Flow Builder, and then from Debug Details, click Basic Debug Log. Select Show Governor Limit Consumption or Show Transaction Boundaries or both.
      2. We moved the Show query limits in debug details check box from the Debug flow window to the debug details, so you can choose the details as you view them.
   10. Debug Flows in Auto-Layout (Beta): – With just a couple of clicks, debug your flow in auto-layout. Get the same rich and contextual debugging experience for flows built-in auto-layout that you do for flows built-in free-form. Debug directly on the canvas, or via a link in a flow error email. Welcome to a new era of simplified debugging!
10. Do More with Branches in Unlocked and Second-Generation Managed Packages: – Development teams who use branches in their source control system (SCS) often build package versions based on the metadata in a particular branch of their SCS. To make it easier to identify which branch a package version is based on, we enhanced the branch attribute. You can specify the branch name for a package version or a package dependency in the sfdx-project.json file, or directly on the command line using Salesforce CLI.
11. Manage Access for Apex Tests That Run at Package Version Creation: – Sometimes the Apex tests that you write require a user to have certain permission sets or permission set licenses. Previously, test-specific permissions had to be added to each Apex test. Now you can use the apexTestAccess setting in the sfdx-project.json file, and assign permission sets and permission set licenses to all the Apex tests in your package.

    Assign permission sets and permission set licenses in the sfdx-project.json file. These permissions are assigned to the user in context when the Apex tests run at package version creation.

     "apexTestAccess": {
                   "permissionSets": [
                       "Permission_Set_1",
                       "Permission_Set_2"
                   ],
                   "permissionSetLicenses": [
                       "SalesConsoleUser"
                   ]
               }

12. Disable Access to Non-global Apex Controller Methods in Managed Packages (Update, Enforced): – This update corrects access controls on Apex controller methods in managed packages. When this update is enabled, only methods marked with the global access modifier are accessible by Aura components from outside the package namespace. These access controls prevent you from using unsupported API methods that the package author didn’t intend for global access.
    1.  To test this update, we recommend working in a sandbox. After April 4, 2021, you can continue to activate or deactivate the update from Release Updates in Setup until the update is automatically enforced when your org is upgraded to Summer ’21.
       1. From Setup, in the Quick Find box, enter Release Updates in the Quick Find box, and then select Release Updates.
       2. Find Disable Access to Non-global Controller Methods in Managed Packages, and click View Details or Get Started.
       3. Test that your custom Aura components are working correctly.
13. Enforce Access Modifiers on Apex Properties in Lightning Component Markup (Update, Enforced): – This update makes Lightning components consistent with the use of Apex properties in other contexts. For example, a markup expression can no longer access an Apex property with a private Apex getter. This release update doesn’t affect usage of Apex setters.

    Let’s look at an example for an Apex class with a private getter for a counter class property.

    public class EnforcePrivateGetter {
        @AuraEnabled
    
        public Integer counter { private get; set; }
    
        @AuraEnabled
        public static EnforcePrivateGetter GetRepro2()
        {
            EnforcePrivateGetter result = new EnforcePrivateGetter();
            result.counter = 2; 
            return result;
        }
    }

    With the update enabled, this Aura component can’t access the private getter with the {!v.apexObject.counter} expression. The same restriction applies for a Lightning web component.

    <aura:component controller="EnforcePrivateGetter" access="global">
        <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
    
        <aura:attribute type="EnforcePrivateGetter" name="apexObject" />
    
        counter = {!v.apexObject.counter} <br></br>
    </aura:component>

    Here’s the JavaScript controller.

    ({
        doInit : function(cmp, ev) {
            var action = cmp.get("c.GetRepro2");
        
            action.setCallback(this, function(response) {
              var state = response.getState();
              if (state === "SUCCESS") {
                cmp.set('v.apexObject', response.getReturnValue());
              }
              else if (state === "ERROR") {
                console.log('Error : ' + JSON.stringify(errors));
              }
            });
            $A.enqueueAction(action);
        }
    })

    With the update enabled, the fix is to remove the private access modifier on the getter and change the class variable definition to:

    public Integer counter { get; set; }

    To make an Apex property readable outside the Apex class, the property can’t have a private or protected access modifier.

14. Create Package Versions Based on the Upcoming Release – During major Salesforce release transitions, you can now specify preview or previous when creating a package version. In Spring ’21, we added the ability to specify the previous release. Specifying the release version for a package allows you to test upcoming features, run regression tests, and support customers regardless of which Salesforce release their org is on.

    To create a package version based on the upcoming Salesforce release version, create a scratch org definition file that contains:

    {
        "release": "preview"
    }
    

    In the sfdx-project.json file, set the sourceApiVersion to correspond with the release version of the package version you’re creating.

    Then when you create your package version, specify the scratch org definition file.

    sfdx force:package:version:create --package pkgA --definitionfile config/project-scratch-def.json

15. New Lightning Web Components – These components are new and require API version 52.0 and later.
    1. lightning-quick-action-panel – Builds quick action modals with the same style as the Salesforce Lightning Design System (SLDS) modal. With this component you can customize screen actions and still have consistent UI across all actions. Use lightning-quick-action-panel with the lightning__RecordAction target to use your custom component as a quick action on a record page. 
    2. lightning-service-cloud-voice-toolkit-api – This component provides access to event listeners and methods for the Service Cloud Voice Toolkit API, enabling your component to listen to events that take place during phone calls with service agents.