Salesforce Winter ’23 Release

  1. Create Overlays with the New Model Component:-Use Models to interrupt a user’s workflow and draw attention to an important message. A Model, which displays the message on top of the current app window, requires a user to interact with it to regain control over the app.
    • To create a Model component, import LightningModel from lightning/Model in your JavaScript file. Then, create a component class that extends LightningModel. winter23
    • This component doesn’t use a lightning-Model tag. Instead, the Model’s HTML template uses helper lightning-Model-components to make the Model’s header, footer, and body. The lightning-Model-body component is required, and the others are optional. winter23
  2. Fix Invalid Template Usage to Avoid Warning When Component Loading: –Loading an LWC component results in a warning if your component includes a <template> element with an invalid attribute. On non-root <template> elements, only for:each, iterator:iteratorName and if:true|false directives are supported. Salesforce recommends that you fix your component template to remove invalid attributes in your <template> element.

    In Spring’23, this invalid usage of the <template> element doesn’t render correctly and loading a component that contains this invalid usage will result in an error.For example, the non root <template> element in this example contains an invalid attribute.


    To fix the warning and make sure that your component continues to load correctly in future releases, remove the invalid attribute or use another element like <div> or <span>, depending on your use case.

  3. .Be Ready for Multi-Factor Authentication Auto-Enablement:-The requirement to use multi-factor authentication (MFA) when accessing Salesforce products went into effect on February 1, 2022. All users must now use MFA when they login to Salesforce, whether they’re logging in directly or using single sign-on (SSO). To help customers satisfy this requirement, in the first half of 2023, Salesforce is automatically enabling MFA for direct logins. In the September 2023 timeframe, we’re enforcing MFA by making it a permanent part of the Salesforce login process. To avoid disruptions to your users when these milestones occur, enable MFA as soon as possible.
    Salesforce Flow Enhancements: –There are several enhancements in Salesforce Flow as follows:
    1. Cut and Paste Flow Elements: – Change the order of flow elements auto-layout faster by using cut and paste. Previously, to move an element on the canvas, you copied and pasted the element then deleted the original element, and then you updated the API name of the pasted element.
    2. Use Formula Builder in Flow Resources and Collection Filter Elements: –You can now use an enhanced formula builder in Flow Formula-type resources and the Collection Filter element. The builder guides you through the syntax so that you can create an expression more easily. Instead of waiting until you save a flow, you can check the formula syntax and catch errors as you work. winter23
    3. Select Multiple Records in the Lookup Flow Screen Component: – Now you can search and then select more than one record with the Lookup flow screen component. You can specify a selection maximum and one or more default records.
      • Add the Lookup component to your screen flow and set the Maximum Selections field to a value greater than 1. winter23
    4. Use Record-Triggered Flows to Update Related Records: – Now you can use record-triggered flows to update any records related to the triggering record.
    5. Launch Screen Flows With Lightning Web Components: – Embed a screen flow from any Lightning Web Component with the new lightning-flow component. Developers can supercharge their flows by customizing finish behavior, setting custom styling, or launching flows from their Lightning Web Components. And they can offload complex input collection and branching logic to Flow, saving time and money.
      Example shows an LWC component with the Survey_customers flow API name winter23
    6. Use In and Not In Operators in Flows to Find Related Records: – With the new In and Not In operators, a flow accesses a collection of primitive values to get related records without using the Loop element. The flow uses fewer SOQL queries and DML statements and performs faster. The new operators support accessing collections of type Text, Number, Date, Date/Time, Currency, and Boolean. The operators are available in the Get Records, Update Records, and Delete Records elements. winter23
    7. Test One, Two, Three, Flow (Generally Available): – 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. Flow tests don’t support flows that run when a record is deleted. This feature, now generally available, includes some changes since the last release. Flow tests now support scheduled paths. Previously, flow tests
      supported only paths that run immediately. Packaging is now supported.
    8. Filter Your Picklists By Record Type in Flow Screens: – Now you only see relevant picklist values when using Dynamic Forms for Flow. Previously, all the picklist values for a field appeared, regardless of whether a record type was provided, and could show irrelevant values.
    9. Select Multiple Records from a Table in a Flow Screen: – Leverage the new Data Table (beta) flow screen component to display a list of records on a flow screen. You can set the table to read-only, or enable your users to select one or more records and use their selections later in the flow. And users can change the width of table columns and wrap or truncate overflowing text.
      Add the Data Table (beta) component to your screen flow and configure the fields. winter23
Write To Us