When a user interacts with a button on a form, what flow type should be employed?

When a user interacts with a button on a form, the flow type that should be employed is the Screen flow. Screen flows are specifically designed to provide a user interface for interaction and guidance, allowing users to enter data, make selections, and navigate through a series of screens as they engage with the process.

In the context of a button that users actively click, a Screen flow facilitates this interaction effectively. It allows you to design a custom user experience by including various components like input fields, display text, choices, and navigation options. This direct user engagement is what makes Screen flows ideal for scenarios where user input is required in real time.

Other flow types, such as Record-Triggered flows, are automatically invoked by changes to records without direct user interaction and do not provide a user interface for input. Scheduled flows are designed to run at specified times but also do not require user interaction. Autolaunched flows are executed without any user interface and cannot take user input directly, making them unsuitable for scenarios requiring active user participation. Thus, for forms where a button is involved in user interaction, Screen flows are the clear choice.