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

The most efficient and standard method to meet this requirement is by using the built-in Component Visibility feature on the screen element itself. Within the Flow Builder, any screen component, such as a picklist, can be configured to display only when specific conditions are met. The administrator can set the visibility of the 'Specific Search Engine' picklist to be dependent on the 'Lead Source' field's value being "Search Engine". This is a declarative setting on a single screen, requires no additional flow elements, and directly addresses both the show/hide and conditional requirement aspects of the task.

A. "Conditional filter" is not the correct terminology for screen component visibility. Filters are typically used in data elements like 'Get Records' to query for specific data, not to control UI display.

B. Assignment elements are used to assign values to variables, not to control the visibility of screen components. This approach would be inefficient, likely requiring a Decision element and separate screens.

D. Validation rules are used to enforce data integrity before a record is saved. They cannot dynamically show or hide a component on a flow screen; they only display an error message if criteria are not met.

1. Salesforce Help Documentation, "Flow Screen Input Component: Set Component Visibility": This document explicitly describes the feature. It states, "Define conditions to dynamically show or hide the component on the screen... When you set component visibility, the flow evaluates the conditions at run time. If the conditions are met, the component appears on the screen." This directly supports the use of conditional visibility as described in option C.

Source: Salesforce Help, Flow Builder Core Concepts, "Flow Screen Input Component".

2. Salesforce Help Documentation, "Flow Element: Screen": This document outlines the capabilities of the Screen element in a flow. It details how to add various components and configure their properties, including conditional visibility, which is the most direct way to handle the scenario.

Source: Salesforce Help, Flow Elements, "Flow Element: Screen".

3. Salesforce Help Documentation, "Validation Rules": This resource clarifies the purpose of validation rules. It states, "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record." This confirms that their function is data validation upon saving, not controlling UI visibility within a flow screen.

Source: Salesforce Help, Data Quality, "Validation Rules".