 After understanding lots of screen flow scenarios, it's time to move to another type of flow that is record trigger flow. So let's explore what record trigger flow is, then we'll see lots of use cases based on that. So if you click on new flow, so here we have an option that is record trigger flow. So it launches whenever a record is created, updated or deleted. This auto-launched flow runs in the background. So it is different with screen flow. Screen flow basically doesn't execute whenever you create, update or delete any record. But if you want to run your flow based on these operations so you can go for record trigger flow. So I just clicked on create. So in this case, we need to select the object first on which we want to run this record trigger flow. For example, I am selecting account. So whenever I am going to create, update and delete any account record, so this record trigger flow will run automatically. But here you can see we need to trigger the flow. So we need to choose this option. So we have separate options. If you are creating the record, then it will run if you select the first option. In second option, if you update your record, then only your flow will run. In third case, if you create or update either of the operation, if you perform, then your flow will run. And fourth is if you delete the record, then your flow will run. So based on the requirement, you can select any of the option. Then we have the set entry criteria. So you can also set the criteria. So for example, I am setting entry criteria as active equals yes. So if on the account record, active field is equals to yes, then only this flow will work. So suppose I'm deleting account record. So this option is selected. So on delete of account record, this flow will work. But if that account record active field is equals to yes, then only it will run. Now I'm just selecting a record is created. So here you can see, you see these two options. First option is optimize the flow form. So fast field update. So if you have selected these options, like record is created, if you select record is updated, then options are same. If you select this third option, then options are same. But you can see, like if I go for record is created, then two radio buttons are gone. If I select a record is updated, then these options are available, right? So one by one, I'm going to show you the differences. So if you select a record is created, then you will see these two options, fast field update and actions and related records. So fast field update means update fields on the record that triggers the flow to run. So the record which is triggering this flow to run. So if you want to do some changes in that record, so then you can select this fast field update. So this high performance flow runs before the record is saved to the database. This actions and related record means update any record and perform actions like send an email, this more flexible flow runs after the record is saved to the database. So if you want to perform actions or you want to do some operations on the related record. So for example, you created any account record and you want to do some operations on related contact or related opportunity. So in that case, you will be choosing this second option, right? Now if you select record is updated. So here you can see we have these two options. These two optimize the flow for both are same. Now here, when to run the flow for updated records? So first option says every time a record is updated and meets the condition requirement. So condition is active equals yes. So if you are updating any record, no matter which field you are updating, if active is equals to yes, then your flow will run. Now, another requirement is if and only, if only I change active field, then my flow should run. So you can go with second option. So it says only when a record is updated to meet the condition requirement. So if you're changing this active field from no or any other value to yes, then only your flow will work. So if you select the second option. So you can go with this help text as well. Perhaps you want the flow to run only when the triggering record is changed from not meeting the condition requirement to meeting the condition requirements. When that's the case, choose the second option. So now if I select creator or updated, so everything is same. And if I select record is deleted. So right now it shows before the record is deleted option, like after delete option is not available here. So the flow can access any record and perform actions before the triggering record is deleted from the database to create update or delete other records and create record, update record and delete records element to run your flow. The dollar record global variable contains the Salesforce record that launches the flow. So it is important when your flow launches. So through whatever record it is launching that records information will be available in this dollar record global variable. If a deleted record is later recovered, the flow's database changes and actions aren't rolled back. Also record recovery can't trigger a flow to run. If you require automation for when records are recovered from the recycle bin, consider using an apex after undelete trigger, right? So this is a note that you need to remember while using record trigger flow. So I clicked on done. So here at left hand side, you can see similar to a screen flow we can create these resources. Those I already explained in the beginning of the course. And if you want to have any element, so here you can see we have these options available. So these are the things, those are basic things that you need to know about record trigger flow. If you want to change the layout, we have these two options. So most of the features are similar to screen flow like settings related features are similar to screen flow. But here you will see like here, we can control the entry criteria of the record trigger flow which is not available in the screen flow. Okay, so through different, different use cases I will try to cover each and everything so that you understand record trigger flow properly.