You are here:
Choose the Right Screen Component for Your Flow
Select a screen component based on the type of information that you want to show or collect from users in your flow.
Required Editions
Flow screen components add fields to collect or display data to your users in screen flows. Choosing the right component ensures a better user experience and helps you get the information you want. This guide organizes components by use case so you can select the best component for your needs.
Display Information to Users
Use these components to show information, but not collect user input.
- Display Text
-
Use when you want to provide instructions, explanations, or confirmation messages to users. The Display Text component supports rich text formatting, including bold, italic, lists, and links.
Example: Display a confirmation message after a user submits a case, such as "Thank you for submitting your case. Your case number is {!CaseNumber}."
- Display Image
-
Use when you want to show images, logos, or visual content. Images can help clarify instructions or enhance the user experience.
Example: Display your company logo at the top of a flow screen or show a diagram that explains a process.
- Message
-
Use when you want to display important notifications, alerts, or status messages to users. The Message component supports different types, such as informational, warning, error, and success messages.
Example: Display a warning message about required actions, show an error notification when validation fails, or confirm successful completion of a task.
Collect Unformatted Text
Use these components when you need users to enter unstructured text values.
- Text
-
Use when you need users to enter short text values up to 255 characters, such as names, titles, or brief descriptions.
Example: Collect a customer's company name or a product title.
- Long Text Area
-
Use when you need users to enter longer text with no character limit, such as comments, descriptions, or feedback.
Example: Collect detailed feedback about a service experience or a full case description.
- Password
-
Use when you need users to enter sensitive information that should be masked on screen.
Example: Collect a password or PIN for verification purposes.
Collect Formatted Text
Use these components when you need specific text formats, such as a phone number or email address.
-
Use when you need users to enter email addresses. The component validates that the input follows an email format.
Example: Collect a customer's email address for follow-up communications.
- Phone
-
Use when you need users to enter phone numbers.
Example: Collect a contact phone number for a lead or customer.
- URL
-
Use when you need users to enter website URLs or links.
Example: Collect a customer's company website or a link to documentation.
Collect Numeric Values
Use these components when you need users to enter numbers.
- Number
-
Use when you need users to enter numeric values, such as quantities, ages, or counts.
Example: Collect the quantity of items to order.
- Currency
-
Use when you need users to enter monetary amounts. The component formats the value as currency.
Example: Collect a budget amount, purchase price, or reimbursement request.
- Slider
-
Use when you want users to select a numeric value from a range by using a visual slider. Best for ratings, satisfaction scores, or preference levels.
Example: Collect a satisfaction rating from 1 to 10 or a priority level from 0 to 100.
Collect Dates and Times
Use these components when you need users to enter dates or times.
Collect Single-Choice Selections
Use these components when users must select one option from a set of choices.
- Picklist
-
Use when you have multiple options and want to save screen space with a dropdown menu. A picklist is ideal if you have many options.
Example: Have users select a product category, department, or priority level from a list.
- Radio Buttons
-
Use when you have a few options (from 2 to 5) and want all choices visible. Radio buttons make it clear that the user can select only one option.
Example: Have users select a preferred contact method (Email, Phone, Text) or choose a service tier (Basic, Standard, Premium).
Collect Multiple-Choice Selections
Use these components when users can select multiple options.
- Multi-Select Picklist
-
Use when you have multiple options for users to select from a dropdown.
Example: Have users select multiple product interests, languages spoken, or skills from a list.
- Checkbox Group
-
Use when you have a small to moderate number of options and want all choices visible. Users can select multiple checkboxes.
Example: Have users opt into multiple communication preferences or select applicable features.
Collect True or False Input
Use these components for Boolean choices.
- Checkbox
-
Use when you need a single yes or no or true or false choice, such as accepting terms or opting into something.
Example: Have users agree to terms and conditions, opt into a newsletter, or confirm that they understand a policy.
- Toggle
-
Use when you want a more visual representation of an active or inactive state.
Example: Have users enable or disable notifications, activate a feature, or switch between two states.
Collect Record Selections
Use these components so users can select existing records from your Salesforce org.
- Lookup
-
Use when you want users to search for and select existing records. The component provides a search interface similar to standard Salesforce lookups.
Example: Have users select an account, contact, or custom object record.
- Choice Lookup
-
Use when you want to provide a filtered list of records based on flow logic or when you need more control over which records appear.
Example: Have users select from a filtered list of accounts in a specific region or the contacts assigned to them.
- Data Table
-
Use when you want to display multiple records in a table format with columns so users can select one or more records. Best for comparing records or viewing details before selection.
Example: Display a list of open cases with details like case number, subject, and status, so users can select which cases to update.
- Kanban
-
Use when you want to display records in a visual board format with columns representing different stages or statuses. Users can view records organized by their current state and understand workflow progress at a glance.
Example: Display opportunities organized by stage (Prospecting, Qualification, Proposal, Closed Won) or cases organized by status (New, In Progress, Resolved).
Collect Multi-Field or Complex Input
Use these components for specific use cases.
- Address
-
Use when you want users to enter a complete address with street, city, state, postal code, and country fields.
Example: Collect a shipping address or business location.
- Name
-
Use when you want users to enter a person's name with separate fields for salutation, first name, middle name, and last name.
Example: Collect a full name for a new contact or lead.
- File Upload
-
Use when you want users to upload documents, images, or other files.
Example: Have users upload a resume, contract, invoice, or supporting documentation.
- Dependent Picklists
-
Use when you have two related picklists where the options in the second picklist depend on the selection in the first picklist.
Example: First, users select a product category, then they select a specific product from that category.
- Repeater
-
Use when you want users to enter information about multiple items of the same type on a single screen. Users can add or remove rows as needed.
Example: Have users add multiple attendees to an event, each with their own name and email fields, or collect information about multiple expense items.
- Choose a Lookup Option for a Flow Screen
Salesforce provides three ways for users to search for and select records on flow screens. Generally, use the Lookup component when you want users to search an unfiltered list of records. Use the Choice Lookup component when you want users to search a filtered list of records or static choices. Use a lookup record field when you want users to have the option to create a record from the lookup field. This table describes the differences between the three options.
