This article includes links to and information from outside resources. We are not responsible for the content on the external site. If there is a link that does not work, please email [email protected] and we will attempt to adjust the information with an updated link. 

We are so excited to partner with the best in the CRM business because their releases help you too! The Summer '23 release for Salesforce is rolling out, and below are some of the key enhancements we want to highlight as your Salesforce partner.

 

Align Fields Horizontally in Field Sections

Sometimes small enhancements make a significant impact! Aligning fields horizontally is a convenient new feature.

 

This change aligns fields with their neighbors in the same row, enhancing page aesthetics. In the example below, the image on the left is without alignment, and the image on the right is with alignment – observe the spacing and alignment of the "Phone" field!

 

Optimize Your App Pages with Accordion and Tabs Components

Accordion and Tabs components are now available for app pages. These components enable better organization and improved performance on your pages.

 

Limit the Number of Inactive Picklist Values (Enforced in Summer '23)

This change, announced in Spring '23, is enforced in Summer '23. The update limits the number of inactive picklist values in a custom picklist field to 4000. Previously, you could remove the limit, but this release removes that ability.

 

Manage Salutation Picklist Values in Lightning Experience

Now you can manage and update the picklist values for the "Salutation" field in Lightning Experience. Previously, you had to switch to Salesforce Classic to modify them.

Reflect the Diversity of Your Customers with Gender-Neutral Salutations

Summer '23 adds a new option to the Salutation picklist. The Mx. salutation is now available by default. As the admin, you'll need to update the picklist to make this new value visible to users.

Set Field-Level Security for a Field on Permission Sets Instead of Profiles (Generally Available)

Setting field-level security for a field on permission sets is now generally available. The update also provides an enhancement that allows you to see each permission set's object permissions for the field's object without leaving the page.

See Object Names in Record Tabs

When viewing or inline editing a record, Salesforce displays the record name, object name, and Salesforce in the tab name. The object name doesn’t appear when fully editing a record in Lightning, but it appears when fully editing a record in Lightning Console. Previously, Salesforce displayed only the record name and Salesforce in the tab name when viewing or editing a record.

Allow Delegated Admins to Manage Permission Set Group Assignments

Delegated Admins gain more capabilities with the ability to manage the assignment of permissions set groups for users in their delegated group.

See More Information in Reports from the User Access and Permissions Assistant

Reports from the User Access and Permissions Assistant now contain key details, including users' titles, profiles, and whether they're active. The performance of these reports has also been improved for orgs with a high number of users. The User Access and Permissions Assistant app was created by Salesforce and is available on the AppExchange.

Set Your Users’ Session Timeout to 90 Minutes

For more flexibility, you can now set the session timeout value in Session Settings to 90 minutes.

Verify User Email Addresses

To protect your org and user data, ensure that your users have a verified email address. You can now manage email verification with simple UI tools instead of code. While viewing a user’s details, you can see whether their email address is verified and initiate verification with a few clicks. Your users can also see their email address status and begin verification for themselves. To finish verifying, they click a link received at their unverified email address.

Get Better Performance for Related Lists

When using the related list "View All" page, expect greater performance! This page now renders using Lightning Web Components instead of Aura.

Calendar

The calendar has received several enhancements to maximize your productivity with the Summer '23 release, including:

• View up to 500 events.

• Enable events for up to 50 shared calendars and resources.

• Drag events to reschedule.

• Click an event to preview (instead of hovering).

• View overlapping event tiles, expanded text, and shaded coloring for dates in the past.

Click Once to See Your Calendar

Another productivity enhancement is the ability to view your calendar with a single click, without interrupting your current work on the screen. Click "View Calendar" to pop open your calendar in a new tab.

Provide More Detailed In-App Guidance with Targeted Prompts on Record Fields

In-App Guidance just got even better, with the ability to provide even more clarity by targeting specific fields!

MFA Auto-Enablement Continues: Find Out When and How Your Org Is Affected (Release Update)

As of February 1, 2022, Salesforce requires all customers to use multi-factor authentication (MFA) when accessing Salesforce products. To help customers meet this requirement, Salesforce is automatically enabling MFA for production orgs in several phases via the MFA Auto-Enablement Release Update. The first phase of orgs completed MFA auto-enablement in Spring ’23. For orgs in the second phase, MFA is auto-enabled with Summer ’23. For orgs in the third phase, MFA is auto-enabled with Winter ’24. Auto-enablement concludes for any remaining orgs in Spring ’24.

Where: This change applies to Lightning Experience, Salesforce Classic, and all Salesforce mobile apps in all editions.

When: To know when your production org is affected, monitor the Release Update node in Setup for the MFA Auto-Enablement Release Update.

• Phase 2 orgs: The release update for this phase was made available in Spring ’23 and goes into effect with Summer ’23. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab. Note that the MFA release update usually takes effect when your org is updated to Summer ’23, but in some cases a delay of several hours to a few days is possible before MFA is auto-enabled for your users.

• Phase 3 orgs: If you see the release update after Summer ’23 finishes rolling out, your org is scheduled to be auto-enabled in Winter ’24. In rare cases, it can take several weeks for the update to appear after the Summer ’23 rollout is complete.

• For orgs not included in phases 1–3, the release update will be available in Winter ’24.

How: The release update automatically turns on this setting: Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org. MFA isn’t enforced at this stage, so you can turn off the setting if your users aren’t ready yet. Users who have the Multi-Factor Authentication for User Interface Logins user permission experience no changes when the setting is enabled.

When MFA is turned on for your org, the process for logging in to the UI changes. After a user enters their username and password, they must verify their identity with an MFA verification method such as an authenticator app, security key, or built-in authenticator. If users haven’t done so already, they’re prompted to register a verification method the next time that they log in after this release update goes into effect.

To prepare for this update, we recommend taking these steps.

• Verify whether your org has exempt user types that must be manually excluded from MFA before MFA auto-enablement occurs. See Exclude Exempt Users from MFA (can be outdated or unavailable during release preview) in Salesforce Help.

• Train your users on how to acquire, register, and log in with MFA verification methods. See Change Management for a Successful MFA Rollout for guidance and customizable templates.

If your users aren’t prepared to start using MFA when Salesforce auto-enables it, you have two options.

• Your users can skip MFA registration for 30 days and log in as usual. This grace period begins on the day the org is auto-enabled, and the same 30-day window applies to all users in the org. For example, if a user logs in 5 days after their org was auto-enabled, 25 days remain before they’re required to register for MFA.

• In the unlikely event that users experience issues with MFA, you can temporarily disable it. But keep in mind that when your org reaches the MFA enforcement milestone in the future, Salesforce will re-enable MFA and remove the option to disable it.

  1. From Setup, in the Quick Find box, enter Identity, and then select Identity Verification.

  2. Deselect Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org.

  3. Save your changes.

• MFA Auto-Enablement Comes with an Improved Registration Experience
  Now it’s easier for your users to register identity verification methods when multi-factor authentication (MFA) is auto-enabled for your org. The new registration process begins with a list of all supported verification methods instead of just the Salesforce Authenticator option. With this experience, users can immediately choose their preferred verification method. To prioritize using Salesforce Authenticator, you can revert to the original experience from Setup.