In a real-time business scenario, how would you decide between Before-Save and After-Save Record-Triggered Flows based on performance and related-record updates?
2 answers
Hi @Vinjamuri Teja The choice between Before-Save and After-Save Flow depends on the business requirement.
1. Before-Save Flow
- Use it to update fields on the same record.
- Runs before the record is saved.
- Faster and better for performance.
- Example: Automatically set Opportunity Priority based on Amount.
2. After-Save Flow
- Use it to create or update related records.
- Runs after the record is saved.
- Supports actions like sending emails and creating Tasks.
- Example: When an Opportunity becomes Closed Won, automatically create a follow-up Task.
Best Practice: Always prefer Before-Save Flow for same-record field updates and After-Save Flow for related-record updates or additional actions.
Hope this helps!
