When designing flows, keep these flow feature considerations in mind. Also, some resources, elements, and screen components have more considerations that are described in their reference topics.
Required Editions
| View supported editions. |
- Flow Conditional Visibility Considerations
Before you set visibility for a screen component, understand the behavior of conditional visibility in flows. - Considerations for Flow Choice Component Default Values
Important behaviors and limitations to understand when setting default values for choice components in screen flows. - Flow Variable Considerations
Before you create a variable resource, understand the behavior of variables in flows. - Multi-Select Resource and Screen Field Considerations for Flows
Checkbox Group, Multi-Select Picklist, and Choice Lookup screen components let flow users select multiple choices. Before you start using these screen components, understand how they work in flows—both when you design the flow and when your users run it. - Paused Flow Interview Considerations
Before you design flows that contain one or more Wait elements, understand the behavior and guidelines. - Two-Column Flow Considerations
If your org has Lightning runtime enabled, you can control whether a flow displays in one column or two columns. Before you use this feature, understand how the flow layout currently behaves. - Considerations for Screen Component Styling
Before you change the width and vertical alignment of screen components, be mindful that the style settings aren't responsive to screen size. Also understand how to lay out components of different heights and when to use sections and blank Display Text components. - Schedule-Triggered Flow Limits and Considerations
A schedule-triggered flow starts at a specified time, runs on a specified frequency, and processes a batch of records. Review these considerations, limits, and special behaviors before creating or activating a schedule-triggered flow. - Record-Triggered Flow Considerations
A record-triggered autolaunched flow makes additional updates to the triggering record before or after it’s saved to the database. Understand the considerations and special behaviors of flows that make before- and after-save updates.