My top 5 developer’s features upcoming within the Salesforce Summer’ 21 release
After reading the new release note of the Summer’21, I wanted to share with you my top 5 developer’s features. Here is my personal opinion on the coolest features this release will bring us 😉
1. Create Quick Actions with Lightning Web Components
We wanted it, we got it. We can now add Lightning Web Component into a Quick Action ! It’s quite simple to set it up and Salesforce gave us the opportunity to call the component in two differents ways :
- Execute an action when the user clicked on the Quick Action
- Open a window when the user clicked on the Quick Action
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.
Here’s the configuration for a headless action.
To use a headless action, add an exposed invoke() method to your component.
Note by Salesforce : LWC Quick Actions are currently supported only on record pages.
2. Create Styling Hooks for Lightning Web Components
For a personnal LWC project that I started, I used Styling Hooks, and it works out very well !
I wanted to create a simple “Dark Mode” in my app, and I used Styling Hooks to be able to do it !
See below Salesforce exemples :
How: 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()
CSS custom properties are inherited. Inherited properties pierce the shadow DOM. Some CSS properties, like color, are also inherited. Because CSS custom properties are inherited, a consumer can set their values at a higher level in the DOM tree and style your component.
More here : https://releasenotes.docs.salesforce.com/en-us/summer21/release-notes/rn_lwc_css_custom_properties.htm
3. Improve Page Performance with Custom Lightning Component Analysis
Because we use Custom Components (Lightning Components or Lightning Web Components) more and more in our pages, Salesforce gave us a new feature to follow the performance of our pages.
The end of the debug nightmare when a page takes forever to load !
1 — Page Load Time
2 — Components performance
3 — Recommendations for optimizing custom components also appear when relevant
4. Create Package Versions Based on the Upcoming Release
For Packages lovers :
During major Salesforce release transitions, you can now specify preview or previous when creating a package version.
In Spring ’21, Salesforce added the ability to specify the previous release. 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.
To create a package version based on the upcoming Salesforce release version, create a scratch org definition file that contains:
In the sfdx-project.json file, set the sourceApiVersion to correspond with the release version of the package version you’re creating.
Then when you create your package version, specify the scratch org definition file.
sfdx force:package:version:create — package pkgA — definitionfile config/project-scratch-def.json
5. Monitor Lightning Component Changes in the Setup Audit Trail
Use the audit trail to track when your users create, change, or delete a custom Lightning component.
Audit history is especially useful when multiple developers work on components.
To view the audit history, from Setup, in the Quick Find box :
- enter View Setup Audit Trail
- then select View Setup Audit Trail.
Sources :
Salesforce Summer’ 21 release note : https://help.salesforce.com/articleView?id=release-notes.salesforce_release_notes.htm&type=5
