App Builder Platform-App-Builder Release Date

The feature that can be used to meet these requirements is two-step approval process. An approval process defines the steps and criteria for approving records. A two-step approval process requires two levels of approval before a record can be deleted. The app builder can configure an approval process for opportunities that requires sales reps to submit their delete requests for approval from their managers. Option A is incorrect because Process Builder with Submit for Approval action is not a valid feature, as Process Builder cannot submit records for approval. Option B is incorrect because Approval Process with a triggered Flow process is not a valid feature, as Approval Process cannot trigger Flow processes. Option C is incorrect because Approval Process with Time-Dependent Workflow action is not a valid feature, as Approval Process cannot use Time-Dependent Workflow actions.

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why not A:Formula fields cannot count related records.

Why not C:AppExchange is not required; Salesforce provides native functionality.

Why not D:A lookup only links records—it does not perform aggregation.

To allow users access to Flows, Salesforce offers multiple integration points:

A. Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.

C. Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.

Steps to set up these features:

For Quick Actions, navigate to Setup → Object Manager → select object → Buttons, Links, and Actions → New Action → Action Type (Flow).

For Flow Launcher, navigate to Lightning App Builder → select the page → drag the Flow component to the desired section of the page → configure it to launch the specific flow.

For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.