Supported Browsers for Salesforce Classic

Customers/Administrators Point of View

Additional enhancements worth noting!

1. Manage Deleted Fields in Lightning Experience: – You can now manage deleted fields in Lightning Experience. In previous releases, you could only manage a deleted field and its data by switching to Salesforce Classic.
2. Choose Your Utility Bar Alignment: – Customize where your Salesforce org’s utility bar appears on the screen. You can choose to align the utility bar to the bottom right or the bottom left of the screen. The default alignment matches the directionality of the user’s language.
3.  Manually Log Emails from the Gmail Integration When Einstein Activity Capture Is On: – If your Einstein Activity Capture configuration has emails disabled, reps can now log emails manually from the Gmail integration. Previously, if emails were disabled in the configuration, users weren’t shown an option to log emails.
4. Custom Metadata Types Support Geolocation Field Types Relationships: – Support for entity particle relationships was introduced in Summer ’20, with the exception of geolocation field types. With Winter ’21, you can now create geolocation field type relationships.
5. Serve CMS Content with a Content Delivery Network (CDN).: – Deliver Salesforce CMS content to your users with higher performance than ever through a CDN. A CDN is a distributed group of servers that work together to deliver your content quickly and efficiently. Readily connect content to your sites through Community Cloud or to custom applications through public channels. And conveniently share your email marketing content and templates from Salesforce CMS with Marketing Email in Lightning.
   
   
   Serve your content from a CDN such as Akamai, or use one of your own. To create a public channel, open the CMS Channels page in the Salesforce CMS app, click Create Channel, and select Public Channel.
   
   
6. Organize Salesforce CMS Content with Folders: – Now it’s easier to organize content in your Salesforce CMS workspace, and share links to folders with others in your org. In your workspace (1) create folders with a hierarchy of up to five levels (2) with the click of a button (3). Edit and rename folders to fine-tune your CMS, and delete empty folders you no longer need. Add content directly to folders and move content within folders (4). Each folder has a unique folder ID that appears in the URL (5). This means you can bookmark the URL to find a folder quickly and share the link to specific folders with other members of the workspace.
7. Personalize Survey Questions Within Email: – Now you can give your participants a VIP experience by personalizing survey questions that are embedded within an email invitation.
8. Review Aggregate Email Metrics in Lightning Experience: – As part of Marketing Email in Lightning, rollup metrics now appear on email content and email template records. Marketers get an aggregate view of how certain content and templates perform based on statistics from everywhere they’re used. Individual list email send and campaign-level email marketing reports are still available, too.
9. Customize More Pardot Assets with Any Tracker Domain (Pardot): – You can now use any of your tracker domains to customize the links for Pardot form handlers, dynamic content, social posts, and multivariate landing page tests. Previously, these asset links defaulted to the primary tracker domain. Emails without templates are now the only Pardot assets that don’t include this functionality.
10. Send Your Custom Notification Recipients to New Places with Page Reference Navigation: – Use the new Target Page Reference field on the Send Custom Notification action to specify navigation targets for your custom notifications sent via flow or REST API. Previously, only the Target ID field was available for custom notification navigation and only a record ID could be specified as a navigation target. Now your custom push and in-app notifications can navigate to any page that’s accessible via the PageReference class, such as a Lightning app or an external URL.
11. Choose When to Show the Submit for Approval Action (Generally Available and Beta): – Ever wanted to display the Submit for Approval action only when a record is eligible for approval? That day has come! With dynamic actions, now you can set conditions for when each action is visible, including the Submit for Approval action.
12. Create a Relationship Map in Quip with Live Salesforce Data: – Build relationship maps in your Account Plans with imported Salesforce record data. To add data to your maps that exist outside of Salesforce, create custom Quip cards.
13. Preview and Test an Email in Lightning Experience (Pardot): – Users can preview and test emails from the email content record. Before sending an email to a large recipient list, do a trial run by sending it to a test list or individual email addresses. Preview and troubleshoot possible personalization issues by previewing as specific recipients.
14. Analyze Your Lightning Page Performance: – Discover ways to make your record page perform better based on analysis right inside the Lightning App Builder. Performance Analysis in App Builder evaluates the fields, instances of the Related Lists component, and metadata of a record page. With the click of a button, get best practices and suggestions for improving page performance and the end-user experience.
    

1. Use the Safe Navigation Operator to Avoid Null Pointer Exceptions: – Use the safe navigation operator (?.) to replace explicit, sequential checks for null references. This new operator short-circuits expressions that attempt to operate on a null value and returns null instead of throwing a NullPointerException.
   
   1. This example first evaluates a, and returns null if a is null. Otherwise, the return value is a.b.

      a?.b // Evaluates to: a == null? Null : a.b

   2. This example returns null if a[x] evaluates to null. If a[x] does not evaluate to null and aMethod() returns null, then this expression throws a null pointer exception.

      a[x]?.aMethod().aField // Evaluates to null if a[x] == null

   3. This example returns null if a[x].aMethod() evaluates to null.

      a[x].aMethod()?.aField 

   4. This example indicates that the type of the expression is the same, whether the safe navigation operator is used in the expression or not.

      Integer x = anObject?.anIntegerField; // The expression is of type Integer because the field is of type Integer

   5. This example shows a single statement replacing a block of code that checks for nulls.

      // Previous code checking for nulls
      String profileUrl = null;
      if (user.getProfileUrl() != null) {
      	profileUrl = user.getProfileUrl().toExternalForm();
      	}

      // New code using the safe navigation operator
      String profileUrl = user.getProfileUrl()?.toExternalForm();

   6. This example shows a single-row SOQL query using the safe navigation operator.

      // Previous code checking for nulls
      results = [SELECT Name FROM Account WHERE Id = :accId];
      if (results.size() == 0) { // Account was deleted
          return null;
      }
      return results[0].Name;

      // New code using the safe navigation operator
      return [SELECT Name FROM Account WHERE Id = :accId]?.Name;

2. Send Custom Notifications from Apex: – Use the Messaging.CustomNotification class to create, configure, and send custom notifications directly from Apex code, such as a trigger. 
3. Break Up Your Record Details with Dynamic Forms (Generally Available): –

   Dynamic Forms is the next step in the evolution of Lightning record pages. It adds the ability to configure record detail fields and sections inside the Lightning App Builder.
   
   With more fields on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customize. With Dynamic Forms, you can migrate the fields and sections from your page layout as individual components into the Lightning App Builder. Then, you can configure them just like the rest of the components on the page, and give users only the fields and sections that they need.
   

   Dynamic Forms benefit you in these ways.

   • An instant upgrade from page layouts: Place fields and sections wherever you want.
   • Better page performance: Put fields and sections into accordion components or tabs to significantly improve page load times.
   • Dynamic layouts: Use visibility rules to show and hide fields and sections.
   • Simpler layout management:
     • Manage the fields and sections on your pages in the Lightning App Builder without touching the page layout editor.
     • Reduce the number of page layouts you need with component visibility rules.
     • Take advantage of a single assignment model for the Lightning page instead of the dual model of assigning a Lightning page and a page layout.

   To enable Dynamic Forms in your org, navigate to Setup (Gear Icon) | Setup | User Interface | Record Page Settings and then click on the Dynamic Forms section, flip the switch to On.

   

   After you enable Dynamic Forms, new features appear in the Lightning App Builder. A new Fields tab in the component palette contains Field and Field Section components, which are the building blocks for Dynamic Forms.

   

   To get started? Open an existing record page in the Lightning App Builder, then click Upgrade Now from the Record Detail properties pane to launch the Dynamic Forms migration wizard. With only a few clicks, the wizard adds fields and field sections to the page for you.

4. Make Apex Callouts After Publishing Platform Event Messages: – You can now make Apex callouts after publishing event messages for events configured with the Publish Immediately behavior. Previously, after publishing such events, you couldn’t make callouts from any Apex code. Events published immediately have a new limit, which is separate from the Apex DML statement limit. Read more about it here.
5. Deploy Organization-Wide Defaults and Criteria-Based Sharing Rules Together: – You can now simultaneously update the sharingModel field for an object and create new criteria-based or guest user sharing rules via the Metadata API. Previously, you deployed these changes in separate packages. You still deploy owner-based sharing rules separately from organization-wide default changes.
6. Lightning Flow Enhancements: – There are several enhancements in Lightning Flow as follows:
   1. Trigger a Flow to Run Before a Record is Deleted: – In Flow Builder, you can now configure a new record–triggered flow to run before a record is deleted. You no longer need to write Apex code to set this up. This autolaunched flow runs in the background and updates related records when a record is deleted.
   2. Improve the Performance and Precision of Record-Triggered Flows with Entry Criteria: – Salesforce has added entry criteria to record-triggered flows, giving you more control over your automation. Instead of configuring the flow to run every time a record is created or edited, you can now configure it to run only when condition requirements are met. This optimization can also significantly reduce your record-triggered flows’ impact on your org’s performance, depending on the flow.
   3. Debug Flow Errors in Sandbox Org as Another User: – Debugging a flow in a sandbox org is now easier than ever with the ability to debug a flow as another user. When you debug a flow as another user, you can catch flow exceptions such as unexpected permission, sharing, and profile configurations before they occur in production orgs.
   4. Create Decision Outcomes that Only Execute When Certain Changes are Made: – Now a flow triggered by a record update can take different paths if the record that triggered the flow was edited to meet certain criteria. When you configure a Decision outcome, you can now set that outcome to execute only when the triggering record is updated to meet the condition requirements. This feature allows you to filter out record updates that are unrelated to your flow’s use case, and to avoid reprocessing records that previously triggered the flow.
   5. Easily Access Related Record Data in Autolaunched Flows with Triggers: –
      Now in autolaunched flows with triggers, you no longer need to create Get Records elements to find associated records and retrieve data from them. Instead, when you configure flow elements and resources, you can easily drill down to the field values of a global or record variable’s associated records. For example, in a Decision element, drill down from $Record to Account ID to Customer Priority.
   6. Use AND, OR, and Custom Operators Across All Flow Builder Elements: –
      Salesforce has added the condition-defining options across Flow Builder. Specify that you want the condition logic to meet ANY conditions or that you want it to meet ALL conditions. For example, specify contacts with the name Joe OR the city of Mumbai. Or you can provide your own custom logic. Salesforce has added these options to the Get Records, Update Records, and Delete Records elements, and to screen elements. You can also find the options in the Start element when configuring schedule- and record-triggered flows, and in record choice sets.
7. Detect Apex Runtime Context with RequestId and Quiddity: – You can now detect Apex context at runtime and correlate multiple logs triggered by the request, using Request ID and Quiddity values. Use the methods in the System.Request class to obtain the Request ID and Quiddity of the current Salesforce request.
   
   

   The following example shows how to retrieve and use Request ID and Quiddity.

   //Get info about the current request
   Request reqInfo = Request.getCurrent();
   
   //Universally unique identifier for this request
   //Same as requestId in splunk or REQUEST_ID in event monitoring
   String currentRequestId = reqInfo.getRequestId();
   
   
   //enum representing how Apex is running. e.g. BULK_API vs LIGHTNING
   //Use this with a switch statement,
   //instead of checking System.isFuture() || System.isQueueable() || ...
   Quiddity currentType = reqInfo.getQuiddity();

8. Create Scratch Orgs More Easily Using an Org’s Shape (Beta): – It is not easy to build a scratch org definition that mirrors the features and settings in your production org. With Org Shape for Scratch Orgs, you can leave building the scratch org definition to us. After you capture the org’s shape, you can spin up scratch orgs based on it with minor assembly required.

   Enable Org Shape for Scratch Orgs in the org whose shape you want to capture (source org). Perform the steps below to configure it: 

   1. As an admin, log in to the source org.
   2. From Setup, enter Org Shape in the Quick Find box, then select Org Shape.
   3. Click Enable Org Shape for Scratch Orgs (Beta).
   4. If your source org is different from your Dev Hub org, enter the Dev Hub org ID to the list of allowed Dev Hub orgs.
   5. Create a scratch org definition file that contains the 15-character source org ID, the only required option.

      {
        "orgName": "Salesforce",
        "sourceOrg": "00DB1230400Ifx5"
      }

   6. Create a scratch org.

9. Add Custom Buttons to the lightning-input-rich-text Base Component (Beta): – You can now add buttons to perform actions that you define, such as inserting an email template, applying formats, or adding a link to your FAQ. You can even open a popup from a custom button. Define a custom button using two new components together, nested in the lightning-input-rich-text component. Read more about it here.

10. Improve Apex Testing with New SObject Error Methods: – Track errors with the new SObject.hasErrors() and SObject.getErrors() methods without performing a DML operation to check the result for errors. Dynamically add errors to specific fields with new SObject.addError() overload methods. Use the hasErrors() method to know if an SObject instance contains errors. Use the getErrors() method to retrieve the list of errors for a specific SObject instance.

    The following example code shows usage of the new SObject error methods.

    //Baseline code sample for using addError, getErrors, together
       Account a = new Account();
       String msg = 'New error method in SObject';
       //The new overload that accepts the field dynamically at runtime
       a.addError('Name', msg); 
       List<Database.Error> errors = a.getErrors();
       System.assertEquals(1, errors.size());
       Database.Error error = errors.get(0);
       System.assertEquals(msg, error.getMessage());
       System.assertEquals(StatusCode.FIELD_CUSTOM_VALIDATION_EXCEPTION, error.getStatusCode());
       String[] fields = error.getFields();
       System.assertNotEquals(null, fields);
       System.assertEquals(1, fields.size());

11. Second-Generation Packages Support Lightning Message Channels: – Lightning components use message channels to communicate via the Lightning Message Service. You can now include message channels in second-generation packages.