An organization tracks product maintenance requests using a custom object named Warranty Claim. When a Warranty Claim status changes to 'Approved', two actions must occur automatically: a custom status timestamp field on the triggering Warranty Claim record must be updated, and a follow-up Task record must be created and assigned to the claim owner. Which TWO declarative automation solutions should a Salesforce administrator implement to fulfill these requirements efficiently?
- Configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) to update the status timestamp on the triggering Warranty Claim record.Answer
- Configure a Record-Triggered Flow optimized for Actions and Related Records (after-save) to create the follow-up Task record.Answer
- CConfigure a single Record-Triggered Flow optimized for Fast Field Updates (before-save) to both update the triggering record timestamp and create the related Task record.
- DCreate a Roll-Up Summary field on the parent Account object linked via a Lookup relationship to track and trigger Task creation for open warranty claims.
Answer
The administrator should use a Record-Triggered Flow set to Fast Field Updates (before-save) for updating fields on the triggering record itself, and a Record-Triggered Flow set to Actions and Related Records (after-save) for creating the related Task record.
Updating fields on the record that launched the flow is best handled by a before-save flow (Fast Field Updates) because it modifies the record in-memory prior to database save. Creating related records like Tasks requires an after-save flow (Actions and Related Records) because the system must finish committing the triggering record first.
Step-by-Step Solution
Key Concept
Selecting the correct trigger timing (before-save vs. after-save) in Flow Builder based on whether automation targets the triggering record or related records.