Supported Browsers for Salesforce Classic

Customers/Administrators Point of View

1. Get More Characters for Field-Level Help Text: – Customers can view the field-level help text by hovering over the Info icon. And with the character limit expanded from 255 to 510, you can now provide more detailed help information. This increase applies to standard and custom fields on detail and edit pages.
2. Create More Roles: – In Salesforce orgs created in Spring ’21 or later, you can create up to 5,000 roles. In existing orgs, the default limit hasn’t changed. You can create up to 500 roles and can contact Salesforce Customer Support to increase this limit. Keep in mind that to improve performance, it’s best to set up roles based on data access and eliminate any roles that aren’t needed.
3.  Embed a Survey in a Web Page: – To gather feedback from your website visitors that can influence your decision-making, you can now embed a survey in a web page.
   1. In the HTML code of the web page, add the iframe tag, and embed the unauthorized survey invitation link. Add the iframe tag in this format: <iframe src=”embed_the_survey_invitation_url”></iframe>
4. Email-To-Case Update Enforcement Extended to Winter ’22 Release: – A new enforcement deadline for the Winter ’21 Email-To-Case updates gives admins until the Winter ’22 release to adopt the changes through the Release Update feature.
5. Enable Einstein Opportunity Scoring with Less Data: – Even if you have a smaller data set, you can now enable Einstein Opportunity Scoring. Einstein takes advantage of a global scoring model that uses anonymous aggregated data to allow everyone to score their opportunities. When you have enough of your own data, Einstein switches to a scoring model built only with that data.
6. Get Report Details Emailed in .XLSX Format: – Get report exports in the format you want. When exporting a report, you can select .xlsx, .xls, or .csv as the format. Previously only .xls and .csv were supported.
   1. On the Reports page, select the Export row-level action for the report. Click Details Only and then select .xlsx as the Format option.
   2. If security is a concern, you can hide the .xls option by selecting Hide the option to export a report in XLS format in Lightning Experience in Reports and Dashboards Settings.
7. Customize Your Default No-Reply Address for Email Notifications: – Before the Spring ’21 release, email notifications were automatically sent from noreply@salesforce.com. Now, you can choose which email address your org uses as the default FROM address for certain Case-related notifications, so your customers know that the email comes from your company.
   1. From Setup, enter Support Settings in the Quick Find box and turn on Send Case Notifications from System Address. Configure and verify a default No-Reply address for your org in Organization-Wide Addresses. Then, click Enable Test Run in the Release Update to send email notifications from your selected email address for Case Comment, Case Escalation, Case Assignment, and when an existing case receives emails.
8. Add Profiles to Einstein Activity Capture Configurations: – Manage your user assignments more effectively. When assigning users to a configuration, you can now add users based on their user profile. Previously, you could add only individual users, which was time-consuming.
9. Use Send Later with Threaded Emails: – Reps can now schedule emails to send at the most optimal time when replying to an email, not just when composing a new email. Previously, reps could schedule only new, unthreaded emails.
10. Salesforce for Outlook Is Being Retired Between June 2021 and 2023: – The Salesforce for Outlook side panel action menu isn’t available starting in June 2021. Salesforce for Outlook full product retirement is scheduled for June 2023. But don’t worry, you can continue integrating Microsoft Outlook with Salesforce using our next-generation products, Outlook integration, and Einstein Activity Capture. Not only do those products offer the latest features, but they’re also compatible with the latest versions of Outlook.
    1. After the side panel action menu is retired in June 2021, the new records button () isn’t available in the side panel. At that point, reps can no longer create Salesforce records from Outlook using Salesforce for Outlook.
11. Get a More Accurate View of Emails Sent from Gmail Integration with Inbox: – Sales managers now have a more accurate picture of the sales team’s performance through the emails they send from the Gmail integration. All emails sent from the Gmail integration with Inbox are now included in engagement history, even if email tracking isn’t turned on. Engagement events include replies to emails sent, out-of-office replies, and email bounces. Previously, only emails set to be tracked were included in engagement history.
12. Add Zoom Meeting Links to Events Created Using Insert Availability: – Sales reps can now connect their Zoom accounts and automatically add Zoom meeting links to invitations created using the Insert Availability feature in Lightning Experience email. Automated Zoom meeting link additions mean reps no longer add links manually after attendees select an event time. This change applies to Lightning Experience orgs with Salesforce Inbox and Enhanced Email enabled in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
13. Let External Users Schedule Appointments Across Time Zones: – Now your authenticated external users and guest users can view and select appointment time slots in the time zone they prefer. When you set the Show Time Zone Pick List attribute to True, the appointment time slot pages show a list of all-time zones supported in Salesforce. Previously, the Time Zone dropdown list was available only in outbound flows.
14. Create and Share Call Collections: – Organize your calls in categories such as effective initial calls or how to handle pricing questions. Make calls more available to access and review. Managers and reps can easily create and access groups of useful voice calls.
    1. Access call collections from the Call Coaching dashboard menu. You can also search for Record Collections in the App Launcher or surface a link to the records in the Navigation Menu.
    2. Reps can add call records that they own, and managers can add calls they have access to. To add a voice call to a collection, click Add to Collection from the voice call record. Managers and reps can also create a collection directly from the Add to Collection modal.
15. Plan Ahead with Advanced Maintenance Recurrence (Field Service): –Service managers can now create maintenance work rules to cover elaborate daily, weekly, monthly, or yearly recurring maintenance activities. Set rules that apply to a maintenance plan and control maintenance more precisely with rules on individual assets.
16. View the Number of Mailable Prospects in When Defining Email Send Settings (Pardot): –Marketers can now determine how many prospects they’re sending an email to based on the selected recipient and suppression lists. The send modal for the Pardot email shows the number of mailable prospects for the email.
    1. Click Calculate Mailable Prospects in the top right of the window. You can refresh the calculation after the initial calculation completes.
17. Sync Custom Fields in Pardot Object Sync – Beta (Pardot): – Pardot Object Sync remains in beta, but with improved infrastructure. Now your standard and custom fields are available as a single Prospect dataset, and you can choose which custom fields to bring into Tableau CRM. In this dataset, Salesforce removed and renamed some fields and made sure that the remaining fields get the latest values.
18. Sync Prospects Safely With Cross-Business Unit Leads or Contacts (Pardot): – A new setting on the Salesforce-Pardot connector stops Pardot package fields from syncing to lead and contact records in Salesforce. Use this setting as part of a custom setup to sync prospects from different Pardot business units to a single lead or contact in Salesforce. There’s no need to maintain duplicate lead or contact records. Salesforce recommends working with a partner to implement this for your org.

1. More Support for Dynamic Actions: – Dynamic actions let you add flexibility and control to actions on your record pages. Dynamic actions for custom objects are now GA for mobile and have been GA for desktop since Winter ‘21. Dynamic actions for Account, Case, Contact, Lead, and Opportunity are now GA for desktop. Dynamic actions for all other standard objects are Beta for desktop. Assign actions in the Lightning App Builder instead of the page layout, and apply filters to control when and where actions appear for users.
2. Ability to Select All Fields in SOQL Query: – Salesforce Object Query Language (SOQL) now makes it easy to include pre-defined groupings of fields within a query statement using the new FIELDS() function.
   1. Use FIELDS(ALL), FIELDS(STANDARD), or FIELDS(CUSTOM) in your SELECT statements.
   2. The SOQL FIELDS function must have a LIMIT of at most 200
3. Access Custom Metadata Type Records Using Static Methods: – Now you can use the Apex getAll(), getInstance(recordId), getInstance(qualifiedApiName), and getInstance(developerName) methods to retrieve information from custom metadata type records faster. These methods don’t rely on the SOQL engine and return the sObject details directly from the call.
   1. The following example uses the getAll() method. The custom metadata type named Games has a field called GameType. This example determines if the field value of the first record is equal to the string PC.

      List<Games__mdt> mcs = Games__mdt.getall().values();
      boolean textField = null;
      if (mcs[0].GameType__c == 'PC') {
         textField = true;
      }
      system.assertEquals(textField, true);

4. Define Localized Component Labels and Attribute Values on Lightning Pages Using Custom Labels: – With Localization Support in App Builder, when you specify a custom label in the Lightning App Builder, you can use {!$Label.customLabelName} to help define the label’s value.
5. Analyze Performance For Lightning Pages Viewed on a Phone and Desktop: – Performance Analysis in App Builder now assesses record page performance for the phone and desktop form factor. New tabs in the Page Analysis window give you separate results for a Lightning record page when it loads on a desktop and on a phone so you can design your page for optimal performance on both.
6. Salesforce Functions: Extend Salesforce with Functions (Beta): – Salesforce Functions lets developers extend Salesforce with custom, elastically scalable business logic built with high-productivity programming languages and open-source components. Salesforce Functions reduces your infrastructure responsibilities, enabling you to build and integrate Functions-as-a-Service (FaaS) apps using the languages and tools of your choice.
7. Add Salesforce CMS Content to Custom Lightning Web Components: – Now you can add Salesforce CMS content to Experience Builder sites using custom Lightning web components. After you publish content in a CMS workspace, you can enhance any custom component with your content repositories at the click of a button.
   1. Configure CMS content for a custom Lightning web component by specifying type=”ContentReference” for the component property type in the .js-meta.xml file. You can also configure your component to filter for a specific content type. For example, to display only published images from your CMS workspace, specify filter=”cms_image”, as shown:
   2. In Experience Builder, add the component to the page and click Add Content in the component’s properties. Add images, documents, news articles, and more directly to your site from your CMS workspace.
8. Use Lightning Email Templates in Salesforce Automations: – Now use Lightning email templates—including Email Template Builder email templates—in Salesforce automation, including email alerts, Flow, Workflow, Process Builder, Approval Processes, and more. For example, you can set up an email alert that sends an email to users about something that’s happened and includes a Lightning email template with the email alert. Previously, when you set up an email alert you used Salesforce Classic email templates only.
9. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Lightning Flow Is Now Salesforce Flow: – The Lightning Flow suite of features is now called Salesforce Flow, and it still includes all your processes and flows. Lightning Flow Builder and Lightning Process Builder are now called Flow Builder and Process Builder.
   2. Refer to the Prior Values of the Record That Triggered Your Flow: – Now when a record is updated, you can access that record’s prior values in Salesforce Flow. The $Record__Prior global variable contains the record’s values immediately before the flow was run. Use these prior values to check for changes and calculate differences in your flow. Refer to this article for step-by-step instructions on how to use it.
   3. Run Part of a Record-Triggered Flow After the Triggering Event: – Add a scheduled path to your record-triggered flow if you want part of the flow to run at a dynamically scheduled time after the triggering event occurs. You can base the scheduled time on when the record is created or updated or on a field value in the record. Scheduled paths run in the system context, so they have permission to access and modify all data. But the running user associated with the flow’s actions is the user who triggered the flow to run. Refer to this article for step-by-step instructions on how to use it.
   4. Send Rich Text Emails from Your Flow Using a Send Email Action: – Send an email in rich text format by using a Send an Email action. Previously, only plain text was available for Send Email actions, and you used an email alert to send a rich text email. Salesforce also added new run-time error improvements for Send Email actions to catch invalid email addresses and sender types. Refer to this article for step-by-step instructions on how to use it.
   5. Build Multicolumn Screens in Flow Builder (Beta): -You can divide each flow screen into multiple sections and columns to create a visually appealing and effective layout—without touching a single line of code. The multicolumn screen layout is responsive, so columns stack vertically to fit on mobile phones. This feature, which is now beta, includes changes since the pilot release. The Section component now supports conditional visibility. Multicolumn screens also benefit from improved styling for screen components, which is a separate, generally available feature.
   6. Control Revisited Screen Component Values in Flows: – One size doesn’t fit all when it comes to revisited screen component values, so now you can choose to refresh the values. When a user navigates to a previous screen, then proceeds forward to a screen that they visited already, the flow can refresh screen component values. Changes elsewhere in the flow are incorporated in the refreshed values. Previously, a screen component always used the same values that the user entered. The options for revisited screen component values are available only for Lightning components.
   7. Access Complex Merge Fields from Loops: – Now you can loop through a collection via merge fields on complex objects such as an Apex-defined variable or output from a custom action or screen component. Previously, you weren’t able to access merge fields on complex objects.
   8. See Accurate Flow Information in Debug Logs: – Debug logs now record the total amount of CPU time consumed by a particular flow or process in the FLOW_INTERVIEW_FINISHED_LIMIT_USAGE log lines. Also, the FLOW_INTERVIEW_LIMIT_USAGE log lines now accurately record the CPU time consumed by flows and processes that are configured to run in API version 51.0 or later.
   9. Debug Flows More Easily with Consistent Terms and Direct Debugging for Schedule-Triggered Flows: – In addition to non-triggered autolaunched flows, debugging directly on the canvas now supports schedule-triggered flows. Also, Salesforce updated the text in flow debug details and error emails to match Flow Builder’s element names: Create Records, Update Records, Get Records, and Delete Records.
10. Include Top-Level Named Array Definition for List Types in Your External Services Schemas: – You can create a top-level named array and nest named and anonymous arrays underneath it. This new support impacts response and request body definitions in your schema.
    1. For example, this top-level array definition is now supported. Previously, it was unsupported.

       {
           "swagger": "2.0",
           ...
               "schema": {
                   "$ref": "#definitions/MyObjectList"
               }
               ...
           "definitions": {
               "MyObjectList": {
                   "type": "array",
                   "items": {
                       "type": "object",
                       "properties": {...}
                   }
               }
           }
       }

11. Customize Markers and Control Map Behavior in lightning-map Base Component: – You can now make your map look and behave the way you want. Customize map locations to use your SVG image instead of the standard Google Maps markers, or define a shaded circle, rectangle, or polygon around a location. Modify or disable the zoom and dragging behavior, or disable the map controls altogether to create a static map.
    1. For example, say you want to create a simple locator map to show customers where to find your business. You can remove the zoom and Map | Satellite buttons, disable dragging, and add your own SVG to use a star for the marker.
    2. In your component, use the new options attribute to specify properties that enable or disable user interface controls. This example uses a mapOptions object in the component’s JavaScript to set the property values.
    3. In mapOptions, set the disableDefaultUI property, which disables zooming and removes the Map | Satellite buttons. To disable panning the map, set the draggable property.

       <template>
           <lightning-map
               map-markers={mapMarkers}
               options={mapOptions}
          ></lightning-map>
       </template>

    4. In mapMarkers, add the map icon property to the marker definition, and specify the SVG path property for a star. Add fillColorand and fillOpacity properties to set the color and opacity of the image fill. Add the strokeWeight property to set the line weight of the stroke drawn around the SVG image. Optionally, to determine the size of the image, set the scale property.

       import { LightningElement } from 'lwc';
       
       export default class LightningExampleMapCustomMarker extends LightningElement {
           mapOptions = {
                 'disableDefaultUI': true // when true disables Map|Satellite, +|- zoom buttons
                 'draggable': false, // when false prevents panning by dragging on the map
               };
       
           mapMarkers = [
               {   
                   location: {
                       City: 'San Francisco',
                       Country: 'USA',
                       PostalCode: '94105',
                       State: 'CA',
                       Street: '425 Mission St', 
                   },
                   mapIcon : {
                       path: 'M 125,5 155,90 245,90 175,145 200,230 125,180 50,230 75,145 5,90 95,90 z',
                       fillColor: '#CF3476',
                       fillOpacity: .5,
                       strokeWeight: 1,
                       scale: .10,
                   }
              }
           ];
       }

12. Target a Specific Release for Your Packages During Salesforce Release Transitions: – During major Salesforce release transitions, you can specify preview or previous when creating a package version. 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. Previously, you could only create package versions that matched the Salesforce release your Dev Hub org was on.
    1. To create a package version based on the previous Salesforce release version, create a scratch definition file that contains:

       {
           "release": "previous"
       }

    2. Next, specify the definition file when you create your package version.

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

13. Use BatchApexErrorEvent Triggers to Monitor ISV Applications: – Include BatchApexErrorEvent triggers in your managed package to monitor the health of batch jobs and take necessary corrective action without any post-installation steps.
    1. The BatchApexErrorEvent object represents a platform event associated with a failing batch Apex execution. To fire this platform event, a batch Apex class declaration must implement the Database.RaisesPlatformEvents interface. A BatchApexErrorEvent platform event is fired when a batch Apex job encounters an unhandled exception
14. Attach Actions to Asynchronous Apex Jobs Using Transaction Finalizers (Beta) – With Spring ’21, the Transaction Finalizers feature is in beta. A new limit establishes that a Queueable job that failed due to an unhandled exception can only be successively re-enqueued five times by a Transaction Finalizer. This limit applies to a series of consecutive Queueable job failures. The counter is reset when the Queueable job completes without an unhandled exception. Finalizers can be implemented as an inner class. Also, you can implement both Queueable and Finalizer interfaces with the same class. You can read more about it here.