Customers / Administrator’s Point of View

1. Create and Edit Records That a Restriction Rule Applies To: – Restriction rules no longer prevent users from creating or editing a record. Users can create a record that a restriction rule subsequently blocks their access to. A user can edit a record so that a restriction rule blocks subsequent access to the record based on the value they changed.
2. Use Flows in LWR Sites: – Ready to automate your processes and use them on your lightning-fast sites? Flows are now available in LWR sites, across all LWR templates. With flows, you can harness the unlimited flexibility of Flow Builder to show screen flows on your site. To use flows in LWR, build them with Lightning web components. Flows built with Aura components can’t run in LWR sites.
3. Preserve User Access to Personal Information Fields: – To ensure that the appropriate users can access personally identifiable information (PII) in Summer’22, update those users’ permissions. Users with broad permissions such as View All Data and View All Users can no longer view personal information. To give users access to personal information, assign the View Concealed Field Data permission, which replaces the View User Records with PII permission.
4. Share Service Resource Availability Using an Invitation URL: – Salesforce Scheduler has two new flows: Generate Appointment Invitation and Book Appointment from Invitation. Service resources can use the Generate Appointment Invitation flow to generate the invitation URL with their availability. They can restrict the period for which invitation URLs are available for appointment booking using URL expiration dates. Users can use the Book Appointment from Invitation flow to book appointments by using the invitation URL generated using the Generate Appointment Invitation flow. The invitation URLs direct users to the time slot page that shows the resource’s availability so they can quickly book appointments. If invitation URL has an expiration date, users can book appointments using invitation URLs only before the expiration date.
   
5. Search Layouts for Salesforce Classic Is Now List View Button Layout: – In Setup, the Search Layouts for Salesforce Classic page was renamed List View Button Layout.
6. Run Flows for Guest Users Is Being Deprecated: – In Winter’22 Salesforce discontinued the Run Flows permission for the Guest User and Experience Cloud External User profiles in new orgs. Without the Run Flows permission, you’re free to use the more granular permission structure embedded in Flows and give your users the detailed access they need. Run Flows will be removed from the Guest User profile in all orgs in Spring’23. To avoid future access issues, Salesforce recommend updating your sites to the new permission structure before Spring’23.
7. Customize Cumulative Rollup Names: – To tailor your forecast grid to your business, change the labels that represent cumulative rollups of forecast categories. For example, show cumulative rollups for Closed Only, Best Case, Commit, Most Likely, and Open Pipeline forecasts to reflect the way your company forecasts. Previously, label changes showed only for single-category rollups.
8. Get a List of Custom Picklist Fields with Inactive Values: – Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. Get email notifications when custom picklist fields have more than 4,000 inactive values and then use this information to bulk delete the inactive unused values. Previously, you checked each field for inactive values, which is time-consuming when there are many custom picklist fields.
9. Limit Results in Tabular Reports: – To fast-track to the most relevant records and to avoid unnecessary processing time, you can limit the number of rows returned in a tabular report in report builder. When you set a row limit, you can include the report as the source for a dashboard table or chart component.
   1. For example, to review the top 20 opportunities by amount, open the opportunities report in the report builder. Sort the Amount column in descending order (1). Then click Filters | Add Row Limit (2). Set the row limit to 20, and click Apply (3). Save your changes and run the report.
10. Test a Custom Domain with the Salesforce CDN Partner in a Sandbox: – Roll out changes to a custom domain such as https://www.example.com with confidence. Now you can test a custom domain that uses the Salesforce CDN partner to serve your site in a sandbox before you enable the updated domain in production.
    
    1. In production, on the Domains Setup page, edit your custom domain. Select the HTTPS option, Salesforce serves the domain over HTTPS using a Salesforce content delivery network (CDN) partner. In the Associated Org field, select your sandbox, and save your changes. After Salesforce provisions your changes, activate the custom domain in production. Then log in to the sandbox to finish updating the sandbox Experience Cloud sites domains.
11. Export Security Center Data with the Click of a Button: – Easily download a .csv file for tables that show your policies, alerts, and monitoring metric details to access important data whenever you need it.
    
12. Add an Enhanced Bot to Messaging for In-App and Web: – Create an enhanced bot for your Messaging for In-App or Web channels to ease the load for service agents and leverage flexible routing with Omni-Channel Flow.
13. Configure a Single Default No-Reply Address from Organization-Wide Addresses in Setup: – You can use an existing org-wide email address as a default No-Reply email address. Choose multiple purposes for an existing org-wide email address in the record page.
14. Account for Holiday Closures: – Refine your working hours and show holidays in the dispatcher console. Update operating hours so that service appointments aren’t scheduled on holidays. You can override holidays to schedule workers as needed by creating holiday shifts.
    1. Turn on Enhanced Scheduling and Optimization in Field Service Settings. Create holidays in setup, then add them to your operating hours. To add availability during holidays, select the Holiday field on a shift.
15. Enable Multi-Factor Authentication for Your Entire Org: – Now you can turn on MFA for all the users in your org with the click of a checkbox. This setting is the fastest way to satisfy the MFA requirement. It’s also the setting that Salesforce will use to automatically enable and enforce MFA in the future.
    1. To enable MFA for all users in your org, from Setup, in the Quick Find box, enter Identity and select Identity Verification. Then select Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org.
16. Exclude Exempt Users from Future MFA Auto-Enablement and Enforcement: – There are several use cases that are exempt from the MFA requirement. Salesforce will automatically exclude many of these cases when auto-enablement and enforcement milestones go into effect in the future. But even if you’re fully in compliance with the MFA requirement now, there are some exempt use cases that you must exclude on your own. If any of these situations apply to your org, avoid disruptions by using the new Waive Multi-Factor Authentication for Exempt Users user permission before Salesforce enables and enforces MFA.
17. See Related Sales Cadences in Task Reports: – New fields available in Task object reports let your users see the sales cadences, sales cadence states, sales cadence steps, and target dispositions ralated to each task.
18. Raise Flags and Whisper in More Channels: – The Phone, Messaging for In-App, and Messaging for Web-enhanced channels support flag raises and whisper messages. For example, an agent can raise a flag to get their supervisor’s attention, chat with them with two-way messaging, and then ask them to join the call to help resolve a complicated customer issue. Previously, only the Service Chat standard channel supported agents raising flags and supervisors sending one-way messages to agents.
    1. Agents can click Flag to raise a flag and enter a whisper message.
    2. The flag and whisper message appear in the Conversation component (1) for messaging sessions and Call Controls (2) and Omni-Channel widget for calls.
19. Customize the Agent Experience with Omni-Channel Alert Sounds: – Define custom sounds to notify agents when work is routed to them in Omni-Channel. You can play a different sound for each service channel or group of agents. For example, to differentiate the type of work, you can play a ringing sound for incoming calls and a ta-dah sound for incoming messages.
    1.  You can set up the sound notification in the presence configuration for a group of agents or in a service channel. The sound notification at the service channel level overrides the setting at the presence configuration level. When you set up the sound configuration, select the default sound or add a custom sound based on an audio file. You can also specify how long the sound plays.
20. Remove Guest User Assignments from Permission Sets Associated with Permission Set Licenses with Restricted Object Permissions (Release Update): – To improve the security of your data, Salesforce is removing guest user assignments from permission sets and permission set groups associated with permission set licenses that contain View All, Modify All, edit, and delete standard object permissions. The only standard object permissions allowed for guest users are read and created. You can no longer assign guest users permission sets or permission set groups that are associated with these permission set licenses that contain the restricted permissions. This update was first available in Spring’22.
21. Analyze Google BigQuery Data Directly (Generally Available): – Skip the hassle of bringing Google BigQuery data into Salesforce and prepping it before you can explore and analyze it. With CRM Analytics Direct Data for Google BigQuery, run explorations directly on your data in Google BigQuery after creating a live connection to it. You can query the data in real-time, explore it in tables, and visualize it in charts. To continuously monitor important metrics and accelerate business decision-making, you can also include your BigQuery data in dashboards. This feature, now generally available, includes support for binding functions in conjunction with the bigquery keyword.
22. Securely Connect Data Across Amazon DynamoDB and Salesforce (Generally Available): – Use the new Salesforce Connect adapter for Amazon DynamoDB to seamlessly and quickly integrate AWS data natively with Salesforce business applications. You can connect DynamoDB data sources to Salesforce through external objects and take advantage of the Salesforce Platform capabilities.

1. Create and Share Your Own Bot Templates (Beta): – Now you can create your own bot templates from scratch or from existing bots. You can even package and share your bot templates between orgs or on AppExchange so everyone can use your bot customized for your industry or use case. Bot template packages include stored intent data, Flows, and Apex, so you can go from idea to fully-featured bot in minutes.
2. Update an Existing Schema Connected to Flow: – If a registration is in use by a flow, now you can update it with a new, compatible API specification version. Previously, you couldn’t update a registered schema that was in use by a flow. If the new schema version isn’t compatible, the editing workflow notifies you which operations and schema objects are in use by which flows and by which Apex classes. With this information, you know which existing references are incompatible so that you can remove them before saving your updated registration.
3. Call Invocable Actions from Apex (Developer Preview): – Invocable.Action is a new Apex class that allows you to call invocable actions from Apex code. For the developer preview, this feature is available only in scratch orgs.

   To enable this feature in your scratch org, add a reference to CallIAFromApex in the project-scratch-def.json file in your SFDX project.

   {
    "orgName": "my company", "edition": "Developer",
    "features": [ "CallIAFromApex" ],
    "settings": {
      ...
    }
   }
   

   After you modify the file, reference Invocable.Action in your Apex code. This example uses the standard invocable action “chatterPost” to post a message to the current user’s feed.

   
   Invocable.Action action = Invocable.Action.createStandardAction('chatterPost');
   action.setInvocationParameter('text', 'This is a test.');
   action.setInvocationParameter('type', 'User');
   action.setInvocationParameter('subjectNameOrId', UserInfo.getUserId());
   List<Invocable.Action.Result> results = action.invoke();
   if (results.size() > 0 && results[0].isSuccess()) {
       System.debug('Created feed item with ID: ' + 
   results[0].getOutputParameters().get('feedItemId'));
   }
   

   This example calls a custom invocable action named Doubler that returns a number that’s twice the input value.

   
   Invocable.Action action = Invocable.Action.createCustomAction('apex', 'Doubler');
   action.setInvocationParameter('input', 1);
   List<Invocable.Action.Result> results = action.invoke();                                          
   if (results.size() > 0 && results[0].isSuccess()) {
       System.debug('Result is: ' + results[0].getOutputParameters().get('output'));
   }

4. Write Queries with GraphQL API (Beta): – Aggregate records, request explicit fields, introspect the schema and more with the GraphQL API for Salesforce. GraphQL is an open-source data query and mutation platform for APIs. Use the GraphQL API instead of REST APIs to send and receive data more efficiently and make your app perform better. Your app can query for all the data that you want in a single request, and the response contains only the data you need.
5. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Send Screen Flows to Slack with an Invocable Action (Beta): – Send a message to a Slack channel, a direct message, or the Messages tab of a Slack app that includes a button that a recipient can use to launch a flow.
   2. Use Formulas as Flow Entry Conditions: – A formula builder is now available in the Start element of a record-triggered flow. The builder guides you through the syntax and simplifies the process. Instead of waiting until you save a flow, you can check the formula syntax and catch errors as you work.
   3. Add Section Headers to Flow Screens: – Use section headers to create a visual hierarchy to guide your users to the most important items on a screen. Sections with headers are collapsible and always open by default to make screen flow completion more efficient.
   4. Manage the Run Order of Record-Triggered Flows from Flow Trigger Explorer: – Easily change the run order of record-triggered flows by dragging them into place. Flow Trigger Explorer lets you manage the run order of record-triggered flows without opening and editing individual flows.
   5. Two-Column Flow Layouts Are Superseded by Multicolumn Screens: – Starting in Winter’23, two-column layouts are ignored. But your data isn’t affected, and a better layout option is available. With the Section component, you can organize record fields and screen components in up to four columns directly on the screen. To prepare for this change, Salesforce recommend that you update your flow screens to use Section components.
   6. Make Custom Screen Components React to Other Components on the Same Flow Screen (Pilot): – Design a flow screen with custom screen components that respond to updates on the same screen, and reduce the number of screens for a user to navigate through. Previously, you placed these components on separate screens.
   7. Convert Workflow Rules to Flows with the Migrate to Flow Tool (Generally Available): – Start transitioning to Flow Builder. The Migrate to Flow tool now supports more kinds of workflow rules, including most rule criteria formulas. Use the Migrate to Flow tool to convert your workflow rules into flows. Flow Builder can do everything that workflow rules can do—and more.
      1. In Spring ’22, the Migrate to Flow tool supported workflow rules that contained these items:
         1. Field-based criteria
         2. Field updates
         3. Email alerts
         4. Outbound messages
         5. Time-dependent workflow actions
         6. 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)
      2. In Summer ’22, the Migrate to Flow tool now also supports:
         • Equal to null
         • Not equal to null
         • Rule criteria formula
         • Formulas that use Hour, Minute, Second, TimeNow, TimeValue, IsClone, or $RecordType aren’t supported.
   8. Test One, Two, Three, Flow (Beta): – Before you activate a record-triggered flow, you can now test it to quickly verify its expected results and identify flow run-time failures. In Flow Builder, you create, save, and run flow tests. Previously, you debugged a flow manually to troubleshoot failures each time they occurred. Now, you create and save a flow test from a debug run. Then each time you modify the flow, you can run the test. You can test only a flow path that runs immediately.
      1. Flow tests don’t support flows that run when a record is deleted.
      2. View All Data Permissions for Debugging Triggered Flows
6. Flow Orchestrator: – There are several enhancements in Flow Orchestrator as follows:
   1. See New Milestones in Orchestration History: – New orchestration history milestones make testing and debugging your orchestrations easier. See when an orchestration is canceled; a stage or step is discontinued; an orchestration, stage, or step encountered an error; or a work item is reassigned.
   2. Wake Up Paused Orchestrations: – You now have access to an orchestration’s run ID with the new $Orchestration.Instance system variable. Use it to save the ID to a record field so you can reuse it later to fire a Flow Orchestration Event platform event and wake up the associated paused orchestration run. This change gives you greater flexibility to wake up paused orchestrations.
   3. Deploy Orchestrations with Change Sets: – Develop and test orchestrations in a sandbox environment and use a change set to send the orchestration and its associated flows to production.
   4. Use Improved Orchestrator List Views: – Use the Recently Viewed list view for orchestrator runs and orchestrator work items to limit the items you view. Use the new Orchestration Developer Name column in Orchestration Runs list views to identify the API name of the orchestration associated with an orchestration run. Completed, canceled, or failed orchestration runs with no orchestration developer name indicate that the orchestration was deleted from the Flows page in Setup.
      1. In the App Launcher, find and select Orchestration Runs or Orchestration Work Items. Then select Recently Viewed from the list view dropdown.
7. Limit How Often a Recommendation or Offer Appears: – With Next Best Action Limit Repetitions, you can limit the number of times the same recommendation or offer appears on the same record or for the same user during a time period. For example, you can use Limit Repetitions so that service agents don’t see the same offer for a customer more than once a week. After you configure Limit Repetitions for a recommendation, Next Best Action captures the user’s response to a recommendation or offer and then filters out recommendations that don’t meet your thresholds.
8. Get the Result of Asynchronous Platform Event Publishing in Apex (Pilot): – Get the final result of an event publish operation through an Apex callback that you implement. Previously, you could get the intermediate queueing result only of an event publish operation, not the final result. Event publishing is asynchronous, and the immediate result returned in SaveResult is the result of queuing the publish operation in Salesforce. When resources are available, the system carries out the event publish operation, and the final result is sent in an Apex callback.

   The publish callback is an Apex class that implements the EventBus.EventPublishCallback interface. The interface includes two methods: onSuccess and onFailure.

   public class MyPublishCallbackClass implements EventBus.EventPublishCallback {
       public void onSuccess(EventBus.SuccessResult successResult) {
          // Your implementation.
          // ...
       } 
   
       public void onFailure(EventBus.FailureResult failureResult) {
           // Your implementation.
          // ...
       }
   }
   

   If the asynchronous publish operation is successful, the onSuccess method is invoked. If it isn’t successful, the onFailure method is invoked. Each method takes a parameter that contains the result of the publish operation.

   Apex publish callbacks are available for high-volume platform events. Legacy standard-volume events aren’t supported.
9. Group Platform Events into One Stream with a Custom Channel: – With a custom channel, you can receive a stream of event messages corresponding to one or more platform events defined in Salesforce. For example, if you defined platform events corresponding to orders for different regions, one client can subscribe to all those events and process them. Custom channels are supported in CometD clients only and you can add filters (beta) to them. By using only one client to subscribe to all events and using filters, your subscriptions are optimized.
   1. Create a custom channel, and specify the platform events it contains in Tooling API and Metadata API using PlatformEventChannel and PlatformEventChannelMember.
   2. Custom channels are supported for high-volume custom platform events that you define. They aren’t supported for legacy standard-volume custom platform events or standard platform events, such as real-time event monitoring events.
   3. For Performance, Unlimited, and Enterprise editions, you can add up to 50 distinct platform events as part of channel members to a channel. For Developer Edition and Professional Edition with the API add-on, this allocation is 5 distinct platform events. If the same platform event is a member of multiple channels, it’s counted once toward the allocation.
   4. As part of this change, Salesforce added the EventApiName field to event messages to distinguish the messages received on a custom channel. The field contains the type of event and is available in CometD clients that use a Streaming API endpoint with API version 55.0 and later. For example, this event message has an EventApiName of Order_EMEA__e, which means that it’s an Order_EMEA__e event.

      {
        "schema": "e8jMOnID4xDThlaPBMx5gg",
        "payload": {
          "City__c": "London",
          "CreatedById": "005RM000002Qu16YAC",
          "Amount__c": 20,
          "CreatedDate": "2022-03-29T13:45:19.230Z",
          "Order_Number__c": "2"
        },
        "event": {
          "EventApiName": "Order_EMEA__e",
          "EventUuid": "218544ad-0472-4315-970f-8825a2802de6",
          "replayId": 10306
        }
      }

10. Plan and Test Your System for Scale Using Performance Assistant: – Performance Assistant is your central hub of information and resources about scalability and performance testing with Salesforce. Use the step-by-step instructions, articles, and tools to help you architect your system, conduct performance testing, and interpret your results.
11. Secure Apex Code with User Mode Database Operations (Beta): – Declare if Apex runs database operations in user mode or system mode. The new Database methods support an AccessLevel parameter that lets you run database operations in user mode instead of in the default system mode.

    You can indicate the mode of the operation by using WITH USER_MODE or WITH SYSTEM_MODE in your SOQL query. This example specifies user mode.

    List<Account> acc = [SELECT Id FROM Account WITH USER_MODE];
    

    Database operations can specify user or system mode. This example inserts a new account in user mode.

    Account acc = new Account(Name='test');
    insert as user acc;

    The new AccessLevel class represents the two modes in which Apex runs database operations. Use this new class to define the execution mode as user mode or system mode. Use these new overloaded methods to perform DML and query operations.

    • Database.query methods
    • Search.query methods
    • Database DML methods (insert, update, upsert, merge, delete, undelete, and convertLead)
12. Debug Your Code More Easily to Run with Lightning Web Security: – Dig deep into your code as it runs with Lightning Web Security. Now you have greater visibility into your code as it runs in a JavaScript sandbox. Previously, you saw your source code with Lightning Web Security’s runtime changes in your web developer tools, which could make it difficult to find problems in your code. The features are optimized for Chrome DevTools.
    1. Enable Debug Mode for your Salesforce user account to see these improvements in source display while debugging your component code as it runs in a Salesforce org.
    2. Source location has changed so that you can find your files more easily in the Page tab of the Source panel. Instead of the lightning/n/modules folder, look for the lws folder. Expand the folder and see your component files organized under their namespace folder. Here you see the c namespace and its components on the current page.
    3. Source mapping is improved so that the sandboxed code in the lws folder now looks closer to your components’ source code. You can inspect it, use breakpoints, and so on, in the Source panel.
13. Load Large Datatables Faster with Virtual Rendering: – Display datatables with more than 200 rows more quickly and make them scroll more smoothly with virtual rendering. Use the render-mode and render-config attributes with the lightning-datatable component to enable virtualization for your datatable. Instead of rendering all the table rows on load, the datable renders the rows that are visible and a few rows above and below them to ensure smooth scrolling.
    1. This example shows how to enable virtualization for lightning-datatable in Lightning web components. See New and Changed Aura Components for an example using Aura syntax with the lightning:datatable component.
    2. In the JavaScript file of your component, create a renderConfig object with the attribute virtualize set to vertical.

       import { LightningElement } from 'lwc';
       
       export default class DataTable extends LightningElement {
           // set data
           // set columns
           renderConfig = {
               virtualize: 'vertical',
               // additional customization
           };
       }

       In the lightning-datatable component, set the render-config attribute to your renderConfig object. Set the component’s render-mode attribute to role-based and set the lightning-datatable component’s parent container to an explicit height.

       <template>
           <div style="height: 300px;">
               <lightning-datatable
                   key-field="id"
                   data={data}
                   columns={columns}
                   render-mode="role-based"
                   render-config={renderConfig}>
               </lightning-datatable>
           </div>
       </template>

14. Create Notifications with New Alert, Confirm, and Prompt Modules – Use the new modules LightningAlert, LightningConfirm, and LightningPrompt instead of native APIs to create notifications from your Lightning web components. Chrome and Safari plan to end support for cross-origin use of the window.alert(), window.confirm(), and window.prompt() native APIs. Each new module creates a modal that functions like its API counterpart and works in cross-origin iframes.This example creates an alert modal with an error message and “OK” button. The .open() function returns a promise that resolves when the user clicks “OK.”

    <!-- c/myApp.html -->
    <template>
        <lightning-button onclick={handleAlertClick} label="Open Alert Modal">
        </lightning-button>
    </template>

    // c/myApp.js
    import { LightningElement } from 'lwc';
    import LightningAlert from 'lightning/alert';
    
    export default class MyApp extends LightningElement {
        async handleAlertClick() {
            await LightningAlert.open({
                message: 'this is the alert message',
                theme: 'error', // a red theme intended for error states
                label: 'Error!', // this is the header text
            });
            //Alert has been closed
        }
    }

15. Enable Third-Party Integrations with Light DOM (Generally Available) – Lightning web components render in shadow DOM by default, providing strong encapsulation but posing challenges for global styling and many third-party integrations. With light DOM, your component markup is attached to the host element instead of its shadow tree. You can then access it like any other content in the document host.To enable a component to render in light DOM, set the renderMode static field in your component class.

    import { LightningElement } from 'lwc';
    
    export default class LightDomApp extends LightningElement {
        static renderMode = 'light'; // the default is 'shadow'
    }
    

    Use the lwc:render-mode template directive on the <template> tag of your component.

    <template lwc:render-mode='light'>
        <my-header>
            <p>Hello World</p>
        </my-header>
    </template>

    When you enable light DOM on a component, it no longer renders its elements in the #shadow-root tree.

    <my-app>
        <my-header>
            <p>Hello World</p>
        </my-header>
    </my-app>

    A light DOM component can contain a shadow DOM component. Similarly, a shadow DOM component can contain a light DOM component. However, base Lightning components always render in shadow DOM. Restricting light DOM to specific namespaces isn’t supported.