To understand how to solve the same business use case using Process Builder and Salesforce Flow. Check out this article Getting Started with Process Builder – Part 8 (Auto Sync Accepted Quote with Opportunity).
Big Idea or Enduring Question:
Use multiple types of functionality to enhance the automation of your business processes.
After reading this blog post, the reader will be able to:
- Understand when to use before-save vs after-save record-triggered flow
- Use Flow to improve business process automation
- Use Before-save Record-Triggered Flow to create a record
- Use Before-save Record-Triggered Flow update records based on actions in a related record
Business Use case
Steve Cartwright is working as a System administrator at Universal Containers (UC). He has received a requirement from his manager to auto-update the Case Owner field with Asset’s owner if a case is created for an Asset record and anytime the Case asset field is changed.
Automation Champion Approach (I-do):
When it comes to Cases and Customer Support, organizations likely have a variety of automation that occurs. Beginning in Summer ‘20, flows are available to launch on record change. In addition to performing specific updates and actions, Salesforce Flow can initiate other Flows and Apex.
Before vs After Save Flow?
The before save flow is a trigger that is performed before an operation such as insert, update, delete. You can use such a flow to check or change values before data is updated or inserted in the database.
The after save flow is a trigger that is executed after an operation such as insert, update. You can use such a flow to update data in related objects or send an email alert.
Check out this article to understand why we are using after-save record-triggered flow for this scenario.