To help you easily view all of your record-triggered flows by the object, Salesforce introduced Flow Trigger Explorer in the Spring '22 release. It is a great tool that displays record-triggered flows in a single place.
If you have a lot of flows (active or inactive), it can be hard to see them in a single place. In the Winter '24 release, Salesforce added an option to filter flows in Flow Trigger Explorer. Using this feature, you can filter flows by their status, package state, or process type.

4. HTTP Callout Supports More Methods
HTTP Callout is an amazing feature that Salesforce introduced in the Spring '23 release. In the previous release, they added a POST method as well. Starting with the Winter '24 release, HTTP Callout supports other methods as well (PUT, PATCH, DELETE).

5. Transform (Beta) Element
Salesforce introduced a new element called Transform (Beta). This element transforms source data to target data. For source and target data, you can select resources like outputs from actions, record variables, and Apex-defined variables. Then, map the data using the circled bullet icons.
In the screenshot below, this element transforms a lead record to a contact record.

It is also possible to use a formula for the mapping.

Output of this element is a variable (single or collection). For example, here the output is a Contact record variable and then it is used to create a Contact record.

Here is another example that transforms Contact records to Opportunity Contact Role records. It transforms a record collection to another type of record collection. Before this release, you had to use Loop and Assignment elements in order to achieve this.

6. More Components Are Reactive
Salesforce introduced reactive screen components in the Spring '23 release. With reactive screen components, your screen components can react to a user’s actions on the same screen. However, some of the standard screen components were not reactive. In the Winter '24 release, more components start to support reactivity. For instance, selection components are now reactive. On the other hand, display text component starts to be reactive too. However, it is a beta program and you have to opt in from Process Automation Settings in Salesforce setup.
As you can see from the screenshot below, reactive screen components is not a beta program anymore. If you are using API version 59, you don't need to enable reactive screen components.

7. Pause Element is Replaced By Wait Elements
Salesforce introduced 3 new Wait elements to replace the Pause element.

The Wait for Conditions element replaces the Pause element, there is nothing different here.

Wait for the Amount of Time element lets you wait for a specified amount of time. Valid values are Minutes, Hours, Days, and Months. Moreover, you can resume at a specific time of day.

Wait Until Date element lets you wait until a specific date and time.

8. Product Selector Screen Component
There is a new screen component called Product Selector. This input component lets you select products with quantities. In order to configure this component, you have to provide the available products and price book entries.


This element stores the output in an Apex-defined collection variable.
9. Auto-Layout User Interface Changes
The element configuration will now appear on the right side instead of as a popup.

10. Dynamic Actions on Mobile for Standard Objects
The future is all things ‘dynamic’: Dynamic Forms, Dynamic Interactions, and – the subject of this idea – Dynamic Actions.
Dynamic Actions enable admins to create uncluttered, intuitive, and responsive pages that display only the actions your users need to see based on the criteria you specify.
Instead of scanning an endless list of actions, your users will be presented with a simple choice relevant to their role, profile, or when a record meets certain criteria.

Currently, you can define different Dynamic Actions for mobile (versus desktop) for custom objects. This idea is advocating for this flexibility to be extended forstandard objects.
11. Disable Access to Session IDs in Flows (Release Update)
To improve security, this update prevents flow interviews from resolving the $Api.Session_ID variable at run time. Previously, when a flow screen included the $Api.Session_ID variable, the browser session ID of the user that ran the flow appeared on the screen. A user was able to employ the session ID to bypass security controls. This update was first made available in Winter ’23 and was scheduled to be enforced in Summer ’23, but we postponed the enforcement date to Winter ’24.
Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
When: Salesforce enforces this update in Winter ’24. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.
How: Before you apply this update, remove all dependencies on the $Api.Session_ID variable from your flows. Then, from Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. To get the Disable Access to Browser Session IDs in Flows release update, follow the testing and activation steps.