So summer is here and with that we have Salesforce Summer ’21 Release Notes is available. With every release Salesforce introduce many new features and this release is no different. So today we will check some of the new exciting features.
Salesforce Summer ’21 Release Notes Points Related to Salesforce Admin
Future Requirement to Enable Multi-Factor Authentication (MFA)
Beginning February 1, 2022 Salesforce is making MFA effective. We need to enable MFA for direct and SSO logins. You can check how to setup MFA here.
Build Multicolumn Screens in Flow Builder (Generally Available)
Multicolumn Screen in Flow builder is now Generally Available. The Section component is now supported in flows that get launched from Einstein Next Best Action and Actions & Recommendations components. Labels for components in sections are now supported in Translation Workbench. You can check more details about them here.
Use Is Changed in Condition Logic for Start Elements and Decision Elements
We can now use Is Changed for Start elements and Decision elements in record-triggered flows. For Start elements, if you select the Is Changed operator in a condition, you can’t change when to run the flow for updated records.
Use ISCHANGED, ISNEW, and PRIORVALUE in Record-Triggered Flow Formulas
We can now use ISCHANGED, ISNEW, and PRIORVALUE formula functions in record triggered flow. This will help us in identify when record is created vs updated. We need to use the $Record global variable instead of the object. For example, to use ISCHANGED(account.x) in a record-triggered flow formula, change it to ISCHANGED($Record.x).
Place Fields from Your Salesforce Objects Directly on Flow Screens (Beta)
We can now directly add record in flow screen. When we add a record field to a flow screen, the field’s name, data type, help text, requiredness, and existing values are automatically configured. Record fields don’t save data automatically. Use a Create Records or Update Records element to save the record variable. They only support certain data types for now.
Preview More Flow Screen Components
Now we can preview many components in canvas when building the flow screen. These components are supported: Address, Call Script, Dependent Picklist, Email, Display Image, File Upload, Lookup, Name, Phone, Slider, Toggle, and URL. And we can preview most checkout flow components.
Salesforce Flow Accessibility Enhancements
Focus management has been improved in the flow screen experience. If there’s an error on the current flow screen, the focus is set to the first field with an error. If there aren’t any errors on the current flow screen, using Previous or Next displays the appropriate screen and the focus is set to its first focusable field
Find Failed Flows Faster
Using the new Failed Flow Interviews list view we can easily find failed flow interviews. We can also created our own custom list view to combine failed and paused flow. From Setup, enter flow in Quick Find box, and then select Paused and Failed Flow Interviews. The default list view is Paused Flow Interviews.
Read Flow Error Emails More Easily
Now flow error email subject will include flow label instead of flow API name. In the body also email text is improved.
You can also check this post to get more details related to Flow.
Salesforce Summer ’21 Release Notes Points Related to Salesforce Developers
Create Quick Actions with Lightning Web Components
We can now use Lightning Web Components in quick action. They are currently supported only on record pages. 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.
<?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>To use a headless action, add an exposed invoke() method to our component.
import { LightningElement, api } from "lwc";
declare default class HeadlessSimple extends LightningElement {
@api invoke() {
console.log("Hi, I'm an action.");
}
}Create Styling Hooks for Lightning Web Components
We can create custom style hooks for LWC. 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()
/* consumerComponent.css */
:host {
--light-theme-backgroud-color: honeydew;
--light-theme-text-color: darkgreen;
--dark-theme-background-color: maroon;
--dark-theme-text-color: ivory;
}Monitor Lightning Component Changes in the Setup Audit Trail
We can now track Lightning component changes in Setup Audit Trail. We can track when a component is created, edited and deleted.
Attach Actions to Asynchronous Apex Jobs Using Transaction Finalizers (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: It 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 Queueable jobs, we must implement the Finalizer interface. Only one finalizer instance can be attached to any Queueable job. We 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.
Secure Apex Code with User Mode Database Operations (Pilot)
We can now declare when Apex will run in System Mode vs User Mode. The new Database methods support an AccessLevel parameter that enables us to run database operations in user mode, instead of in the default system mode. By default Apex run in system mode and doesn’t respect running user’s permissions.
Default Font Is System UI Font
SLDS design tokens now use the native sans-serif font that the operating system’s UI provides by default. The Previous font Salesforce Sans is no longer used.
Salesforce Mobile App Requirements Have Changed
Salesforce has released a list of devices for Salesforce mobile app. Customers can still use the app on untested devices but in case of an issue Salesforce might not able to provide support. (List available as of 19 April 2021).
So these are some of the points which I found in Salesforce Summer ’21 release notes. Which points you like most in this Summer ’21 release. you can signup for Summer 21 org here. Let me know in comments. Happy Programming 🙂
2 thoughts on “Salesforce Summer ’21 Release Notes: Quick Overview”