It’s that time of year again. Seemed like just yesterday that I reviewed the Spring ’22 features. Time flies! Check out the newest features for you and your end users, hitting your sandboxes and Production orgs soon.
As always, I encourage you to read the release notes for features that are important to you, as an admin, and your company.
Once you’ve read the summaries below, check these new features out in your Summer ’22 sandbox prior to the release upgrade in your Production org. You can also get hands-on in a Summer ’22 pre-release org here. Check the Maintenance Calendar for exactly when your Salesforce org will get the Summer ’22 features. Scroll through the list and check your Salesforce instance (NA__, EMEA__) against the release dates listed in the calendar.
All enhancements below apply to Lightning Experience unless specified otherwise.
Releases include Pilot, Beta, and Generally Available (GA) features:
Below are a few Summer ’22 features I thought your users would find helpful!
The due date for an overdue task will appear in red in a task list view, on the task record, task Kanban view, task split view and activity timeline. That way, your users can very quickly identify and work on those overdue tasks first!
Einstein Activity Capture tries to identify emails containing sensitive information and automated emails before they are added to the activity timeline. It sets these emails to Don’t Share. Your users can leave it as is, off the activity timeline, or share the email, if they wish. The choice is theirs to make.
Using the availability calendar view, you can easily scan availability across calendars and create an event by clicking into a calendar. The event will appear with the selected date, time, and assigned user prefilled for you! What a productivity gain!
Now a fully supported feature, you can make inline edits to multiple rows and columns and save them in a single click! Note: Any field that shows a lock icon means that the field cannot be inline edited.
With the enhanced report type selector, you can access recently used report types, whether standard or custom, along with the fields and objects included in the report type. This can save you time when creating reports by surfacing up report types for you.
The section called “Created by you” shows at maximum three recently used reports created by the user using the selected report type and the section “Created by Others” shows at maximum three recently used reports created by other users in the org using the selected report type.
For admins with the manage report types permission, you also have the ability to hide any report types which are no longer in use.
When you create a new report, you can now filter existing report types by object. Click Filter which will then allow you to select one or more standard or custom objects. Once the filter is applied, it will show you a list of report types filtered by those objects. These selected objects can be searched through using the search bar within the filter modal. Note: This feature is in Closed Beta. If you’re interested in using this feature, please contact Salesforce Support.
The Analytics Home page is a new and improved Analytics Home experience for users who have reports and dashboards. And, if you also have access to CRM Analytics, then all your analytics content will be available here as well. The ‘For You’ section provides a personalized and intelligent experience for each user. When you browse, you can set primary and secondary filters to refine your search. To enable this feature, go to Reports and Dashboards User Interface Settings page, check the Enable Unified Home setting, and save. Then, access Analytics from the App Launcher.
Users can manually share a campaign with another user in Lightning. Previously, this feature was only available in Classic. To share a campaign, the campaign owner can select Sharing from the campaign action menu to share with a new user or group. Access Sharing Hierarchy to view all users who have access to a given campaign.
This release has a lot of features to help boost your productivity level when creating automagic. There are also upcoming changes you should be aware of, so you can start preparing your org before those changes are enforced in a future release. I highlighted a few of them here so you won’t be caught off-guard.
The requirement to use multi-factor authentication (MFA) when accessing Salesforce products went into effect on February 1, 2022. All users are required to use MFA when logging in to Salesforce with Salesforce username/password credentials or SSO. Note: Salesforce plans to automatically enable and enforce MFA in the future on a cloud by cloud basis, so we strongly recommend you enable MFA for your company if you haven’t already. To learn more about how to implement MFA for your organization, type “MFA” into the Quick Find Setup and select Multi-Factor Authentication Assistant, or visit security.salesforce.com/mfa.
Picklists are finally getting some much deserved love in this release. Check ‘em out!
Get rid of that tech debt! Get an email notification when custom picklist fields have more than 4,000 inactive values, so you can spring clean your org and bulk delete those inactive values. To enable this, search for Settings, and select Picklist Settings. Then, click the Email Me button to receive an email of custom picklist fields with inactive values.
Remove inactive picklist values from custom picklists to improve org performance and health. You can now bulk delete inactive picklist values at once. First, search for Picklist Settings, and then toggle on the option Bulk Delete Inactive Picklist Values (Beta). 
With this Beta feature, you can now activate, deactivate, delete, or replace multiple custom picklist values at once. No more doing this one by one—no one has time for that! To enable this feature, please contact your account executive (AE).
A descriptive message is shown when you save picklist values which will indicate which picklist value is a duplicate, not just that there are duplicate values. No more guessing which one is the duplicate.
You can now create custom address fields like the standard address fields. Custom address fields use the State and Country picklist values.Note: By default, all countries, territories, and their states and provinces are visible to users. If State and Country/Territory Picklists are enabled, those picklist values are used in standard address fields. With Address as a Custom Field (Beta), the same picklist values are automatically available in custom address fields. You cannot specify separate picklist values for standard versus custom address fields. Read the Help & Training article, Address as a Custom Field (Beta) Requirements and Limitations, for more information on this feature.
Customize related lists directly in Lightning App Builder instead of in the page layout editor using the new Dynamic Related List – Single Component. You can choose the list’s fields, sort order, filters, and a list descriptive name. This allows you to have different related lists for the same object with different filters. Note: For the initial release of this feature, you won’t be able to filter using picklist and can only view up to 30 records in the related list.
The Migrate to Flow tool, now GA, allows you to convert your workflow rules, including most rule criteria formulas, to a record-triggered flow. Note: This tool will convert one workflow rule to one record-triggered flow.
The tool supports workflow rules that contain the following:
In Summer ’22, the enhanced tool now also supports:
Note: Formulas that use Hour, Minute, Second, TimeNow, TimeValue, IsClone, or $RecordType are not supported.
Check out the Migrate to Flow Tool Considerations Help article for more information.
You can now send a message to a Slack channel, a direct message, or the Messages tab of a Slack app that includes a button the recipient can use to launch a flow. The Slack Send Message to Launch Flow invocable action is available in Beta in sandboxes.
In Flow Builder, create a screen flow that only includes screen components supported in Slack. Select the Make Available in Slack (Beta) checkbox in the Advanced area when you save the screen flow. Build a second flow that includes the slackSendMessageToLaunchFlowflowName invocable action, where the flowName is the API name of the flow to send.
Note: Users must have a permission set with the Connect Salesforce with Slack permission to use this feature.
Hooray! This has been a long-awaited Flow feature. I can hear all the #Flownatics getting excited over this one. Formula builder is now available for use in the Start element of a record-triggered flow! You can use formulas to access related records and build more complex queries, too. Time to get rid of the old workaround—create and reference a formula custom field in the flow entry criteria. For the condition requirements, specify Formula Evaluates to True (NEW) and insert a resource, function, and operator.
Click the Go To connector element name to locate the outbound connected element. To locate all inbound connections for a given Flow element, click Connections. All inbound linked connectors will show as highlighted.
![How to find an outbound and inbound connector for a flow].](https://d3nqfz2gm66yqg.cloudfront.net/images/20220509143921/GoToConnectors1.gif)
Make your Apex-defined invocable actions stand out on the Flow Builder canvas with custom icons. Upload a SVG file as a static resource or select a standard Salesforce Lightning Design System icon. Set the value of the iconName attribute of the InvocableMethod annotation and voila! When you add the invocable Apex action to your flow, the custom icon automagically appears.
Use section headers in your screen flow for better UI organization for your users. Sections with headers are always open by default but are collapsible. To display the section header to the user, use the Section screen flow component and check Include Header.
Create screen flows faster using the Name and Address data type fields. The field name, data type, help text, required-ness, and possibly existing values are automagically configured for you. 
Beginning in Winter ’23, two-column layouts will be ignored in favor of using section components to create multicolumn screen flows. The section components give you greater features above and beyond the two-column layout. To prepare for the change, we recommend you update your screen flows to use the section components prior to the enforcement.
To determine whether your screen flow uses the two-column layout:
The dependent picklist component has been rebuilt in Lightning Web Components (LWC), improving the overall error handling user experience where it can now show two potentially duplicate error messages as opposed to only one.
Reduce the number of screen flows you need to create by designing screen flows where screen components can react to updates on the same screen.
If you’re interested in participating in this pilot, please ask your AE to nominate you for the Salesforce Flow: Reactive Screen Components pilot.
The drag and drop function for Flow Trigger Explorer is now here! No more manual editing the order by opening and editing each individual flow. Just drag your record-triggered flow or orchestration into the order you want it to run and voila! The sorting order is automagically re-sorted for you.
When you create a new flow directly from within Flow Trigger Explorer, you create the new flow prefilled based on the category and context you created them from, saving you clicks.
You can now access Flow Trigger Explorer directly from Object Manager for quick access to your record-triggered flows and orchestrations. Navigate to an object within Object Manager, then access Flow Triggers. On the Flow Triggers page, click Flow Trigger Explorer. This saves you time in not having to go to the Flows setup page to access Flow Trigger Explorer to find the record-triggered flows and orchestrations for that object.
Use these shortcuts when navigating the Flow Trigger Explorer feature.
Action | Keyboard Shortcut |
Switch section focus | F6, Shift+F6 (backwards) |
For reordering flows, these keyboard shortcuts are added.
Action | Keyboard Shortcut |
Select flow | Spacebar |
Drop flow | Spacebar |
Move flow | Arrow keys |
Cancel reordering | Esc |
You can now create and save a flow test from a debug run of your record-triggered flow without developer resources. With these flow tests, you can re-run them at any time and all your needed test data scenarios are there. No need to recreate them or do manual testing using Flow debugger! For now, you can only run these on your record-triggered flows.To create a flow test in a record-triggered flow, click View Tests (Beta) and then Create. To run a test, click Convert to Test from a debug run. Note: To view test run details, you’ll need the View All Data permission. However, you can view test results and run tests without this permission.There are some beta limitations and considerations:
The following updates only impact flows and processes created with API version 55.0 (new flows or processes you create starting with the Summer ’22 Release):
Text data coming into flow that looks like a merge field will show the merge field notation instead of the merge field’s evaluated value (which is what it does in API version 54.0 and earlier).
Let’s say you send the following into your flow: Contact {!Contact.First Name} {!Contact.Last Name} regarding Opportunity {!Opportunity.Name}. The merge fields notation {!Contact.First Name}, {!Contact.Last Name}, and {!Opportunity.Name} will remain as is.
IMPORTANT NOTE: If you have flows that rely on using the evaluated merge field values, you’ll need to implement a workaround using code. Have your developer create a custom Apex action that performs an equivalent merge field substitution, and then call it in a flow with the Apex Action element.
When using the add operator on a collection string value, the merge fields now show their values at the time of assignment and not their new values after evaluation (which is shown in API version 54.0 or earlier).
Processes that start when a record changes or have multiple criteria will not evaluate the original value of the field even if the original value is null. Note: If you use the “Do you want to execute the actions only when specified changes are made to the record?” or the ISCHANGED() function in your criteria, this update can cause your process to behave differently. In API version 54.0 or earlier, if the original value is null, the newer value was used in the evaluation.
No more guessing when your orchestrations execute! With Flow Trigger Explorer, you take control by specifying the order of execution of your record-triggered orchestrations along with your record-triggered flows for a specified object. 
You can open an evaluation, screen, or autolaunched flow in Flow Builder directly from within your orchestration. Click the Open Flow in Flow Builder button. No need to exit the orchestration and navigate to the flow separately. Another click-saver!
Create and test your orchestrations in a sandbox, and deploy it and its associated flows to another sandbox or Production using a change set. Note: Just like flows, your orchestration and associated flows will deploy into the target org as inactive. You’ll need to manually activate the components in the target org.
Fire a Flow Orchestration Event platform event to wake up an associated paused orchestration by saving the orchestration’s run ID for later use from the new $Orchestration.Instance system variable.
Your orchestration will now capture milestones in its history, such as when an orchestration is canceled; a stage or step is discontinued; an orchestration, stage, or step has encountered an error; or a work item is reassigned. These milestones may be helpful in testing or debugging your orchestration.
We missed this update in the last release, so we’re calling it out to ensure you’re aware—because it’s a big deal. The formula compile size has tripled from 5,000 to 15,000 allowing you to write more complex formulas to support your business. The compile size is the size of the formula in bytes, which includes all of the fields, values, and formulas it references. Thank you, Steven Tamm!
In Summer ’22, we’re introducing 18 new formula functions:
UNIXTIMESTAMP (date/time) | Returns the number of seconds since 1 Jan 1970 for the given date, or number of seconds in the day for a time |
ISOWEEK (date) | Returns the ISO 8601 week number for the given date (from 1-53) so that the first week starts on Monday |
ISOYEAR (date) | Returns the ISO 8601 week-numbering 4-digit year for the given date so that the first day is a Monday |
DAYOFYEAR (date) | Returns the day of the calendar year (from 1-366) |
FORMATDURATON (numSeconds[, includeDays] | dateTime/time, dateTime/time) | Format the number of seconds with optional days, or the difference between times or dateTimes as HH:MI:SS |
FROMUNIXTIME (number) | Returns the number of seconds since 1 Jan 1970 for the given date, or number of seconds in the day for a time |
CHR (number) | Returns a string with the first character's code point as the given number |
CHR (text) | Returns the first character's code point from the given string as a number |
TRUNC (number,num_digits) | Truncates a number to a specified number of digits |
PI () | Returns pi |
SIN (number) | Returns the sine of the number, where the number given in radians |
COS (number) | Returns the cosine of the number, where the number given in radians |
TAN (number) | Returns the tangent of the number, where the number given in radians |
ASIN (number) | Returns the arc sine of the number in radians, if the given number is between -1 and 1; otherwise NULL |
ACOS (number) | Returns the arc cosine of the number in radians, if the given number is between -1 and 1; otherwise NULL |
ATAN (number) | Returns the arc tangent of the number in radians |
ATAN2 (y, x) | Returns the arc tangent of the quotient of y and x in radians |
INITCAP (text) | Returns the text as lowercase with first character of each word made uppercase |
ASCII (text) | Returns the first character’s code point from the given string as a number |
You can now create and manage restriction rules for external object records to add that extra layer of security, to ensure only the appropriate users can view data external to Salesforce. Note: As with all restriction rules, we recommend only using object fields that are indexed especially in record criteria.
Users can create a record even if a restriction rule subsequently blocks their access to it. Users can also edit a record to a value that a restriction rule subsequently blocks their access to.
Users with View All or Modify All permissions can access records that have a restriction rule applied to them.
We updated access rights to ensure only the appropriate users have access to personally identifiable information (PII) in Summer ’22. Users with View All Data and View All Users permissions cannot view personal information fields. To grant user access to this information, assign the View Concealed Field Data permission.
Use single picklists to restrict record access with a restriction or scoping rule. Note: Scoping rules are available in Lightning Experience to customers using Unlimited or Performance Edition with Signature Support or Implementation Architect, Program Architect, or Technical Account Manager professional services.
You can now assign expiration dates to permission sets and permission set groups in addition to creating list views to better manage your users. To enable this feature, go to User Management Settings in Setup, and enable Permission Set & Permission Set Group Assignments with Expiration Dates. From the Permission Set Group or Permission Set page, click Manage Assignment. Previously, this feature was in Beta.
For customers with Event Monitoring, you can create transaction policies to track any changes to your permission sets and permission set groups AND block any permission changes that do not adhere to your security policies. You can also use this feature to send notifications to the admin if changes are made and block changes that do not comply with internal usage, compliance, or security policies. Previously, this feature was in Beta.
You can create transaction security policies to block these user assignments:
Once the update is enabled, admins can set an expiration date for each permission set and permission set group, and also use the new Lightning Experience UI and workflow to handle these assignments. This release update will be enforced in Winter ’23. Currently, by default, permission set and permission set groups do not expire. To enable this, search for Release Updates, find the Enable Permission Set Group Assignments with Expiration Dates release update, then follow the testing and activation steps.
These enhancements are available with the Security Center add-on subscription.
New security policy types are now GA: Trusted IP Ranges, Health Check Baseline, Password Configuration, and Session Settings.
Create reports on Security Center permissions, logins, and monitoring metrics with new custom report types.
Target global-level elements such as Einstein Search, Help, and Trailhead or target action buttons in the Actions Ribbon on list views and record pages to show for In-App Guidance to your users.
Note: These add-on features are available with Salesforce Feedback Management Starter and Growth licenses.
You can group multiple questions that have the same choice answers and group related questions, allowing your survey takers to complete the survey faster.
Promote brand loyalty and increase responses by adding your logo to surveys. In Survey Builder, select the Branding tab and scroll down to the Logo section to upload a logo.
You can add links to the Thank You page that’s shown to users after they respond to a survey that take them to your company website, social media pages, or other web pages. In Survey Builder, go to the Thank You page and turn on Customize Page.
Go to Search Manager in Setup. Then, navigate to an object to view the fields that are searchable by your user.
Natural Language Search (NLS) allows you to specify what you’re looking for in the search bar. NLS will return the list of articles that match your keyword and search criteria. You can filter articles by publication status, creation date, or author.
MuleSoft Composer for Salesforce (or simply, Composer) allows admins to build automation for data declaratively within Salesforce. Composer has its own product release notes. Note: Composer requires an additional cost. Talk to your AE for details. Custom Expression Editor was introduced as a new Composer feature in mid-April.
Update your primary billing contact in the app. No need to contact Salesforce.
You can now use an existing organization-wide email to set as your default no-reply address. Now, set any organization-wide email to serve multiple purposes. 
Once you enable enhanced domains, the *.force.com URLs for your Experience Cloud and Salesforce sites will change. You have the option to choose to either redirect those public-facing URLs to your enhanced domain URL (set as the default) or return to the error message page. Go to the My Domain Setup page; in the Routing section, the Previous force.com Site URLs should be set to redirect mycompany.force.com and mycompanyportal.force.com URLs to your current My Domain site URLs.
Sandbox orgs (new Developer Edition orgs, demo orgs, sandboxes, scratch orgs, patch orgs, free orgs, and Trailhead Playgrounds) are partitioned when you enable enhanced domains. Salesforce will gradually roll out the service delivery changes by org type. When the partition becomes available for that org type, new orgs will be partitioned by default. To prepare for this upcoming change, update your allowlists for the new domains so your users can access the partitioned domains. The partitioned domains will include a word related to the org type:
An example of a My Domain login URL format for a partitioned Developer Edition org is https://MyDomainName.develop.my.salesforce.com.
In Developer Edition orgs, scratch orgs, free orgs, and Trailhead Playgrounds with enhanced domains, you can enable or disable this feature in the My Domain Details section of the My Domain Setup page. This option is only available if partitioning is available for your org type. For updates about the availability of this feature by org type, join the My Domain and Enhanced Domains group in the Trailblazer Community.
For increased security of your connected apps and to allow for minimal downtime, you can now generate new consumer key and consumer secret information for a connected app and apply the new details when you’re ready to make the switch to the new information.
For improved security, you’ll be required to verify your identity by completing MFA before you can view a connected app’s consumer key and consumer secret details. After 5 minutes of viewing, you will be challenged again to verify your identity.
You can now configure Microsoft as an authentication provider and allow your customers to log in to Salesforce and Experience Cloud sites with their Microsoft credentials.
The Customizable User Settings component has been updated to allow Aura site users to deactivate their account. Go to User Management Settings in Setup and enable User Self Deactivate. Then, in Experience Builder, configure the new Account Details properties of the Customizable User Settings component. Don’t forget to deselect the Hide the Deactivate Account section checkbox.
You can now use flows in LWR (Lightning Web Runtime) sites, across all LWR templates. Build the flows in LWC in order to use flows in a LWR site.
The Run Flows permission will be removed from the Guest User profile in all orgs in Spring ’23. To avoid any future access issues, we recommend you update your sites to use the new permission structure embedded in flows prior to Spring ’23.
To provide the appropriate Aura, LWR, and Visualforce Experience Cloud site users with access to personal information, assign those users the View Concealed Field Data permission via a permission set.
As an admin, you can now enable person accounts in your org yourself. Person accounts allow you to store information about a person in a record that acts like an account when necessary. You can enable person accounts after all three prerequisites are met:
Access Person Accounts in Setup to enable this feature.
Note: Once person accounts are enabled, they cannot be disabled. We recommend you enable this in a sandbox and review the org with implications prior to enabling it in Production.
Don’t forget, as a best practice with each release, to review the release updates to ensure you’re on top of upcoming updates, giving you ample time to test and activate the release updates before they’re enforced in your org.
To learn more, go to Release Updates in Setup. Give yourself ample time before an update is enforced to enable it in a sandbox, do proper testing, and make any necessary changes to code and configuration to ensure all still works post update.
I’m calling out a few of the release updates here. I recommend reviewing the comprehensive list of the release updates for those that apply to your org.
To comply with the latest browser and security standards, Salesforce will enforce enhanced domains on My Domain in all orgs in Winter ’23. Enhanced domains is available in all orgs except Public Cloud orgs. What is enhanced domains, you ask? It allows your company-specific My Domain name in your URLs, including your Salesforce sites and Experience Cloud sites. Your users can access Salesforce using browsers that block third-party cookies. Since this update does affect your application URLs, including Experience Cloud sites, Salesforce sites, and Visualforce pages, we highly recommend you enable and test enhanced domains in a sandbox before the update is enforced in Production.
Salesforce is upgrading its SAML (Security Assertion Markup Language) framework as part of regular maintenance. This update can impact integrations with third-party systems with SAML identity providers and SAML-enabled applications. To review this update, from Setup, type “Release Updates” in the Quick Find box, and then select Release Updates. For Upgrade SAML SSO Framework, follow the testing and activation steps.
Starting in Spring ’22, you cannot assign guest users permission sets or permission set groups that contain permission set licenses with View All, Modify All, Edit, and Delete standard object permissions. In Winter ’23, Salesforce will enforce this update and remove all affected permission set and permission set assignments from guest users. We recommend you review customizations to avoid disruption in functionality prior to the enforcement. There are some replacement permission set licenses intended for guest users that only contain allowed permissions in the Summer ’22 Release.
The original release update was enforced in Spring ’22 but the update was not successful in all orgs. Orgs that weren’t enforced in Spring ’22 will be enforced in Summer ’22. MFA challenges are bypassed for users with the user permission Multi-factor Authentication for User Interface Logins who are logging in with a SSO Auth Provider. Previously, in some cases, a user completed MFA twice.
The original release update was enforced in Spring ’22 but the update was not successful in all orgs. Orgs that weren’t enforced in Spring ’22 will be enforced in Summer ’22. Users must reset their password before changes to their email address and password become active. Previously, the new email address became active upon save with no verification. Admins can now change an email address and reset a password in one step.
Salesforce now matches email headers to their associated cases. With this new threading behavior, new outbound emails do not contain the Ref ID. Note: This update will be enforced in Summer ’23. Before you enable the Email-to-Case threading capability, we recommend you verify that there’s data in the Message-ID, In-Reply-To, and References fields. It’s important that getCaseIdFromEmailHeaders replaces getCaseIdFromEmailThreadId wherever you are referencing it in your custom code. Otherwise, incoming responses will not link to the existing case but instead will create a new case.
Phew! That was a LOT of features we just reviewed. Which Summer ’22 user or admin productivity enhancements are you most excited about? Share with us on Twitter @SalesforceAdmns using #AwesomeAdmin.
Picture this: It’s release week. You’re prepping your orgs, coordinating with your stakeholders, and keeping a close eye on maintenance windows. Suddenly, your inbox is flooded with status alerts. You pause everything to sift through them, manually cross-referencing your specific instance names against hundreds of global updates, only to realize that none of those alerts […]
Calling all admins! It’s almost time for the Summer ’26 Salesforce Release! An essential part of every admin’s job is staying on top of the latest Salesforce Releases. Three times a year, Salesforce releases new features and updates to our technology, enabling users everywhere to take advantage of the latest and greatest that our platform […]
Spring ’26 introduces Screen and Component Styling Overrides in Flow Builder, giving admins more control over how screen flows look and feel without custom code. As with any feature that expands customization, it comes with responsibility. Styling flexibility is powerful, but without a clear approach it can create inconsistency, or a screen that looks like […]
