Here’s my list of notable Salesforce Summer 20 features. All Summer 20 Release Features.
Edge Browser Support Updates
Lightning Experience supports the latest version of Microsoft Edge Chromium for Windows. Salesforce Classic isn’t supported. Lightning Experience and Salesforce Classic support for the non-Chromium version of Microsoft Edge ends on December 31, 2020.
Where: This change applies to Lightning Experience in all editions.
How: To see which version of Edge you’re using, check its
icon. The Microsoft Edge Chromium browser uses the icon, while non-Chromium Edge uses the icon.Summer Release Notes
Salesforce is supporting Microsoft’s new Edge Chromium browser in Lightning but not classic and it’s ending support for the original Edge browser in December of 2020.
Work Through Lists with Ease Using Split View for Standard Navigation
Do you often find yourself working through multiple records in a list? With split view, you can see a list view and a record side by side. To move on to a new record, select it from the split view, and the new record opens with the list still in view. No more navigating back and forth between your list and your records. Split view is great for going through records in sequence or for quickly skimming through a set of records. The split view panel is collapsible for extra flexibility.
Where: This change applies to Lightning Experience in Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.Summer Release Notes
This is a console-like way to see a listview’s records in the left pane and see the selected record’s details on the right.
Show Extended Record and Polymorphic Relationships with the Related Record Component
Now your agents can look up more information with fewer clicks. Agents can use the updated Related Record component to look up two levels of record relationships to get more context for their customers.
Where: This change applies to Lightning Experience in the Group Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Who: To create and save Lightning pages in the Lightning App Builder, users need the “Customize Application” permission. To view Lightning pages in the Lightning App Builder, users need the “View Setup and Configuration” permission.
Why: Now agents can look up a field value on the related record that’s associated with another record. For example, an agent can look up the account for a contact that’s related to a case. Previously, the agent could look up only one level of a record relationship. So, they could look up the contact that’s related to the case, but not the account that’s associated with the contact that’s on that case. Now, agents can also look up polymorphic fields on the Related Record Component. For example, the Tasks Related To field can take a value of a Case, Account, or Opportunity, and so on. Then the agent can select the lookup field type “Case” and from there display the case. Previously, polymorphic fields weren’t supported in the Related Record Component.
How: On the Lightning App Builder, select your record page and add the Related Record component to the page. Specify the first record lookup, and then specify the second-level lookup. You must specify a first-level lookup before you can add a second-level lookup. The second-level lookup must be a field that’s accessible from the first record lookup. 193 Salesforce Summer ’20 Release Notes Other Changes in Service Cloud To let users look up polymorphic fields, select a polymorphic lookup field type on the first-level lookup or on the second-level lookup.Summer Release Notes
Even though this is buried in the Service Cloud notes, I suspect that the “Related Record” lightning component is supported in the lightning experience in general and is usable in Salescloud too. This enhancement now allows one to see grandparent fields and polymorphic related info too which is very powerful.
Attach .csv Files to Report Subscriptions (Beta)
When people subscribe to a report, a new option lets them choose to receive results as a .csv file attached to the subscription email. The email itself includes the report name in the subject line, but there is no email body. Row-level record details are included in the attached .csv file instead. And small changes to the Edit Subscription menu design include a new Attach File button and a refined layout.Summer Release Notes
The report details can now be attached as a CSV to a scheduled report! One no longer has to open the report link. Note that this is a Beta feature though!
Trigger a Flow That Performs Actions After a Record Is Saved
Creating or updating a record can now trigger a flow that performs actions such as sending an email after the changes are saved to the database. Use record-changed flows to perform after-save actions and make before-save updates. You can replace most of your workflows and record-change processes that you created in Process Builder.
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Who: To activate a flow that performs after-save actions, you need the View All Data permission.
Why: Perhaps you’re familiar with Process Builder and using a record-change process to send an email. Such a process can send an email automatically for each new account. After-save actions in flows accomplish that same goal, and you don’t have to use a different tool.
Or perhaps you’re familiar with Apex triggers. A flow that performs after-save actions is similar to an after trigger and can:
• Access field values that are set only after the record is saved, such as the Last Modified Date field or the ID of the new record.
• Create or update related records.
With Flow Builder, you can also do more such as get records and loops.Summer 20 Release Notes
Now one can do a lot more automation when a record is created or updated from a flow alone instead of having to use a process builder and flow combination. This is more of a convenience than a totally new capability. This also reinforces Salesforce’s stance of moving away from process builders.
Debug More Flows Faster
When you debug an autolaunched flow that saves changes to the database such as create records, you don’t have to revert those changes manually anymore. In Flow Builder, use rollback mode and let it save you the hassle. You can now use the debug option in Flow Builder for schedule-triggered flows. And the debug option includes the Lookup screen component so that you can set record variables more easily.Summer 20 Release Notes
This allows database changes to be rolled back automatically if desired when debugging a flow. This will save a ton of time!
Let Flow Users Search for Records by Any Searchable Field
Now flow users can now search by any searchable field and choose from more than five records. Previously, the flow lookup component only supported instant search results. Users could search only by the name field, and the results were capped at five records.
Where: This change applies to Lightning Experience and Salesforce Classic and all versions of the mobile app in Enterprise, Performance, Unlimited, and Developer editions. Lookup screen components are supported only in the Lightning flow runtime.
Why: Now that full lookup search is enabled, there are fewer barriers between flow users and the specific record they’re looking for. Instant search results are still limited to five, like in the lookup field on a record.
Let’s say you want to search for a contact by their email address instead of their name. Click Show All Results for “…”, and the full lookup modal opens.Summer 20 Release Notes
This will greatly allow users to more easily find records in flows.
Analyze Screen Flow Usage
We set up a new Sample Flow Report: Screen Flows custom report type and report for you. See who’s running the screen flows you build. Discover flow interview execution counts and screen duration times. Review the status of a flow interview. No configuration on your part is needed.Summer 20 Release Notes
One can see all the flows that ran within the last 31 days. This usage information will drive future enhancement decisions. For example, seldom used flows probably don’t need to be the most user friendly but ones executed frequently do.
Create Flow Screen Components That Work for Multiple Objects (Beta)
Now developers can create reusable screen components that use the generic sObject and sObject data types. They can build one component that works for multiple objects, rather than one component for each individual object. For example, they can build a data table component that works with any collection of records, from accounts and contacts to custom objects.
Where: This change applies to Lightning Web Components in Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions.Summer 20 Release Notes
This is very awesome. Developers can now create generic, multiple object components. It appears that it only is supported in LWCs though and is currently in Beta too. When this becomes GA, I’ll definitely check it out further.
Dynamic Forms (Non-GA Preview)
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.
Why: The 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 benefits 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.Summer 20 Release Notes
This essentially allows one to create lightning record pages that are loosely tied to page layouts and are much more flexible. I’m a bit skeptical on the page performance claims though.