Why are there 2 versions of Flow Launcher?
Summary
Flow Launcher has two versions to handle launching other flows either with simple inputs/outputs or with complex Salesforce record data. The standard Flow Launcher supports basic input/output like text and integers, while Flow Launcher_SObject allows passing Salesforce records or collections as inputs and outputs, supporting more advanced use cases like editing datatable rows reactively in modals. The article showcases detailed example flows that demonstrate reactive flow invocation, record editing, and adding new records directly from datatables, improving efficiency and user experience in Salesforce screen flows.
Takeaways
- Use Flow Launcher_SObject to pass Salesforce records as flow inputs and outputs.
- Configure reactive flow launches by hiding buttons and reacting to input attribute changes.
- Name output variables precisely to enable value passing back from launched flows.
- Combine Flow Launcher with datatables and reactive collection components for inline record editing.
- Leverage Auto Navigate to streamline user navigation after flow completion.
Flow Launcher and Flow Launcher_SObject both allow you to launch any auto-launched or screen flow from an existing screen flow. They can show up in-line or as pop-up modals. The flows can be launched with a button, or you can hide the button and let the flows launch reactively when one of the input attributes changes. This post will review how to configure this component, when to use which version and provide some example use cases. Configuring Inputs for the Launched Flow You can pass values into the launched flow a few different ways. One is to specify the name of the input resource (variable) in the launched flow and identify the value to be passed to it. NOTE: The Flow Input Variable Name should be a text entry of the name of the attribute in the launched flow. Be sure not to select an existing resource from your own flow in the drop-down with the same name.