If a flow requires the context of a record, which distribution options should be used?

When a flow needs the context of a record, using a Lightning record page or a flow action is essential because these options are specifically designed to work with record context. In a Lightning record page, the flow can access the record’s data directly because it is embedded within the page that shows all the relevant information about that specific record. This allows the flow to perform actions based on the current record's values, enabling more personalized and accurate processing.

Similarly, when utilizing a flow action, the flow can be invoked in the context of a particular record, allowing it to manipulate that record’s data or use its attributes directly in the flow logic. This tight integration is crucial for scenarios where actions need to directly relate to a specific record, such as updating fields or validating information against the record's properties.

Other options, like a Lightning community page, utility bar, or custom app page, may not provide the same direct access to a record's context, which is why they are not the ideal choices for flows that require such context. These alternatives may work for more general use cases where record-specific data is not crucial or where the flow's functionality is more about broader processes rather than direct record manipulation.