See Record Access Reasons in Lightning Experience

A user has access to a record, but why? Is it because of their role? Their territory? From a sharing rule? Now you can see why a user has the access they do, right from Record Sharing Hierarchy in Lightning Experience. Previously, you switched to Salesforce Classic to see this information. Sharing Hierarchy is now available on the action menu, not just in the Share window.

Power Up Recently Viewed Lists with Customizable Actions

Now you can add custom actions to your Recently Viewed lists. To be consistent with other list views, Recently Viewed lists now show the actions added to an object’s list view search layout. Some actions, such as Printable View, aren’t available on Recently Viewed lists. This feature originally was available in Spring ’21, then temporarily removed. It’s rereleased now with performance improvements and the option to disable custom actions.

Create a Dynamic Actions Bar for Your App Page (Pilot)

Install More Custom Fields

Each Salesforce edition has a limit on the number of custom fields per object that you can create and install. The new 900 limit on custom fields per object allows you to install more fields from AppExchange. For example, for the Unlimited Edition, you can create 800 custom fields on an object and install 100 fields from a managed package. The custom field limit can’t exceed 900, so if you’re approaching the limit, you should hard delete or erase custom fields that you no longer need.

Save Time with Mass Actions in Split View

No need to open a separate list page—act on multiple records at once, now in split view. Select items in the split view list and apply an action to all of them in standard or console view.

Create Quick Actions with Lightning Web Components

To save your users time and clicks, create a quick action that invokes a Lightning web component. On a record page, create a screen action that shows the component in a window, or create a headless action that executes with a click.

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.

<?xml version="1.0" encoding="UTF-8" ?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
   <apiVersion>52.0</apiVersion>
   <isExposed>true</isExposed>
   <targets>
       <target>lightning__RecordAction</target>
   </targets>
    <targetConfigs>
   <targetConfig targets="lightning__RecordAction">
     <actionType>Action</actionType>
   </targetConfig>
 </targetConfigs>
</LightningComponentBundle>

import { LightningElement, api } from "lwc";
 
declare default class HeadlessSimple extends LightningElement {
  @api invoke() {
    console.log("Hi, I'm an action.");
  }
}

Monitor Lightning Component Changes in the Setup Audit Trail

Aura component and Lightning web component modification tracking is available in Setup Audit Trail when a user create, change, or delete a custom Lightning component. Audit history is especially useful when multiple developers work on components.

Set a Default Value for Any Screen Component That Displays Choices

The defaultValue field on the FlowScreenField subtype of the Flow metadata type can now be used for choice resources. The defaultValue field is now supported when the FlowScreenField subtype has a fieldType field value of RadioButtons, DropdownBox, MultiSelectCheckboxes, or MultiSelectPicklist. A FlowScreenField can’t have both a defaultValue and a defaultSelectedChoiceReference field.

If the Default Value Is…	Then the Default Selection…
A choice resource that’s included in the list of choices associated with a screen component	Continues to be stored in defaultSelectedChoiceReference.
A choice resource that’s not included in the list of choices associated with a screen component	Is stored in defaultValue.
A FlowElementReferenceOrValue	Is stored in defaultValue. At run time, we select the choice whose value matches this selection.

Build Multicolumn Screens in Flow Builder (Generally Available)