Salesforce is back with its Summer ‘22 release notes. Salesforce releases updates on a regular basis to enhance the productivity, consistency, reliability, and availability of their products. The Release Revamps page lists the upgrades that your organization may need to implement. Many release changes have an effect on the current configurations. When a release update is developed, it is planned to be implemented in a future release.
Usually, release notes include a Test Run option that allows you to activate an update and analyze any changes to your org, including modifications to customizations, before the Comprehensive Steps By date of the version.
Let’s have a look at the features that are coerced with this release.
Salesforce CPQ now operates quicker incompatible web browsers thanks to the use of Web Components V1 technology. This upgrade will be implemented in Summer '22.
Where: This modification affects Lightning Experience, Salesforce Classic, and the Salesforce mobile app in Salesforce CPQ.
When: This modification, which was initially made accessible in Summer '21, is now standard and cannot be turned off. Go to Trust Status, look for your instance, and then select the maintenance tab to retrieve the major release upgrade date.
How: Salesforce CPQ runs quicker using Web Components V1 technology, but the appearance and feel of your modifications may alter. We recommend that you focus on these features while testing your customizations on desktop and in the Salesforce mobile app.
Quote line editor, Product selection, Salesforce CPQ favorites, Product bundle configuration, Quote calculator plugin, Page security plugin
Some variations in the user interface are to be expected when the update is implemented, depending on your settings and the browser.
Don't forget to check out: Why are Salesforce Releases Named After Seasons?
To utilize, update flow screens. Section components will be used to prepare for the replacement of two-column layouts with multi-column displays. Lightning Web Components is used to rebuild the Dependent Picklists component. Create a flow screen using custom screen components that react to user input on the same screen (pilot). Versioned updates are provided for flows and processes running on API version 55.0.
The Component Dependent Picklists Are Rebuilt Using Lightning Web Components (LWC)
Salesforce now finds it easier to support the Dependent Picklists component in all areas that perform screen flows. With a few exceptions, the component looks and behaves the same as it did in previous iterations.
Where: This update affects Lightning Experience, Salesforce Classic, and all mobile app versions in the Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
How: Examine these modifications and, if required, update the impacted Dependent Picklists elements in your flow screens.
When a user fails to fill out a needed field in a Dependent Picklists component, two possibly identical error messages emerge. Two systems validate Dependent Picklists components, and each system can deliver an error message. Previously, when both systems detected the same issue for a necessary field, the user saw just one error message.
Gauge the CPU Time Consumption of Flows and Processes Accurately
Salesforce can now precisely monitor, log, and restrict the CPU time required by flows and processes thanks to this upgrade. Because CPU time is now precisely tracked, flows and processes fail after executing the element, criterion node, or action that causes a transaction to exceed the CPU limit. All complicated flows and processes that are more likely to surpass this limit should be tested.
Where: This modification is applicable to Lightning Experience and Salesforce Classic versions in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer.
When: Salesforce will implement this change in the summer of '22.
Why: Salesforce correctly measures, tracks, and restricts the CPU time required by flows and processes running in API version 51.0 or later. When this update is enabled, the behavior is applied to all flows and processes, independent of their run-time API versions.
How: To install this update, go to Setup, type Release Updates in the Quick Find box, and then pick Release Updates. Follow the testing and activation steps to obtain the Accurately Measure the CPU Time Consumption of Flows and Processes release update.
Flows and processes crash if they cause a transaction to run over the CPU time limit, and sophisticated flows and processes are more likely to do so. Reduce the number of components, formulae, and cross-object references in a flow or process to reduce CPU time utilization. You may examine the debug logs to see how much CPU time each element, criterion node, and action consumes.
Update Email Addresses and Reset Passwords in a Secure Manner
Where: This modification is applicable to all versions of Lightning Experience and Salesforce Classic.
Why: When an org user's email address is changed and the Generate new password and inform user setting is enabled, the user receives a password reset link at their new email address. The user must generate a new password before the new email address becomes active.
The new method guarantees that each user's email address is correctly confirmed before it is updated, while also delivering a simple user experience that does not need two different processes.
How: Your organization's administrators may now safely update a user's email address and reset their password in the same action.
Check out another amazing blog by Apphienz here: Defining Salesforce Marketing Cloud Engagement and Why It's Crucial For Businesses
Solve MFA Challenges for Auth Provider Logins in Single Sign-On
Where: This modification affects Lightning Experience, Salesforce Classic, and the Salesforce mobile app in the Personal, Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Why: When a user registers into Salesforce using an SSO Authentication Provider, the anticipated and documented action is to skip MFA enforcement in Salesforce, because MFA is normally applied during the SSO provider's login process.
Users who have the Multi-factor Authentication for User Interface Logins user permission and log in using an SSO Auth Provider are no longer requested to complete an MFA challenge in Salesforce.
How: Users who access Salesforce using an SSO Auth Provider are no longer requested to complete an MFA challenge.
Configure the assigned user profile to demand a High Assurance session security level upon login, and ensure that Multi-Factor Authentication is in the High Assurance Column, to enforce MFA in Salesforce for users who log in using an SSO Auth Provider.
These are some of the features that Salesforce released. If you are looking to implement them in your current system or upgrade t for better productivity, gett in touch with us at Apphienz.
Read our previous Salesforce release notes blogs here. Visit our website for more information or write to us in case of any further queries.