Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Winter ’25 (API Version 62.0)

          Winter ’25 (API Version 62.0)

          These updates affect only flows that are configured to run on API version 62.0 and later.

          Required Editions

          View supported editions.

          Enforce Sharing Rules when Apex Launches a Flow

          This versioned update enforces sharing rules when an Apex class that’s declared using the with sharing keyword launches an autolaunched flow that runs in the default context. To enforce sharing, the Apex class must be declared using the with sharing keyword.

          Previously, the flow ran in system context without sharing even when an Apex class was declared using the with sharing keyword launched the flow.

          With this versioned update, the flow runs more securely in the default context when an Apex class that’s declared using the with sharing keyword launches an autolaunched flow. The flow enforces the sharing rules of the user that executes the Apex class. Previously, when sharing rules weren’t enforced, the flow was able to access all data.

          This versioned update restricts data access for autolaunched flows that are run in the default context and launched by an Apex class. The Apex class must be declared using the with sharing keyword. Data access is restricted to the sharing rules of the user that executed the Apex class.

          For example, a query can return fewer rows than it did in system context without sharing. An operation can fail because the user doesn’t have the correct permissions.

          Set Screen Action Outputs to Null Correctly

          In API version 62.0 and later, this versioned update makes sure that if a flow run by a screen action has an output that isn’t set by using an Assignment element, its outputs are set to null, as expected. Screen components using that output are now updated automatically.

          Set Conditionally Hidden Screen Component Outputs to Null Correctly

          In API version 62.0 and later, this versioned update makes sure that if a conditionally hidden screen component has a collection as an output, its outputs are set to null, as expected.

           
          Loading
          Salesforce Help | Article