A Platform Administrator at Universal Containers has a screen flow that helps users create new leads. When Lead Source is "Search Engine", the administrator needs to require the user to choose a…

Question

Options

• AUse a conditional filter in the screen element to only show the Specific Search Engine field only
• BUse Assignment elements; one for when Lead Source is "Search Engine" and one for everything
• CCreate a picklist for Specific Search Engine, and set conditional visibility so that it is only shown
• DConfigure a picklist for Specific Search Engine, and use a validation rule to conditionally show

• A
  3% (1)
• C
  94% (34)
• D
  3% (1)

Explanation

In Flow Builder, the most efficient and user-friendly way to handle dynamic user interfaces is through Component Visibility. This feature allows an administrator to set logic on individual screen components (like a picklist) so they only appear when specific criteria are met. In this scenario, the administrator would select the "Specific Search Engine" picklist component within the Flow Screen and configure its visibility to show only when the "Lead Source" screen component equals "Search Engine." This provides a "clean" user experience where the form adapts in real-time to the user's input without requiring the user to navigate to a new screen or trigger a validation error. Validation rules (Option D) are reactive and only tell the user they made a mistake after they try to save, whereas conditional visibility is proactive. Option B is inefficient as it would require multiple screens and complex branching logic, whereas component visibility handles everything within a single screen element.

No community discussion yet for this question.