Its the year end and Salesforce Spring ’22 Release Notes are here. What is a better way then spending time reading new release notes and learning new things. So today we will take a quick look and Spring 22 Release Notes.
Salesforce Spring ’22 Release Notes Points Related to Salesforce Admin
Starting February 1, 2022, we must need to use multi-factor authentication (MFA) when accessing Salesforce products. You can check how you can quickly setup MFA here.
We can enable Enhanced Personal Information Management to prevent external users, such as portal or community users from accessing other users’ personal information. This feature will replaces the Hide Personal Information setting, secures more personal identifiable information (PII) user record fields. We can also decide the PII data in custom and standard user fields.
Manage Permission Sets and Permission Set Group Assignment Expiration Dates with an Enhanced User Experience (Beta)
With the Spring 22 it’s easier to search for and filter users to assign to permission sets and permission set groups. Using the Lightning list views, we can better manage expiration dates for those permissions.
To enable this feature, From User Management Settings, enable Permission Set Group Assignments with Expiration Dates (beta). Then, from either the Permission Set Group or Permission Set page, click Manage Assignment Expiration. On the Current Assignments page, you can view permission set or permission set group users. To create a user assignment, click Add Assignment. On the Add Assignment page, you can search for and filter users.
To comply with the latest browser and security standards, enable enhanced domains on our Salesforce org’s My Domain. Now our domain is included in our all URLs, including Salesforce Sites and Experience Cloud sites. Consistent domain formats improve the user experience and standardize URLs for use in custom code and API. So now its one domain for all places.
With the enhanced report type selector, quickly access recently used report types and view the fields and objects that are included. See at a glance which report types are standard or custom, and keep the number of available report types manageable by hiding ones that we don’t need. If we need to find recently created reports, report type we can check the list view.
From Setup, in the Quick Find box, enter Reports and Dashboards, and then select Reports and Dashboards Settings. Select Enable Recommended Report Types (Lightning Experience only), and save the changes.
Now we can edit more fields in inline editing in report run page. The fields we can edit come with pencil icon and if fields are not editable it will come with lock icon.
Salesforce Spring ’22 Release Notes Points Related to Salesforce Developer
UI Test Automation Model (UTAM) is based on the popular Page Object design pattern commonly used in UI tests. When a web application, such as Salesforce, changes, the DOM of the pages and components in the app also change. Using JSON page objects makes your tests more robust and reduces test maintenance time every time an application UI changes.
Using the new Lightning Web Runtime (LWR) makes web development fast, secure, and standards-based. We can build single page Application with LWR and can get the better speed and performance.
With the latest release Salesforce is enabling the Lightning Web Security. Enablement for production orgs with only custom Lightning web components is scheduled to begin in February 2022.
We can now programmatically change a focused field to edit mode from an external element such as a button. Display a lock icon on fields that can’t be edited. Use an icon as a column header without a column label. Give a column a unique ID to enable a field name to be used in multiple columns. You can check more details here.
Salesforce Platform API versions 7.0 through 20.0 are deprecated and are no longer supported by Salesforce. They will be retired in Summer ’22. If you’re using versions 7 through 20 of the SOAP, REST, or BULK APIs, you’re using an unsupported product.
Using the new tool, Flow Trigger Explorer we can now check all of the flows that are associated with a specified object and that run when a record is created, updated, or deleted. From Setup, on the Flows page, click Flow Trigger Explorer.
In Flow Trigger Explorer, select an object and a trigger to see flows that run when a record for that object is created, updated, or deleted. See all of the before-save and after-save flows that run for the same object and trigger. Click a flow label to open the flow in Flow Builder in a new tab. Check any asynchronous paths that are associated with flows that run for the same object and trigger. Click a menu dropdown and select Flow Details and Versions to see details and activate or deactivate versions of the flow.
We can now use existing record collections to generate collection-based choices in a flow. Collection choice sets prevent the need to duplicate the results of a Get Records element, a component, or an action. So now we don’t need to query multiple times. We can create a collection once, and then use the record collection anywhere that we need it.
We can now set order on record triggered flow in before-save or after-save flows for the same object. While saving the flow we can decide the order from 1 – 2000.
As Salesforce is planning to deprecate Workflow rules. We now can migrate Workflow to flow. We can migrate workflow rules that contain these items:
- Field-based criteria
- Field updates
- Email alerts
- Outbound messages
- Time-dependent workflow actions
- Rule criteria formula that’s set to true (unless evaluation criteria is also set to created, and any time it’s edited to subsequently meet criteria)
So these points I like in Salesforce Spring ’22 Release Notes. Which points do you like most, let me know in comments. Happy Programming 🙂