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. Choose Where Your Prompts Appear: – Now you can choose the page and app that you want your prompt or walkthrough to show up on. Previously, when you created in-app guidance, your only option was for a specified page and app.
   
   1. As you create a prompt or walkthrough, select an option from the Prompt Location dropdown.
2. Clear Workspace Tabs for New Console Sessions: – Start new console sessions without loading workspace tabs from previous sessions. Only admins with the View Setup and Configuration and Customize Application permissions can enable this feature.
   1. To enable this feature, navigate to App Settings, select App Manager. Under Setup and Personalization, select App Personalization Settings. Select Clear workspace tabs for each new console session.
3. Manage Service Resource Availability by Using Shifts: – Service territory managers can use shifts to easily create, edit, and view the ever-changing working hours of service resources. Service territory managers can also create one or more tentative shifts and assign a service resource to a shift. The assigned service resource can acknowledge and confirm the tentative shift. Service resources can set up and update their own working hours. Service resources can also set up shifts beyond their service territory’s operating hours and even set up shifts for more than one service territory. Both service territory managers and service resources can directly create confirmed shifts. A shift is applicable only when confirmed. You can also access the Shift entity via Experience cloud or APIs.
4. Use Natural Language Search with Tasks: – Natural Language Search (NLS) just got better. Your users can now enter NLS queries for task objects. In the search box, enter phrases like my tasks this week or tasks with status in progress. Einstein Search evaluates the query and finds matching records. 
   
5. Set a Redirect for Unpublished Pardot Landing Pages: – You can now configure redirect settings that activate when an enhanced landing page is unpublished. Previously, when a Pardot landing page is removed from the web, a default redirect sends visitors to the website listed in your Pardot Settings. The new Redirect Target field on a landing page record can support the default website or a custom URL that you provide.
6. Add Scripts to Pardot Landing Pages: – Enhanced landing pages now support script code, such as the JavaScript used to support Google Analytics tracking. You can add code to the header or footer of an individual landing page, using <link>, <script>, and <style> tags.
7. JWT Bearer Flow Supports High Assurance Sessions: – The OAuth 2.0 JWT bearer flow for server-to-server integration now supports high assurance settings. Previously, high assurance settings in user profiles weren’t passed to access tokens retrieved during the JWT bearer flow. 
   
8. Let Users Access Salesforce with Slack Credentials: – Simplify your users’ login experience by enabling single sign-on (SSO) with a Slack authentication provider. With this SSO solution, your users can log in to your Salesforce org or Experience Cloud site with their Slack credentials, saving them time and clicks. They can also access their protected Slack data in Salesforce.
   
9. Say Hello to the Digital Experiences App in Lightning Experience: – After we started adding new Digital Experiences settings to the Salesforce CMS app in Lightning Experience, it didn’t make sense to keep on calling it CMS anymore. So to keep in line with the Setup menu, we changed the name of the Salesforce CMS app to Digital Experiences. Now, in addition to managing your content, you can use this app to see your site’s details and the underlying framework that it’s using and to archive or unarchive your site.
   1. Use the app launcher to access the Digital Experiences app (1).
   2. For consistency, Salesforce renamed CMS Home to Digital Experiences Home (2), and
   3. the All Experiences and CMS Experiences tabs are now called All Sites (3).
      
10. Support More Site Members with Experience Cloud Licenses: – Customer Community licenses now support six times as many site members. Customer Community Plus and Partner Community licenses with account role optimization can now support four times as many site members.
    
11. Keep Your Quip Users Working in Lightning Experience with Admin Control Enhancements: – Ensure that your users work on embedded Quip documents and spreadsheets in Lightning Experience instead of Quip.com. Remove the Open in Quip button from Lightning Experience so that your users always collaborate within the context of your Salesforce records.
    
12. Share Knowledge Article Links that Don’t Expire: – Copy a knowledge article link and share it without worrying about the article version number. With the new Copy Article Link button in Knowledge layouts, you generate a link that points to the latest published version, even if you update the knowledge article after creating the link.
13. Fine-Tune Operating Hours with Holidays: – Help your team enjoy their holidays. Create holidays and apply them to a service resource or a territory. Holidays mark operating hours and shifts as an unavailable times to give the team members time off.
    
    1. To associate operating hours with a holiday, click the plus icon, set the territory that the holiday is applied to, and then from search enter the holiday that you want and select it.
14. Create Account-Specific Work Plans: – Now you can associate flows and procedures to account Work Plans. For example, a company has safety and security protocols for its mobile workers. With account-specific work plans, you can attach these requirements to the work order that’s assigned to the company’s account.
    
15. Use Colors to Find Shifts Fast: – When your team creates shifts, they can assign background colors to represent different shift types, such as for certain job profiles. Shift managers can also add background colors to shift templates so that they can create color-coded shifts in a snap. Background colors appear in the shift calendar and the dispatcher console Gantt.
16. See Pipeline Changes from the Flow Tab: – Pipeline Inspection users can see the changes to their pipeline from the Flow tab. This chart shows the changes to opportunities in different forecast categories over time. Users can filter results to see the data that’s most useful to them.
    
17. Get Insights from Core Forecasting KPIs Quickly: – Now you can include columns in your forecasting grid that calculate Gap to Quota and Pipeline Coverage metrics automatically. We simplified the process by providing two ready-to-use calculated columns. Calculating forecasting metrics manually can be time-consuming and subject to user error.
    1. Through the setup process, an admin can configure Forecasting to provide Gap To Quota and Pipeline Coverage calculations.
       
    2. When enabled, the Gap To Quota and Pipeline Coverage columns show on the Forecasts page.
       1. The Gap To Quota column lets your sales team know at a glance how close they’re to achieving their quota, without them calculating the gap manually. The column calculates the Gap To Quota metric automatically by subtracting the closed sales amount from your sales quota.
       2. The Pipeline Coverage column lets your sales team know the ratio of opportunities in the sales pipeline over your sales team’s Gap to Quota. The ratio shows the sales team how much pipeline remains, compared to how much quota they must close.
18. Pause Sales Cadence Targets for a Specific Length of Time: – Now when a prospect is out of the office or asks to be contacted later, sales reps can pause the target in its sales cadence and choose when to resume the target.
19. Reduce Email Fatigue with Einstein Engagement Frequency: – Einstein Engagement Frequency scans individual customer engagement behaviors to predict the optimal send frequency for marketing emails. The frequency category is stored in a prospect field, and can be used to filter prospect lists or as criteria in Engagement Studio.
    
    1. Enable Einstein Engagement Frequency in Marketing Setup. When adequate data is detected, the model is typically trained within 72 hours. After frequency categories appear on prospect records, users can select the field as criteria to create dynamic lists or Engagement Studio rules.
20. Enable Stronger Protection for Your Users’ Personal Information (Release Update): – Enable Enhanced Personal Information Management to prevent external users, such as a portal or community users from accessing other users’ personal information. This feature, which replaces the Hide Personal Information setting, secures more personally identifiable information (PII) user record fields. You can also decide which custom and standard user fields are considered PII. 
    1. When you enable the permission, Salesforce blocks 30 personal information fields using a field-set called PersonalInfo_EPIM. Customize the user fields that are concealed by adding or removing them from this field-set.
21. Access External Services Actions in Flow as a Guest User: – Community guest users now can run flows that contain External Services actions if they have access to the flow in Experience Builder. Previously, Community guest users couldn’t get that access, and you opened a support case to request it for them.

1. Create Custom Components for Email Template Builder: – With custom components, you can help marketers and managers create more engaging email content for their customers.
   1. To configure a custom component to use in the Email Template Builder, define the metadata in <component>.js-meta.xml. Define a lightning__StaticEmail target, and set <isExposed> to true.
2. Test and Plan Your System for Scale Using Performance Assistant: – Performance Assistant is your central hub of information and resources about scalability and performance testing with Salesforce. Use the step-by-step instructions, articles, and tools to help you architect your system, conduct performance testing, and interpret your results.
   1. To access Performance Assistant, from Setup, in the Quick Find box, enter Performance Assistant, and then select Performance Assistant. Performance Assistant guides you through the three phases of performance testing: Prepare, Execute, and Analyze and Optimize.
   2. In each phase, the Performance Assistant provides guidance and resources to help you test your system with confidence. You can revisit any stage of Performance Assistant during your round of testing. We recommend that you integrate performance testing into your release cycle.
3. Capture and Add New Prospects to Sales Cadences with a Bot Template: – The new Sales Prospecting Bot template comes prebuilt with conversational text and Salesforce flows that capture prospects, connect prospects with sales reps, and add prospects to sales cadences automatically. You can create dialogs for common sales use cases such as answering frequently asked questions and directing website visitors to appropriate resources. Process customer input right away with the bot template’s preloaded intent data, and add new intent data for your unique business needs. 
   1. On the Einstein Bots page in Setup, create your first bot by clicking Create a New Bot. If you have existing bots, click New. Then choose the Sales Prospecting Bot template.
4. Build Your Bot with Confidence in Conversation Canvas: – Goodbye searching through menus, hello streamlined conversation design. Conversation Canvas reimagines the Bot Builder to make it easier to build and edit bots, visualize the flow of the bot conversation, and discover new and useful features.
   1. When you add a dialog step to the canvas, you see only the core conversational elements in the center of your screen. We’ve moved the configuration details to a separate Step Properties panel.
   2. The dialog steps dynamically update with important information from the Step Properties panel, such as required conditions for an action or the destination of a transfer. So you can visualize what your bot does and says without previewing the bot live.
5. Build Localized Component Labels on LWR Sites with Custom Labels: – Use the expression {!Label.namespace.name} to define a label’s value when you specify labels in Experience Builder. Use the expression in any component that has a text input field: Button, HTML Editor, Rich Content Editor, or Text Block.
6. Build Einstein Next Best Action Strategies in Flow Builder (Generally Available): – Display a personalized list of recommendations to users while taking advantage of Flow Builder’s features and structure.
   1. To create a strategy in Flow Builder, go to the Flows page in Setup and click New Flow.
   2. Select the All + Templates tab (1), and then select the Recommendation Strategy category (2). Select the Recommendation Strategy flow type (3), and click Create (4).
7. Filter Your Stream of Platform Events with Channels (Beta): – Optimize event processing by receiving only the event messages that match a predefined filter on a custom channel. Create a channel, and configure it with a complex filter that CometD clients can subscribe to. With fewer events delivered to subscribers, subscribers can make more efficient use of the event delivery allocation. This feature, offered the last release as a pilot, has some enhancements and is now a publicly available beta.
   1. With the Customize Application permission, you can configure stream filtering using Tooling API or Metadata API. For the beta release, only one filter and one custom platform event are supported per channel. To create a channel, use PlatformEventChannel. To add a filter expression for a custom platform event, use PlatformEventChannelMember.
   2. This example shows a filter expression value in the PlatformEventChannelMember.FilterExpression field.

      (City__c LIKE 'S%' OR City__c='New York') AND Has_Shipped__c=true 
        AND Delivery_Date__c>2021-10-21T09:30:11-08:00

8. Find Which Apex Classes Implement an Interface: – Use the ApexTypeImplementor 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 classes. In installed managed packages, you get information only about global Apex classes.
   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 is chosen based on user requirements.

      // 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);

9. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Visualize All Your Record-Triggered Flows in One Place with Flow Trigger Explorer: – See and manage your record-triggered flows with Flow Trigger Explorer, a new tool that’s more visual and interactive than the Flows list view. Flow Trigger Explorer shows all of the flows that are associated with a specified object and that run when a record is created, updated, or deleted. For example, quickly see all flows that are triggered to run when a case record is created.
      1. In Flow Builder at the bottom of the Start element for a record-triggered flow, click Open Flow Trigger Explorer for [object name, for example, Opportunity].
      2. Or from Setup, on the Flows page, click Flow Trigger Explorer.
   2. Translate and Customize Button Labels in the Flow Screen Footer (Generally Available): – Sometimes a flow screen’s navigation button doesn’t clearly state what happens when a user clicks it. For example, you’re designing a screen flow and using a Create Records element that creates a contact record. On the flow screen, you change the Finish button to Create Contact and change the Previous button to Go Back. The custom label makes it clear that a contact record is created as a result of the flow. 
      1. To relabel a button, select Use a custom label, and enter the text that you want to use.
      2. To provide translated labels, use Translation Workbench.
   3. Generate Choice Options from Record Collections: – Use existing record collections to generate collection-based choices in a flow. Collection choice sets prevent the need to duplicate the results of a Get Records element, a component, or an action. Instead of querying for a set of records multiple times throughout the flow, you can create a collection once and then use the record collection anywhere that you need it.
   4. Filter Items into a Collection in Flow Builder: – Now you can filter unwanted data from your collections in Flow Builder. Use the Collection Filter element to select a collection and define conditions. When the flow runs, the element outputs a collection with only the items that meet those conditions, leaving your original collection intact.
      1. When defining conditions, you can set the requirements using a formula or logic, such as All Conditions Are Met, Any Condition Is Met, or your own custom condition logic.
   5. Define the Run Order of Record-Triggered Flows for an Object: – Specify a trigger order value to determine the run order of before-save or after-save flows for the same object. Declaratively configure a flow to run before or after another flow. Order your flows to help ensure consistent results without creating overly complex flows, letting you divide automation by teams or logical owners.
   6. Place Flow Elements Automatically with Auto-Layout (Generally Available): – Building flows and aligning elements is easier with auto-layout. Elements on the canvas are spaced, connected, and aligned automatically, saving you time and keeping your canvas neatly organized. Auto-layout is now the default canvas layout for flows. User templates are also now open in auto-layout.
   7. Place More Fields Directly on Flow Screens (Beta): – You can now use record fields to directly add phone, email, and picklist fields to your flow screens. For dependent picklist fields, both the controlling field and the dependent field must be on the same screen.
10. Flow Orchestrator: – There are several enhancements in Flow Orchestrator as follows:
    1. Orchestrate Multiuser Processes with Orchestrator: – Combine your automated processes in a single interface with Orchestrator. Use Orchestrator’s no-code approach to create orchestrations and transform flows into steps organized by stages. Benefits of Orchestrator include more flexibility to create approval processes, better ability to assign work to any Salesforce user and more control over record lifecycles. Use Orchestrator to automate complex processes, and use Flow Trigger Explorer to order record-triggered flows.
       1.  From the Flows page in Setup, click New Flow. In New Flow, click All + Templates and select Orchestrator. Select either Autolaunched Orchestration (No Trigger) or Record-Triggered Orchestrations, and click Next.
       2. Add stages to your orchestration, and then add steps to your stages. Use Decision elements, stage exit conditions, and step entry and exit conditions to determine how your orchestration runs.
    2. Assign Interactive Steps to Groups or Queues: – Avoid process bottlenecks by assigning an interactive step to a queue or public group rather than a specific user. All queue or public group members receive an email when the associated work item is created. When more than one person starts the work item, the step is completed by the first user who completes the associated flow. All other users who were in the process of completing the associated flow, receive an error when they finish the flow. After the first user completes the flow, other users no longer see the work item on the associated context record. Public groups are groups with a type of Regular. Queues are groups with a type of Queue.
    3. Process Background Steps Asynchronously: – You can now mark background steps to be processed asynchronously to prevent orchestration errors. Use this option when the autolaunched flow associated with a background step makes external callouts or contains a Pause element. The in-progress orchestration pauses when an asynchronous background step runs. When the associated flow completes, the orchestration resumes and sets the status for the asynchronous background step to Completed. The orchestration then continues.
       1. In the Details pane of an orchestration background step, select an autolaunched flow, and then select Contains external callouts or pause elements.
    4. Orchestration Deployment (Generally Available): – Use packaging or changesets to move your orchestration and its associated flows from one org to another.
       1. Package – Create a package with your orchestration, and move it from one org to another. We recommend that you create and debug your orchestration in a sandbox environment. When it’s ready, create a package to deploy it to your production environment. 
       2. Change Sets – Use separate change sets for orchestration and its associated flows to send changes from one org to another. An orchestration references screen flows, autolaunched flows, and evaluation flows. Referenced flows must be activated before the orchestration is created or deployed, or the orchestration can’t use them. Flows distributed through a change set are always deployed as inactive in the target org, even if they were active in the source org. This flow limitation means that you must first create a changeset with your orchestration’s flows. Deploy it, and activate all referenced flows in the target org before you deploy your orchestration.
    5. View Orchestration Runs: – Use the All Orchestration Runs list view to see all in-progress, cancelled, and completed orchestrations in your org. You can also access the status for each stage and step associated with an orchestration run and view the orchestration run history.
11. Write More Robust UI Tests with UTAM (Generally Available): – UI Test Automation Model (UTAM) is based on the popular Page Object design pattern commonly used in UI tests. When a web application, such as Salesforce, changes, the DOM of the pages and components in the app also change. Using JSON page objects makes your tests more robust and reduces test maintenance time every time an application UI changes. Because UTAM moves test logic into JSON page objects, you can handle many changes by updating your page objects rather than test code. It’s much less effort to update the JSON page object for a changed component than it is to rewrite complicated UI automation tests.
12. Create Web Apps with Lightning Web Runtime on Node.js (Developer Preview): – From static websites to single-page applications, Lightning Web Runtime (LWR) makes web development fast, secure, and standards-based. With LWR you can create standalone Lightning Web Components (LWC) applications while using your preferred tooling and code. And you get the high performance that comes from page generation at build time, not runtime.
13. Secure Your Components Better, Stronger, Faster with Lightning Web Security (Generally Available): – Lightning Web Security (LWS) is a new client-side security architecture for your custom Lightning web components. The architecture is defined by fewer restrictions and more functionality while providing strong sandboxing and a security posture to enforce namespace isolation. The result is strong, flexible, usable security for your Lightning web components. This feature, now generally available, includes some changes since the beta release.
    1. From Setup, in the Quick Find box, enter Session, and then select Session Settings. On the Session Settings page, select Use Lightning Web Security for Lightning web components.
14. Ensure That Your Code Works in Lightning Web Security with New Tools – Try our new developer tools to ensure that your Lightning web component’s JavaScript code works with Lightning Web Security (LWS).
    1. Lightning Web Security Console – Evaluate your code in Lightning Web Security Console as it runs with LWS enabled and disabled. This tool can help you determine if a problem with your JavaScript code is related to its interaction with LWS.
    2. LWS Distortion Viewer – View information about the security modifications, known as distortions, in LWS Distortion Viewer. LWS applies distortions to code running in a sandbox to help prevent behavior that’s not secure. This tool can help you learn how to modify your JavaScript code to avoid distortions that affect your components.
15. Quickly Bind Data to Components in ExperienceBundle – LWR sites have components that support binding data from Salesforce CMS. ExperienceBundle now supports component-level data providers, making it easier to bind data to components in your LWR sites. Because the metadata is exposed in ExperienceBundle, you can move the component-level data providers between different orgs, such as from a sandbox to production or two different Salesforce orgs. Previously, the metadata wasn’t enabled in ExperienceBundle. 
    1. You can have only one dxp:dataProvidersin the array. The contentKey is a string that you can change to any content key in CMS that is shared with the site. The other parameters are locked.