An administrator at a manufacturing company is designing an automation strategy for the custom Work Order object. When a Work Order record is updated, two business requirements must be satisfied:
1. Update fields on the triggering Work Order record itself before it is saved to the database, ensuring maximum performance without additional DML operations.
2. Execute a complex post-save business process that posts a notification to Chatter and updates related Asset records.
Which TWO automation design choices should the administrator implement to meet these requirements following Salesforce best practices? (Select TWO.)
- Configure a Record-Triggered Flow set to Fast Field Updates (Before-Save) for updating fields on the triggering Work Order record.Answer
- BConfigure an Actions and Related Records (After-Save) Record-Triggered Flow to perform field updates on the triggering Work Order record.
- Configure a Record-Triggered Flow set to Actions and Related Records (After-Save) to handle related Asset record updates and Chatter notifications.Answer
- DCreate a Roll-Up Summary field on the Asset object that points to the Work Order object via a Lookup relationship to summarize status changes.
Answer
The administrator should configure a Fast Field Updates (Before-Save) Record-Triggered Flow for same-record updates, and an Actions and Related Records (After-Save) Record-Triggered Flow to update related Asset records and send Chatter notifications.
Configuring a Fast Field Update flow ensures high-performance same-record updates prior to saving, while an Actions and Related Records flow provides the required execution context after record commit to update related records and trigger Chatter notifications.
Step-by-Step Solution
Key Concept
Selecting optimal Record-Triggered Flow trigger types based on timing (Before-Save vs. After-Save) and architectural constraints.