Salesforce Flow Radio Button Group Component

Salesforce Summer '26: implementing the Radio Button Group component in Screen Flows

The Summer '26 release adds a Radio Button Group component for Screen Flows. It shows single-choice options compactly, instead of a vertical list of radio circles or a dropdown picklist the user has to open first.

Understanding the Radio Button Group component

The Radio Button Group behaves the way standard radio buttons do: the user picks one option from a defined list. What changes is the presentation: each option renders as a button-like element rather than a radio circle on its own line. On desktop they sit side by side, which saves vertical space. On mobile they stack, so they are easier to tap.

You get a tidier screen and the same single-select behavior underneath.

Rationale for adoption

More teams are building internal apps and customer-facing screens in Flow, so the UX on those screens matters. A long vertical list adds friction, and so does a dropdown nobody can read until they open it. The Radio Button Group puts a short set of options on screen straight away, so people can scan and pick without extra clicks or scrolling.

Configuring the Radio Button Group

Drag the component onto the Screen element canvas in Flow Builder. If you have configured any other selection component, the settings will look familiar.

Choice Type is where you decide how the options get populated:

• Individual choices, where you define each option's label and value by hand. Fine for small, static lists.
• Picklist choice sets, which read values from an existing Salesforce picklist field so you are not maintaining the same list twice.
• Record choice sets, which build options from Salesforce records. Handy for a list of active accounts or contacts.
• Collection choice sets, which use a collection variable that already holds records, usually filled by an earlier Get Records element.

As a rule of thumb: use Choice for static options, Picklist Choice Set to reuse an existing picklist, Record Choice Set to select from records, and Collection Choice Set for records you have already retrieved.

The rest is what you would expect: mark the component required, set visibility rules, and note the multi-select option, although this component is meant for single selection the way traditional radio buttons are.

Ideal use cases

The component works best when someone picks one option from a short, clearly defined set. For example:

• Payment method: Credit Card, Bank Transfer, Invoice.
• Contract type: New, Renewal, Amendment.
• Action: Create, Update, Delete.
• Object: Lead, Account, Opportunity.
• Simple affirmations: Yes, No, Maybe.

Every option is visible at once, so people decide faster than they would with a dropdown.

Limitations and considerations

It does not fit everywhere.

• Long lists: dozens of options, or very lengthy labels, make the component hard to read and manage. For a large set of values a traditional picklist gives a better experience.
• User expectations: the button-like look can suggest that clicking an option does something. Selecting is only a choice; people still have to click something like 'Next' to move on.

Key takeaways

• The Summer '26 release adds a Radio Button Group component for Salesforce Screen Flows.
• It lays single-select options out compactly and horizontally.
• It saves screen space and helps people decide faster when the list of choices is short.
• Options can come from individual choices, picklist choice sets, record choice sets, or collection choice sets.
• It suits a limited number of clear, concise options.
• For very long lists or lengthy labels, stick with a traditional picklist.

You get a more polished flow screen without writing a custom component.