Hello folks, today we are going to discuss Record Triggered Flows in Salesforce. A record-triggered flow allows you to automatically perform actions in Salesforce behind the scenes, without any user interaction, once a record is created and/or updated, or deleted. In some regards, it’s similar to a workflow rule and process, which are triggered when a record is created and/or updated/deleted.
You can create a flow that updates another record, sends a notification, initiates a process, or maintains data consistency by triggering it from another record. The record-triggered flow allows you to fine-tune the timing of your automation to avoid conflicts and improve performance.
Also, check this: Custom Footer Buttons In Screen Flow
Key Highlights :
- Only when a record is created.
- Anytime a record is updated.
- Anytime a record is created or updated.
- Only when a record is deleted.
- Use for Fast Field Update, before commit in database flow can change the same object record information.
- Perform Related Records and Actions, we can manipulate related records and use multiple actions After Flow.
- Run Asynchronously used mainly break the transaction and runs in a new transaction.
- Scheduled Paths use to run the action after a specific time. We can set the time.
There are 4 ways in the Record Trigger Flow
1. Fast Field Update: Used for updating the same object record update before committing the transaction.
- The Before-save Flow is a trigger that is performed before an operation – such as an insert, update, delete, etc.
- Data can be checked or changed before being updated or inserted into the database using a Flow.
- In a Before-save, each record is not saved to the database again, so it is much faster.
You can check my full blog on Fast field by clicking below link
2. Related Records and Actions: This will call on after the DML operation and used to work on related records and call many actions like
- Creating, updating, or deleting other records
- Calling sub-flows
- Calling actions, such as sending email alerts or posting to Chatter, call invocable Apex class.
3. Run Asynchronously: Immediately after the record update that triggered the flow is complete. Used mainly to break the transaction and run a new transaction. Work the same as future methods. Executing more advanced scenarios like sending requests to external systems or performing other longer-running processes. Read full blog on click below link.
4. Scheduled Paths: Use to run the action after a specific time. In the future, after the trigger has fired, based on dates and times. Scheduling reminders or follow-ups based on dates in the record that triggered the flow, such as Close Date.
You can check my full blog on Scheduled Paths by clicking the below link