 Hello everyone, I am Sanjay Gupta, I welcome you on Sanjay Gupta Tech School. So today is day 29 of this Salesforce Learning Bootcamp and we will be understanding record triggered flow. So from last two days, we are understanding different scenarios based on record triggered flow. So today also I will be discussing a few flows with you and they will be having different requirements. And along with the session demonstration, I will be answering all your questions that you will be asking. So I'm just waiting for more folks to join and then we'll be starting. And I hope you are practicing all the scenarios which are related to flow. So always remember like flow is the future of low code automation because workflow rule and process builders are deprecated. So flow is the powerful tool and most of the tasks that those are related to process automation that we'll be doing with the help of flows in future. And you can see there are lots of flows available to perform different activities. So it is very much important if you want to become a good developer. So you should know proper knowledge of flows. And if you are not doing regular practice, so I just request you do proper practice. And I can see lots of people are discussing their doubts in the telegram group. So if you know the answers, please help them because I don't find enough time in my day to continuously watch all the problems related to telegram group. So if you have enough time, then please try to answer the questions so that that telegram group can become self-help group in real sense. Sumit, I'm good. I hope you all are good and doing good. So once again, welcome everybody. And I'm just starting with a session. So this is about me. So those who don't know about me, so you can go through with this slide. So I have lots of experience both in teaching and ID industry. And soon you will see like these numbers of certifications is same from past few months or years. So now this year I decided to do more certifications. So right now I'm learning few stuff and soon you will see a few more certifications will be added in the slide. Like many people are following these virtual learning best practices. So please continue and soon we'll be starting custom coding related sessions from next week. So in those sessions, these learning best practices are very much important because those sessions will be connected. And if you do regular practice, then only you can learn the programming. Okay. So today also I will be explaining the topic and then along with the demonstration, then I will take all the Q and A's. And today you will see a little change. I just renamed this group. So actually on telegram it is available with Sanjay Gupta Tech School. But I just want to consider it as self help group, right? So there are very less groups where people are actually helping each other. So I just want to make that group in such a way so that people are helping each other so that whenever you face any problem while practicing or doing any project work. So anytime you can just ask help from the people because this group is now having more than 700 members. And I can see lots of members are active and asking questions, answering questions. So that is good. So soon we'll be completing week eight. So like today I will be completing record triggered flow. And tomorrow we'll pick schedule triggered flow, auto launch flow and platform even triggered flow. And on Friday we'll be seeing flow related best practices. And from next week we're going to start Apex. Okay. So please share the channel name with everybody in your group and just want to have one request like please support. I can see less people are like connecting with this channel. I'm trying to give all the quality knowledge and more boot camps I'm planning. So please share the information with folks. So that more and more people can connect and get benefited. And in this channel everything will be available free of cost. So recorded as well as live sessions will be there throughout the year or in upcoming years as well. Okay. So we are here to learn record triggered flow scenarios. So here you can see today I have planned three different scenarios that will be having three different problems. So one by one I will be explaining and implementing them so that you can just understand how we can implement these scenarios. So first scenario you can say suppose on particular object you have record types and you want to implement some automation on that object and you want to play with record types in the flow. So here this is the requirement. So first let's understand the requirement and then we'll be implementing this together. And so I can see the few questions. So someone is suggesting when you're suggesting please add Salesforce or SFDC in the group name. Yeah Salesforce is already added in that group name. So I will take your suggestion actually Salesforce is added at the end. So I will just add it in the beginning. Okay. So Simran is asking for business scenario. So I think Simran if you go to that recruitment application so there I just added four requirements. So those are like that that project is basically real business scenario. So if you go and check so that is basically available there. So the requirement is first requirement we need to create two record types named as partner case and customer case on case object. And on creation of case we need to populate the total number of partner case as well as customer case on account object. So on account whatever case you are creating if it is customer case so customer case field will be having the counted value if it is partner case so partner case field will be having the counted value. So basically we need to create these two fields as well total customer case and total partner case. So first I will be creating two custom fields then I will be creating two record type on case and then we'll be implementing the flow. Okay. So jumping to the org. So here I'm going to object manager then moving to account and on account I will be creating two fields. So clicking on new so both fields will be of same data type. So here I'm going to select number as a data type. So from this list I'm going to select number clicking on next and if you have system along with you. So along with me you can also try and implement this scenario. So total customer cases. So here I'm just putting default value as zero. So this is important because we'll be fetching this field in the flow and will be adding some value into it. So make sure you set default value as zero for this field. Right. And I'm clicking on next visible to all the profiles and then next. So I'm just clicking on save and new because I need to create one more field. So I just clicked on save and new. So I'm going to create one more field of type number and clicking on next. So earlier I created total customer cases. Now I'm going to create total partner cases right. And here also default value I'm setting as zero. Then I'm clicking on next visible to all the profiles next and save. So this way on account object I created two fields. So if I search with total so here you can see total customer cases and total partner cases right. So first task is done that is to create fields. Now click on object manager and here what you need to do you need to search for case object and on case object we are going to create two record types. So I'm just going to create two record types and we'll be using the same page layout for both the record types. Okay so because we are not categorizing different page layouts as of now but I hope you know how we can create two page layouts and how we can assign them to record type so that I leave up to you. So I just want to record types so that two different type of records I can create on case. So I'm just quickly creating two case record types. So I just clicked on new. Okay so here you can see there is one additional requirement. A case record type must be associated with a support process. You currently do not have any active support processes. You must create a support process before creating a case record type. Okay so basically support process controls status field of case. Right so if you want to understand it in detail so if you go to study Salesforce administrator and lightning experience. So here you will find a video upon support process. So basically support process is used to control case status pick list. Right so this is important and you can just watch this number 31 video so that you can understand the complete process of the support process why we need and why to create it. Okay so I'm just going to create support process so I just clicked on here and I'm going to create it so case support process I'm creating and clicking on save. So basically it will be deciding like what status values you want to use so I'm just clicking on save. I'm not explaining what support process is because I just showed you this number 31 video if you watch you will be able to understand it. Right so again I'm coming here so the support process is created. Now if I go to object manager and again search for case. So now I will be able to create record type properly. Okay so I'm just clicking on new so that I can create a record type. So here record type label will be customer case. Then here we need to select the support process that we created right now that is case support process and here it is asking for profile so I'm selecting all the profiles and then clicking on next. So it will be asking for the page layout so I will be selecting the case page layout case layout and from bottom bottom right corner I'm clicking on save so this way or first record type will be created. So here you can see customer case record type is created. Okay again click on record type so here it is available now click on new. So I hope everybody those who are following this bootcamp knows how to create record type so now we need to create partner case record type. Again I'm selecting the same support process and clicking on active so that it will be available to use then make available click on next. Then again we need to select the layout and click on save. So this way I'm able to create two record types. Okay so two record types are created now if you want to create any case so you will see those two record types. So if I go to accounts open any account record and if I go to related so here you can see we have case related list if I click on new so you can see what the record types are available customer case partner case right so basic requirement is completed we created two fields on account and we created two record types on case. Okay so I hope till now everybody is good and this is very basic functionality that you all know so instead if you are implementing a flow so you should know basic configuration of the Salesforce so that you can just configure that and you can build a proper or appropriate flow so that your functionality will work properly. So now after creation of this basic requirement I'm just searching for flows. And I hope you are doing lots of practice so you all know how we can create the flow what is the use of flow trigger Explorer and these six options are available so we are doing second tomorrow we will be doing schedule auto-launched and platform event because these are very simple and very less used okay screen flow and record trigger flows are used more and like record triggered orchestration I won't be able to cover because I need more time to prepare content on this so maybe in upcoming weeks I will be dedicating some sessions on this include like while we will be learning about the apex programming okay so I need some time to prepare this so I will be skipping this part in this week but later on I will be completing this so right now I'm creating record triggered flow so I'm just selecting on create okay so here like we will be creating case so on creation of case we just need to count number of cases so a record is created now here we can apply the condition like whenever you are creating case so it should be related to account so account ID is null false so if your case is related to account then only it will be considered to be counted okay and I am just selecting actions and related record because we are creating case we are creating flow on case but we will be updating related account so that's why I am selecting actions and related record okay so I am just clicking on done so that I can proceed for further now what I need to do first of all I need to get account information so that the case which we are creating it will be related to particular account so I need to know on that account what is the current value of total part pattern case and total customer case right so I will be getting that so get records so I am going to get account and here I am searching for account so account ID should be equals to now you all know we have a global variable that is known as dollar record and this flow we are creating on case so whenever a new case record will be created so that case record information will be available under this dollar record variable and this dollar record will be having account ID populated so we need to select the second one because on first you can see we have arrow and this will be showing you the specific account fields but if you need account ID so you can select the second one so this account ID will be available on the case record if any account matches with that ID so that account we will be fetching so all the things you can leave as is because only one account you will be fetching because that ID is unique so one record will be available there so you can just select only the first record and automatically store all the fields and click on done right now we need to decide whether we created the case as a partner case or customer case right so here I am going to create a decision so we need to check case record type okay so it can be customer case or it can be partner case now I won't be able to implement this decision appropriately you must be thinking why so let's figure it out so if I select record then try to access a record type so here you can see we need record type ID right we don't have any record type name we need record type ID with which we can compare right so we have current case that is available under this record global variable through that we can have the record type ID but in this flow we don't have record type ID available right so we won't be able to compare it appropriately okay so unfortunately right now we are not able to complete this decision element so we need to click on cancel now before implementing decision what we need to do we need to get both the record type IDs right so we need to get customer case record type ID we need to get partner case record type ID okay then only we will be able to implement the decision element so now I am clicking on plus and searching for get records so we will be getting get customer case record type okay and record type is also an object so here what I selected record type because I just need to fetch record type information now here I am searching for name so I am populating developer name developer name is basically API name of the record type so how you can have that so you just need to go to object manager search for case and here you will find the record type so just open the customer case record type and here you will find record type name so this is basically developer name that is the unique name so just copy it and you can paste it here in the flow right so we are comparing record type particular record like developer name is equals to this customer case so that particular record will be identified and that will be available under this get customer case record type variable right click on done now again click on plus search for get records now we need to get partner case record type so again search for record type now here what you need to do just type developer name equals and again go to object manager and click on record types we have partner case so from here we will be selecting this record type name partner case so I am just copying it and here I am going to paste it right so everything you can leave as is and click on done so this way what we did the case which is related to particular account we just fetched that account information the case it can be related to customer case record type or it can be related to partner case so we just need to fetch both so we just fetched record type information okay now so what we need to do just click on plus and here we can apply the decision so in decision here what I can write check case record type okay so first we are going to check customer case so now if I search for record dollar record dollar record is basically our current record current case record that we created now we can just search for record type ID equals right so we can just have get this customer case record type and just search for ID so here you can see we have record type ID so this way if you get your record type record so through that record type record you can just have the ID of that particular record type and you can just try and compare it then click on plus and have one more outcome and here you can type partner case then again you can just search for record dot record type ID equals and here you can search for get partner case and then record type ID so this way we will be able to identify which type of case we actually created okay and then third we have default outcome that will be available so we created customer case outcome we created partner case outcome and then default case okay now I'm just clicking on done so this way you will be having this information okay so I hope you understood how I just implemented this decision element so through this decision decision element I will be able to identify which type of case I created actually okay now here I will need assignment element and I will be requiring a resource that I'm creating from here and I'm creating a variable so count customer case data type will be numbered and here like I am putting nothing clicking on done so I created count customer case I am creating one more variable and it will be count partner case and data type will be number and clicking on done now first of all I'm going to implement this customer case path so clicking on plus what happened I'm not able to click on plus okay so before I do refresh I'm just saving it so I'm saving it with case flow clicking on save so actually I'm not able to click on this plus sign don't know why so yeah here I'm able to plus but here I'm not so I just saved it and I'm just refreshing it so sometimes this canvas create some problem so what you can do what you can do just create your flow and if you are not getting you are not able to do something so before doing refresh just save it if you don't save and refresh everything will be removed automatically right so this is part of best practice like before refreshing a flow or like locking your computer laptop you just need to save your flow otherwise if you refresh without saving all the elements that you created after save those will be removed okay so I'm just clicking here now what I'm going to do I'm just having assignment so assign customer case value from account so we have count customer case equals now we have get account information right so on account we have that field customer case so whatever value of this customer case field will be that will be available here now what we need to do we need to count this customer case then you can add one into this right and you can just click on done now here we need to update record so we will be updating account okay then select the last option search for account object and here what you need to do field you will be searching ID it will be equals to record dot ID sorry record dot account ID okay now what field we need to update customer cases with which count customer cases so this is the variable that we created in the flow it will be incremented by one through that assignment and the updated value will go to this total customer case field and that field will be updated in the org and I'm clicking on done right so this way this first path is completed now we need to create another path so here again you will be searching for assignment element so here assigned partner case so search for count partner case equals then get account and from here you can search partner case field so whatever partner case field will be it will be assigned as is then you can just add one into this and click on done then again from here you can just search for update records so update account info select last option then search for account object then here you need to specify the condition so it should be ID then equals then here you can write dollar record dot ID no dollar record dot account ID okay and here you will be updating customer case sorry partner case equals to count partner case so this way our flow is implemented completely so the idea behind this example that why I demonstrated because I just wanted to show you if you want to compare record type in the flow so first of all you need to get those record types and record type is also an object so if you get it you will be having record type IDs and then you can use those record type IDs in the flow so I'm just clicking on save activating it now what will happen if I go here on the UI so on account like I am just refreshing it so I just refresh the account I'm moving to details and I will see yeah here you can see total customer case and partner cases are blank right now so if I go to related and try to create new case so I'm creating customer case filling the required information and click on save so I just created one customer case and going to details so here you can see total customer cases one if I go to related and try to create one more record of partner case and just fill the information that is actually required so if I just click on save so here under the details you will see total customer case one total partner case one right so this way you can see flow is working fine so you can also implement it and you can test it thoroughly so that you will be able to understand so the scenario is available in the exercise sheet I already demoed it in the session and session link I will be pasting okay so this is completed now I'm going to explain next example which is on delete like if you delete any opportunity okay not deleting we need to delete the opportunity when it stays is set to close lost right so through this scenario you will be understanding how we can delete and delete a record right so if I go to the flow and if I search for flows and click on new so I am selecting record triggered flow and on update it will be working so we need to update opportunity so I am selecting opportunity from here whenever a record is updated right here we need to set the entry criteria so condition here you need to select states name and if it is equals to close lost and from here you can select only when a record is updated to meet the condition then actions and related record click on done now from like if we click on plus so if you see this plus so almost everything we have completed we use stand alert we use action we use a flow assignment decision loop this collection sort and collection filter I just gave you some practice exercise so there I hope you might have used them then create record we used update record we use delete record we used now we are going to use delete record right so here you can just write delete opportunity right here it is asking which record you want to delete so I just want to specify the condition so OPP opportunity and here I am writing ID equals then the record which you updated its information will be available under dollar record so dollar record dot ID right so the record which you updated and if you updated it from any other states to close lost then that ID will be matched and that record will be deleted so I am just clicking on done now I am just going to save it so delete opportunity I am just clicking on save and activate right so now what will be happening whenever you will be updating any opportunity to close lost it will be deleted automatically so I am moving to an opportunity and I am going to open an opportunity record which is having different stage so here if in details you see so stages prospecting I am going to change it so I am making it close lost closed lost I am clicking on save and you will see an error message right so the requested resource doesn't exist why so because we just updated and in the background it is actually deleted and we are still on this record in edit form we are trying to view it right so it we cannot do that because in the background it is actually deleted so if you refresh the page you want to be able to see that record right so here you can see this error you will see if you click on this tab so that record is gone if you want to verify just go and search for recycle bin so under so I think there is some internet issue so screen just freezed okay so now recycle bin is opened and here you can see ACC 401 is the record that we deleted and it is showing deleted date and time as well you can just verify we just deleted it today and it is basically with PST time zone right so that's why it is showing this time okay so I hope you understood like how we can just delete a record through flow itself right so if you have any question related to this so you can just ask in the chat so I have one more flow to demonstrate once I will be completing that I will be picking all your question and answers right so I hope these two scenarios you are able to understand and I am sure you will be implementing them as well as a practice and here if you go so I just provided you a few more scenarios so two scenarios we completed third I'm going to demo and here you can see three more scenarios are available and in which this last one is very much important it is basically to create a login flow so whenever you log in into Salesforce all and if you want to apply some validation so that flow is basically known as login flow okay so I just have a recorded video for that so now it will be easy for you to understand so why I am applying this approach so some flows I am demonstrating so that we can discuss them and some I'm giving you so that you can implement and have a confidence like whether you will be able to understand them yourself or not right because Salesforce keeps on updating their products every quarter or you can say every four months so if after the training of after the boot camp if you see some new features so you should be able to understand them yourself right so this way now I'm going to explain number three now so number three says we need to apply validation rule based on existing record data right using record record flow so we are going to check duplicates actually okay so we can check duplicates through duplicate rule but if you want to do this through flow and validation rule so that is also possible so this is a work around for valid for duplicate rule so suppose you are not able to apply duplicate rule you want to you don't want to apply and maybe that object is not available there and under duplicate rule still you want to check duplicates so that you can do with the help of this scenario okay so what I'm going to do I'm going to explain you a scenario like suppose we are on account and if you are trying to create an account where account name already exist right so we need to prevent duplicate account creation so I will be comparing account name actually if account name already exist so I need to prevent duplicate account creation right so that I will be doing with this flow okay so I'm going to okay before creation of flow we need to do some more implementations so I'm going to object manager opening account and clicking on fields and relationships so first of all what I need to do I need to create new field and this field will be of type checkbox and I'm clicking on next here I'm writing a field label as duplicate found right so we'll be using this checkbox in the validation rule so if it is false then that validation rule won't fire if it is true then it will fire the validation rule and value of this field we will be setting through the flow okay so I am just creating duplicate found checkbox field on account then visible to all the profiles clicking on next and I'm clicking on save so this way I just created the field now I'm going to create the validation rule okay so I hope everybody who are following this bootcamp they know how to create a validation rule so prevent duplicate accounts right now here what we need to do we just need to insert that field that we created right now so its name is duplicate found so here it is I'm inserting it right so what validation rule does if the formula expression is true so you can see if the formula expression is true then display the text defined in the error message area right so if this field this is a checkbox field it will be true or false so if it is true then validation rule will fire if it is false validation rule won't fire okay so here I'm just going to show alert message so alert duplicate record found and I'm going to save it so this way I just created a duplicate rule okay so you need to do one thing two things first you need to create the first you need to create the checkbox field and then you need to create the validation rule okay now I'm just refreshing this page so here you can see this validation rule is created now I'm moving back to the account object okay and I'm just updating the sheet as well so I'm mentioning here what we are actually doing so okay so you need to validate duplicate account record creation later on you can just apply this duplicate like this flow for preventing duplicate candidates or duplicate contacts so maybe we will be adding this in the project as well so let me complete this flow implementation then I will be creating one requirement that we will be including in the project okay so now what we need to do go to home and here I'm going to search for flows clicking on new flow record triggered flow create now here I'm searching for account and when account record is created so I'm not selecting any requirement and here I'm selecting fast field update because right now what I need to do I need to just update the checkbox duplicate found that checkbox I need to update and that checkbox is basically available on account object only okay so I'm just selecting this fast field update and I'm just clicking on done now here what I need to do I'm just clicking on plus and I will be getting all the records which are having that name so get accounts so we just need to search account here now from here we need to match account name so if account name is equals to dollar record dot name so this dollar record will be having the account that we just created if that created account name matches with any of the existing account name so all those records we just need to fetch so here you need to select this all records option right we need to fetch all those records and I'm just clicking on done right now here I'm going to apply a decision so I'm going to check account size like how many accounts we fetched so if they that get account is null it means there is no account having the same name if it is not null it means there are records already available with the same account name so so if it is not null so how we will be identifying so you just need to use get accounts that element we created if it is is null false so if that get account is not null it means it is having a record or more than one records which are having same account name that we are trying to create okay so click on done and after that what you need to do you just need to update the triggering record so update account checkbox so duplicate found and we just need to set true here right so if we are setting this field as true so validation rule will fire and if validation will fire so you won't be able to create the record so I'm just clicking on done so this way this flow is created so we first what we did we just get all the account record existing account record basis on the name the name that is available in the newly created contact record if it is matches so we are getting all the contacts then we are checking whether that get contact is having contacts fetched or not so if it is not null then we will be just updating that duplicate found field as true so that our validation rule works okay so now I'm just going to save it then it will be duplicate check and I'm going to save it activating it now moving to UI so let's say I'm opening this account record and going to details okay I'm just copying this account name and I'm going to create new account with the same name right and here you can see we have this duplicate found checkbox it is false I'm clicking on save and okay review the fallen field we need to populate active as well because we have one more validation now I'm clicking on save so you can see one more validation is working and it is showing alert duplicate record found because we are trying to create a count record with the same name if I change this name and try to save it will be created okay so this way I hope you understood how we can create a flow to prevent duplicate records with the help of validation right now what I'm going to do I'm just going to implement this in our project so if you have not started implementing flow related use cases in the project or you have not completed the project so just complete the project and at the end you will find flow related scenarios so here I'm pasting it as well so first deactivate duplicate rules created on candidate object then apply validation rule based on existing record data using record triggered flow to validate duplicate candidate record creation based on email field so this will be our use case for this project so first you need to deactivate your duplicate rules duplicate rule that you created on candidate object then apply validation rule based on existing record data using record triggered flow to validate duplicate candidate records creation based on email field right so I just added this requirement so total five business requirements are available and all these five requirements are related to our project right so the project which we implemented as part of admin so here you can see development related tasks available and in real-time scenarios also in the projects these kind of requirements will be there and you just need to implement that in the existing project okay so this will be our ongoing project when we'll be doing apex trigger and test classes so I will be adding those related to the object model that we created okay so those who have not completed try to complete and there is one more scenario available so if you have implemented this approval process so you just need to create one more flow so after testing try to call the approval process through flow when a new position is created so in flow we have an action and through that action you can call the approval process so if I show you that thing okay so here we just need to select the flow actions and related record so here you will be having action and here you can search for approval process submit for approval so if you have created any approval process so that approval process ID you need to pass here and the record ID for which you are calling that approval process so it is very simple you can simply call the approval process through this okay so you have total six scenarios five are listed here and one is written above okay so these are the requirements that you can implement and these are related to flow so all these requirements which I demonstrated into this session so I hope you are able to understand these now I'm just moving to Q&A session so if you have any question you can just ask it in the chat okay so and like please share the world with everybody those who are waiting for apex related sessions so those I will be explaining really in detail and I will consider in mind like those who don't know anything about the programming so I will try to explain in such a way so that all the basics will be covered so there is one question why practicing the flow can we follow the finished steps versus how you did it semi I didn't get your question what you are actually trying to ask can you please elaborate Simran I guess now you can relate that project recruitment application is a real business time scenario and there you have six flow related requirement those you can implement so what is the difference between trigger and record triggered flow so tripti both are almost same some features are not available in record triggered flow those are available in trigger like we cannot do after delete we cannot do undelete operation in record triggered flow and if you want to implement any map so that is not very complex in record triggered flow and if you want to implement nested looping so that is very complex in record triggered flow if you compare it with trigger so around you are asking when we take assignment on flow is confusing so what is confusing so you can ask it here if you have confusion you can ask confusions in the telegram group so all the channels are available you just need to ask the doubts because in projects also requirement will be the similar so you will have confusion so you need to discuss and ask questions so Ketan is asking can we do scenario one with loop element no that is not required because yeah if you want to count so yeah we can do I think what you can do you can just get all the cases related to that account and then you can count them and you can update like we did yesterday yes yes Ketan so we can do scenario one with loop as well one is related to service cloud yes so case object is basically related to service cloud so you can consider it it is related to service cloud Gayathri is asking can we use a field to store the record type and use that field in the decision yes we can do so we are getting that information in the variable that is get record element and if you want to store that record type into a variable that is also possible so Praveen is asking what is the use of while condition apply only record that meet the condition while condition apply only ok so it means the field those you are using in the entry criteria if you are updating those field only then only your flow will work and we have another option that is every time so every time means if your condition is matching and any other field is getting updated still your flow will work so someone is asking if we work on case object so it means we worked on service cloud so no case object is just a part of that service cloud so service cloud is very huge so you need to know the features of service cloud then you can just say for example email to case for example WAP to case so these are some features auto response rule so these are some features that you need to understand I initially I just showed you support process so that is also part of service cloud so there are lots of features available so you need to learn those yes Arun we can use loop while checking duplicate records in the third scenario so what you can do you can just first fetch all those records then through loop you can just compare but that will be complicated so you you need to avoid that so Praveen I didn't use developer name equals to record type ID I gave the record type name if I show you again so if I show you the flow again so here I just used developer name equals and then here you can see developer name is available API name I didn't use record type ID okay so next is please add sales for study material link at video description link so yeah all the links are available in the description of the video so I think from there you can find Yadra so Simi you are asking can we follow the final step instead of the steps you took while practicing the final steps means I didn't get like if you follow whole steps then only you will be able to create the flow Simi is asking if you don't want to use .10 click tools then in that case you can go for flow no in that case you need to go for trigger if you want to use .10 click then we go for flow yes Praveen we can create formula variable as well in place of assignment that I demoed earlier like I think yesterday or maybe day before yesterday I showed you both you can create assignment and you can create formula variable as well okay Vinayak is asking can you explain fourth exercise in our exercise sheet yes so it is very simple in this fourth exercise what you need to do you need to create one flow that will be on account so when you will be creating account so if annual revenue is greater than 10,000 then you need to create one related opportunity you need to send email to account owner and you need to update the description field of account saying this so there are three actions you need to create opportunity related to that account you need to send email and you need to have update update record element if it is a false like account revenue is less than 10,000 then you just need to send email and you need to update the description you don't need to create a related opportunity right so here lots of things you need to use you will be using decision element you will be using create record element you will be using send email action you will be using update record element so all together all A and B will be implemented in the single flow yes in me so you can just follow the final steps as well and if you see any doubt you can just go through the whole recording can we avoid decision in third flow no we cannot avoid decision from third flow because if you don't apply the decision you won't be able to check how many records you get yes Praveen we can automate approval process instead of manual approval button and that requirement is available in our project as well you actually need to do that if you see here so in our project we need to automate our approval process through flow and how you can do that so for that you will be using the action so just click on plus you will find this action and here you need to search for approval process so here you have submit for approval so here you just need to pass the record ID so you can just pass dollar record dot ID here and here you need to pass approval process name or ID so just enable it and here you can just pass it so you can just create a resource and in that resource you can assign that approval process name or ID and you can use it so this is your own task that you need to do if you face any problem you can just ask me anytime or maybe in telegram group you can just paste the screenshot and I will guide you so Ritura as I don't think there is a limit of elements in the flow but whatever best practices are there so those I will be discussing in the Friday session so in Friday session you will be getting all the knowledge related to best practices okay so I think I just answered each and every question so just try to focus on the exercises I am dedicating all my time to create these exercises and I am just dedicating all my time so that this bootcamp help you to prepare all the topics properly and like this week all the admin and flow related sessions will be completed and from next week we will be starting apics related session so one more question is there from Kalpana when we use the data loader will the flow verify duplicate accounts yes so wherever we use data loader so all the automation that you implement that works yes it is for creation only not for update if you want to apply it for update so you can just select the option create or update both okay so I think there are no more questions so I just want to end this stream and tomorrow we will be having three different flow scenarios so we will be discussing then and on Friday we will be discussing about the best practices and from Monday we will be starting the apics sessions okay so just share this information with everybody those who want to learn about the flow scenarios thank you everyone see you tomorrow