 Hello, hi everyone, I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So this is day 22 of Salesforce Learning Boot Camp and we are now moving to the next phase of this boot camp. So first phase we already completed that was related to Salesforce admin and all the sessions we discussed, practiced and followed by a project. So last week I hope you enjoyed implementation of the project which I shared with you and I did all the implementation in front of you and those implementations are recorded and available on YouTube. So if by any chance you missed the implementation, so please go ahead. So again, hi and welcome everyone and happy holy as well. Okay, so as you can see on the screen today, I'm going to start a new topic that is flow and flow is part of both. It is part of Salesforce admin, it is part of developer as well. So if you work as an admin, so maybe you maybe implementing flows or if you are working as a developer, then also you get a chance to build some flows. So in today's session, I will give you all the introduction and we'll discuss about the type of flows, like what all types are available and we will understand the flow builder flow builder is basically a tool through which we implement the flows. So we will be discussing that, right? So I know like many people are joining this boot camp in the middle, like they were waiting for the development related sessions. So if you don't know about me, so this slide will tell you about me. So I have total 16 plus years of experience and I have both education and IT industry experience. Like I got enough Salesforce knowledge and due to my education experience, I am sharing that knowledge with you and I'm helping students, freshers and professionals to ramp their career in Salesforce ecosystem. So whenever anybody reaches out to me, so I just try to help them how they can ramp their self. So like these are virtual learning best practices that you need to follow. So this I already shared with you and now these are very much important because now onwards week by week topics will be related. So this week and next week, we will be discussing about the flows. So everything will be related. So you need to focus on the live sessions, take proper notes, write down all the doubts and you can ask doubts at the end of the session because I am giving 30 to 40 minutes for doubt discussion in every session and don't miss any session because all the parts are connected and if you miss, then recordings are available. So just go through like whatever I discussed and for each session, I am preparing practice questions as well. So if you practice them, you will be able to understand things properly and if you follow everything, so you will become like efficient so that you, you can get a job in Salesforce ecosystem. So like learning everything in detail is very much important. So this is our session timeline. So first I will be explaining all the topic and we'll do some demonstration. So it will take 50 to 60 minutes and then we'll discuss Q&A 30 to 40 minutes, right? And if you have any doubt, you can ask through YouTube comments. You can reach out to Telegram group or Instagram. So in Telegram, I can see many people are helping each other and whenever I get time, I also try to answer the questions, but it is driven by you. So please try to involve as much as you can. So this is the new timeline. So now we will be following this timeline. So in past, we completed total six weeks and here you can see total six weeks timeline is also available with you and this is again tentative timeline if like there is a requirement to extend particular week for particular topics. So I will be the organizing this timeline. So right now, this week and next week are dedicated for flows and then in week nine, we'll see apex implementation, then trigger, then apex test classes and then as an asynchronous apex, right? So these whole six weeks will be related to backend development, right? So all these tools are for development purpose. So many folks were asking like when I will be starting development related sessions. So I think today I'm going to start these sessions for you. And as you all know, all the sessions are totally free. You don't need to pay any amount for that. And in each session, I'm discussing topics in detail and doing Q&A as well, right? So I hope this I'm doing for like, I hope this is helping you and I'm doing this for the community. And like if you are having this opportunity, so to like, you can utilize this and go with me day by day, week by week, you will be having enough knowledge of Salesforce, right? I'm trying to share each and every detail with you. And if you are following this bootcamp from the beginning, so under your LinkedIn profile as an experience, you can add it and all the skills, those you are learning, you can showcase them in your resume and you can also showcase the project, right? And that admin project, which we discussed last week, the same project I will be modifying so that it will be having development related stuff as well, right? So if you see like I already started modifying this. So here I already mentioned like the same project will be for admin as well as development. Because for development, we again need a base, base for like objects, records, fields. So that we already built. So I already started modifying this object relationship. So I added two more object skill and candidate skill object. So related to this, I will be mentioning few requirements as we proceed with the sessions, right? So this complete project you can mention in your CV and like it will be having all the development related stuff, whatever we will discuss. So first I will modify this for flow related tasks, and then I will be modifying it for apex related tasks, and then I will be modifying it for LWC related tasks, right? So I hope now you will be having a complete end to end project with you, which will be covering all admin and development related stuff, right? And I'm dedicated so that you can become successful. So I just mentioned this tagline with my brand name like Sanjay Gupta Tech School. So your successor is our mission. Why are? Because right now I'm delivering this session, but soon there will be lots of people will be involved and they will be delivering more boot camps for different topics. So you can share this information with everybody, whether they are college students or like doing graduation, whether they are freshers, whether they are professionals. So the person who is related to IT or non-IT and they want to learn IT related stuff. So you can just share this channel with them. So along with Salesforce, I'm planning to do more boot camps related to VAP development, related to cybersecurity, related to DevOps, related to data science. So all these boot camps I'm just preparing with other consultants, and soon you will hear from me like when those boot camps will be starting, right? Okay. So I just explained everything related to this boot camp and my organization. Now let's jump on to the topic. So in today's session, we will be getting familiar like what exactly lightning flow is. So you might have heard like flow is very powerful tool which is available in Salesforce. So first of all, we need to understand this. So basically flow provides declarative process automation. So in Salesforce, there are two types of development. One is declarative development and one is custom development. So if we talk about declarative development, so declarative development is also known as low code development where you don't need to write any line of code. Until you can do development and you can implement the processes which will be working automatically, right? So this is basically known as declarative automation or declarative development. So lightning flow provides this point and click automation tool that is flow builder. Okay. So lightning flow is a product. Lightning flow is the name of the product and process builder and flow builder are name of the tools. Okay. So if you talk about the product, so it is lightning flow. If you talk about the tool with which you will be able to implement the flow, so that is flow builder. So as I hope many of you know, like workflow and process builders are getting retired. They are deprecated now. So we don't need to learn workflow rules and process builders anymore. We can directly build all the declarative automations with the help of flows, right? So you need to use flow builder to create flows, right? So this you need to keep in mind. And in this session, I will be comparing flow with workflow rule and process builder. So as a Salesforce consultant, developer, QA or admin, if you are associated with Salesforce ecosystem. So you should know the prior products as well, right? So if you are doing your job and someone says like workflow rule and process builders are being deprecated, so you should know what they used to do. So I have prepared some slides where I will be doing comparison between them so that you will be having brief idea. Okay. So moving to next slide. So here heading says when to use. So you should know when to use flows, right? So first point says automate a guided visual experience, right? So what does it mean? So let me take a simple example. For example, if I want to take feedback of this bootcamp from you and that feedback I want to design in such a way so that there will be lots of questions and some options will be available and you will be having different, different steps through which you will be providing the feedback, right? So you will be having a guided path. Like you will be having a UI where you will see some questions and their options. Then you will fill the details and click on next. Then second question will appear and you will see some options. Then you will select an option and go further. So this kind of guided experience if you want to create so that we can do with the help of screen flow. So screen flow is first type of flow, right? Through which you can create UI. Now what is UI? UI means user interface. So if you want to create a user interface where you can receive some input from the user, so that type of flow is known as screen flow, right? Now second is if you want to build complex functionality which can run automatically in the background, right? Which can run automatically in the background. So we already saw some processes like that. So we created formula field. We created roll up summary. So those are also some functionalities which works automatically in the background. So if you are creating any record, if you are updating any record, if you are deleting any record. So on that event, if you want to run anything in the background for that particular record, so we use record triggered flow, right? So we have second type of flow that is record triggered flow and it basically runs in the background. You won't see its execution in the front end. It will be running in the background. Then we have schedule triggered flow. We have auto launch flow, right? So here four types of flow are listed and in upcoming slides, I will be discussing them in detail as well with few more points. And next we have need to call flow from apex or lightning components. So these are broad requirements with which you can say why to use flow, right? So if you want to create a visual experience to frame some UI, if you want to run some process in the background automatically, or if you want to run some process that you need to call through apex or lightning component. So for accomplishing these requirements, you can implement flows, right? Now if we talk about flow elements, so these are some elements those you will see under flow builder, right? So these are somewhere related to programming. But if you have fear of programming, like you don't want to write any code, you don't like writing code, then flow is best for you because here you don't need to write any programming. You can simply create logics through point and click and you don't need to remember any syntax. Everything will be available on the UI. So all these are related to that. So first we have interaction. So you will find screens. You will find actions. You can create some flows. Then we have logic. For logic we have assignment, decision, loop. Then we can do sorting and we can apply filters on collection. Collection means where you have more than one records stored together, right? Then we have data. So it says create record, update record, get record, delete record. So these operations we can do with flows. So I will be explaining scenarios in these sessions and in each scenario we will be using a few of these elements, not all in one scenario, but in different, different scenarios you will see like I will be using these elements, okay? And when I will take you to flow builder, so I will show you like how these elements are available there, okay? So these are divided heading wise like interaction, logic and data, right? So this way you can remember and in interview also interviewer can ask like what operations we can do in flow. So these operations you can just remember and you can name them. Then what all resources we can create in flows. So we can create some variables, constants, formula. So here also we can create formula. Then we have text template choice, record choice set, pick list choice set and stage. So these also I will be creating when I will be demonstrating the use cases or scenarios, right? So we need to work through two things. One is element that is available in the previous slide and second is resources. So these two things are very much important if we talk about flow builder, right? So first one is elements and second one is resources. So this is a simple UI of flow builder. So we'll be jumping to flow builder and then we'll experience it. So I just placed a screenshot, right? So we'll experience it. Then next, whenever you create any flow, you need to activate it so that it works. If you don't want to execute it, so you can deactivate it as well. So you don't need to delete it. You can just deactivate so that it won't work, right? So activation and deactivation is available. And if you are having any question in between the sessions, so please note it down. And when I will finish all the explanations, so you can just raise your questions. So now let's take a look on the types of flow. So before implementation, in today's session, you will be having all the required knowledge prior to implement any flow, right? So if time permits, then I will be implementing first scenario in today's session. Otherwise, scenario implementation, I will be starting from tomorrow because it will take a lot of time. So these are five types of flow available in Salesforce that you need to remember. And this is most common interview question. So we have screen flow, we have record triggered flow, schedule triggered flow, platform even triggered flow, and auto launched flow, right? Now, what is screen flow? So if someone asks you what is screen flow, so you can say it guides user through a business process, right? You can add on like, we can create some UI through screen flow and those UIs will be interactive. So through those UIs, user can provide some input and basis on that input, we can do some process in between the flow, right? So screen flow is the only flow which can interact with the user. Other flows runs in the background only. And interviewer can also ask like where it can be placed or from where it can be launched. So we can place it on lightning page. So we have three types of lightning pages. We have app page, we have home page and we have record page. So on any of the lightning page, we can place screen flow. Then in Salesforce, we have experience sites. So through experience cloud, you can create experience sites, right? So right now, I won't be able to explain this because it is different cloud. If you have a little bit knowledge of experience cloud, so you will be able to understand. So in Salesforce, we have a separate cloud that is experience cloud where we build sites which are other than your Salesforce actual org, right? So through that experience site, you can also launch your flows. And third is quick action. So quick action, we already discussed. Like you can create actions as global action or object specific action. So if you want to place your flows on quick action, so you can do that. And we have other options as well like nowadays we can place our screen flow with lightning web component as well, okay? So this way you can just connect your screen flow with other features. Those are available. And I can see Vamshi saying one more new flow launched recently. Yes, so that is six type of flow and that is different. So we'll discuss that as well. But that we'll discuss after understanding all these five flows. That's why in today's session I didn't include that, okay? But later on I will be including that as well. So second type is record triggered flow. So this is very important because this record trigger flow actually replaced your workflow rule and process builder. And this also you should know, right? When workflow rule and process builder were available. So at the time screen flow was available, but record triggered flow was not available. When record trigger flow launched, so it basically can launch whenever you create, update or delete any record, right? And all these operations we used to do through workflow rule and process builder. And in workflow rule and process builder, we used to run them on record creation and updation only. They cannot launch on record deletion. But in record triggered flow, we can do that as well. And this auto launch flow runs in the background. So this also you need to remember, like which flow actually is the replacement of workflow rule and process builder. So that is record triggered flow. And whenever you create, update or delete any record, so this flow launch, okay? So after discussion of two types, screen flow and record triggered flow, we have third type that is scheduled triggered flow. It is also important. So for example, if you are not creating any new record, if you are not updating any existing record, if you are not deleting any record, it means you are doing nothing on any record. Still you want to run a process on particular bunch of record. So that is basically scheduled triggered flow. So it launches a space at a specified time and frequency for each record in a batch, right? So this auto launch flow also runs in the background. So if you want to query your existing data, if you want to fetch your existing records and at certain time, date and time or frequency, if you want to perform certain operation. So for that purpose, we basically use scheduled triggered flow. So if I take any real time example, so nowadays we are totally dependent on mobile data. And in many of the countries, we have data plans like companies refill your data on daily basis. And they run a batch at midnight. So at midnight, your data, whatever capacity you have, if you have 1 GB, 1.5 GB or 2 GB. So according to your data package, your data will be refilled automatically at midnight on daily basis. So that is the example you can relate with scheduled triggered flow. So on daily basis, on midnight, on all the existing records that event or that process is executing. So that is basically happening with the help of scheduled triggered flow. So not exactly that is happening through that. But in Salesforce, if you want to implement same kind of process, so you can implement that with the help of scheduled triggered flow, right? So if user is not doing anything, still it will run in the background. And it will affect lots of records which are meeting the requirement of the flow, right? So that's why it is also important. Then next we have platform event triggered flow. So it launches when a platform event message is received. So a platform event basically we generate through code. So if platform event message is received, then this flow will be launched. So this is specific to Salesforce. And when we'll be discussing this in detail, so I will give you a demo like how it will work. So then you will be able to understand. And it will launch automatically and it will run in the background and perform certain operation, right? And it is used very less. Only when platform event message is received, then only it will launch. So it is rarely used, but screen flow, record triggered flow and schedule triggered flow are used mainly. And last is auto-launched flow. So before record triggered flow in Flow Builder, we used to have auto-launched flow. And auto-launched flow is a flow that you need to call through any external feature like Apex, process means process builder. Then if you have REST API, so through that also you can call it. So actually, if you have created a process and if you want to call that process through another tool, like Apex or process builder or any other tool, then that flow is basically known as auto-launched flow. So it is also nowadays very rarely used because we have record triggered flow. That is running automatically, but still if you want to run a declarative process through Apex, then you can just utilize this functionality, right? So first three are mainly used and REST two are very rarely used. Okay, so these are five flows. Those are available and one is also available recently. So that I will be discussing in the separate session. So now let's discuss the difference between process builder, flow builder, workflow rule and approval process. So approval process you already implemented in the admin sessions and it was available in the project as well. So I didn't explain that. I just asked you like it will be self-implement, self-practice topic. So I hope you might have implemented if not then implement. It is important topic and flow builder. We will be learning in this week and we have workflow and process builder as well, right? Those are deprecated. Okay, so if I take you here in the org, so if you want to see like how they look like. So if I search for workflow rule, so here this option is available. And if I click on workflow rule, so here you will see this option. If I click on continue, so here new rule option is available, but see this message. So flow builder is the future of low code automation, right? So the word which I use for declarative development. So you can just say it as low code automation as well. Low code automation like less code and more point and click. So you can use it to create most of the automation found in workflow rules. Start using flows today. Okay, so just click on the second button, create a flow builder because it is important. And if in your org, this button is available. So you can create, but that doesn't make any sense because in future like this option won't be available in the orgs, right? Now you might be thinking like what will happen with the existing workflow rules. So here workflow rule migration tool is also available. So here you can see we have this option migrate to flow. If you search for this option and click on it migrate to flow. So here you can see we have this UI migrate to flow with ease. So Salesforce itself provided a tool which will convert your workflow rules into flows, right? So here you can see this message. So Salesforce is saying we are retiring workflow rules and processes in the near future to ease your transition to flow. We created a tool to convert your existing automation to flows. If you click on this link, tell me more so you will see more details. Then learn about learn more about what workflow rules and processes the migrate to flow tool can convert also learn manual conversion methods for your edge cases. So if you click on these links, so you will get to know more details, right? So soon these won't be available. These features won't be available in the org. So it is suggested not to create workflow rules and process builder instead go with flows. So flow is the future of process automation, low code development. So here also you can see the top line go with the flow with flow builder, the future of low code automation. You can do everything you do with process builder and more Salesforce plans to retire process builder and recommends building automation in flow builder, right? So I think this makes sense and here you can see these options are available. Try flow builder and use migrate to flow tool. Okay. So I hope this makes sense that not to use workflow rule and process builder instead use flow builder. Okay, but you should know the differences like what we can do with workflow, what we can do with process builder, what we can do with flow builder and what we can do with approvals. So I have created this comparison table. So here four columns are available and like through heading you will be able to identify like which tool we are talking about and on left. You can see the like on the basis of what we are comparing. So first is complexity. So in process builder, you can have multiple if then statement like you can apply more than one conditions in process builder in flow builder. You can go beyond that as well. You can apply n number of conditions in flow builder. Then in workflow, we can apply only single if then like only one condition we can apply and basis on that it will work and same happens with approval process. Then we have visual designers. So visual designer is available with process builder and flow builder not with workflow and approvals. Then time support, sorry supports time based actions. So these are supported with these three process builder workflow and flow builder not not available with approvals. Then user interaction is supported with flow only and that too through screen flow. So through screen flow, we are able to interact with user and we can receive some data and basis on that your results will be available. Yeah. So I can see Ajit is saying a workflow and process builder is retired. Yeah. So I also said that but in some of the org, they those options are still available. So you can say like they they are in the process of retiring or they are retired. So for you, you can consider they are retired and don't think about them, but for your knowledge, I'm doing this comparison so that you know brief about them, but we will be learning flow builder only and approvals. We already implemented approval processes. So next is when they start. So process builder whenever record changes, whenever it is invoked by another process. So in process builder, we can apply nesting as well like one process can call another and platform even message is received. So now why this comparison is important because these everything whatever it is written here, this everything you can do with the help of flow. So we have record triggered flow. We have platform even triggered flow. So those will be replacing all these functionalities. Right. Then we have a flow builder like whenever user click on button or link. So through this, your screen flow will be called then you can access screen flow through lightning page experience site. We have page custom tabs. So this we already discussed then user accesses item in the utility bar, right? So utility bar will be available at the bottom. So if we see this bottom, so here at the bottom utility bars are basically available, right? So if I open existing application, so I think there we added utility bar. Yeah, so here you can see we have chatter feed. So this is basically utility bar. So from here, if you want to launch your flow, so that is also possible and you can launch your screen flow from here. So under utility bar also you will be able to place your flow. Then whenever process starts, it means whenever like you are creating record, you are updating record or you are deleting the record, right? And in flow, you can have sub flows as well. So you can call one flow through another flow. So that is also known as process starts. Then apex is called. So through apex, you can call your flows and record created updated or deleted that we already discussed. So this is the important thing that you need to remember like on which action your flow will be initiated. Then workflow basically workflow rule basically calls whenever our record is changed. So changed means insert or update only two options. Then for approvals, we have user clicks button or action or link. So like if you click any button, so through that button maybe your flow is calling and internally flow is calling the approval process. So that can happen. So through flows, we can call approval process, right? So if I take you to the project, so in project also here, I just mentioned one point after approval process. So I just want to show you and when you will be learning flows, so you will be able to do that. So this is our approval process and here you can see one note is available after testing this approval process manually, try to call the above approval process through flow when a new position is created, right? So we can call our approval processes through flows and this use case later on, I will shift into flow exercise. So we will be doing same as part of project, right? So like at that time you will need that approval process. So those who have not implemented this project, so you need to implement this project because this project I will be extending for other features. So things will be dependent. So to understand development related tasks, those are part of this project. So you need to just implement all the base items. Those are listed there, okay? Then in approvals, we have second point, which is process or flow starts that includes a submit for approval action. So this I think you already used like if you click on submit for approval, your approval process initiates and apex is called so through apex also you can call your approval processes, right? Then next is difference based on supported actions. So let's discuss these as well. So this is also very easy. So again, we have four headings and on left we have the feature with basis on that we are going to compare. So first is call apex code. So a process builder can call apex code, flow builder can call apex code, but workflow and approvals cannot. So what does it mean? Through process builder and flow builder, we can call apex code, right? Then we have create record. So we can create new records through process builder through flow builder and through workflow and approvals we can create only task. So task is basically an object and we can create task record only not other object records. We cannot create through workflow and approvals, but with process builder and flow we can then invoke sub processes. So that we can do again with process builder and flow. We cannot do them through workflow and approvals. So sub processes means if you have created to process or to flow, so one flow can be called by another. So that we can do with the help of sub process or sub flows. So in process builder it is known as sub process and in flow it is known as sub flow. Then we have delete records. So that feature is available with flow builder only. So through flow, if you want to delete any existing record so that we can do through flow only, right? Then again, we have some more options. So if you want to launch a flow, so you can launch a flow through process you can launch it through flow builder, but not from approval and workflow post to chatter. So I hope everybody knows chatter. So we use chatter for feed tracking. So if you want to post something on chatter automatically, so that can be done through process builder and flow builder, but not through workflow and approvals send email. So yes, through every feature, we can send emails outbound messages. So we can send it through flow earlier. This feature was not available with flow. It was available with workflow only, but last year Salesforce added that feature with flow. So when that feature added so after that Salesforce decided like let's retire workflow rule because now flow can do everything, right? So workflow and process builder all the features can be implemented through flow builder. That's why they are retired then submit for approval. We can do through process and flow, not from workflow and approvals then update field. So if you are if you want to update any field of any record. So here in process builder, we can update any record whether it is parent or child in flow as well in workflow. We can update the record and the record means which initiated the workflow rule and its parent. We cannot update the child records and here in approvals also we can have the same. Then we have a feature custom notification. So notification comes under bell icon. If I take you here, so this is the place where notifications comes if I click on this bell icon. So here you can see notifications are available. So if you want to send some notifications, so for that you need to create custom notification so that we can do through process builder and flow builder not from workflow and approvals then through like quick action. We can perform through process builder and flow builder quick. We can perform through these two only not from workflow and approvals. Okay. So they these are the differences between these four tools that I discussed with you. Okay. Satya is asking when process builder is getting retired. Then why do we use these options like call epics, create record, delete code. So basically when process builder was available to use then those features were available. So I just compared them. I just compared them so that you know what process builder used to do right now it is retired. So you won't be able to implement processes through process builder and you will be able to do those things through your flow. Okay. Ajit is saying that word not visible clearly. So I think like if you watch the recording you will be able to otherwise I would make sure in future slides. I won't use red color so that it like different color will be visible to you. Okay. Now I'm going to quickly show you a flow builder demo and then I will like ask you so that you can ask questions related to this session. Okay. So let's jump to flow builder now. So in today's session we just we are just discussing about the introduction of flow like how why we use it like how it is different with other tools. What are the features available with flows? What types are available? Right. So that you should know the basics of flows. Now if you want to create a flow. So here under set up home you need to search for flow and here flows options will be available. So you need to click on flows and here you will find this UI where list of flows will be available. So in your org you will find lots of flow prebuilt. So whenever you create any developer addition or so sales force provides you some flows as part of manage package. So they are provided by default. Right. And few are active fewer and inactive. So these are provided by default. So don't modify them. You can just open and see what is happening there but don't change the functionality that is available there because we will be implementing new flows. So here we have two buttons. One is flow trigger explorer. So this we will be discussing later on it is basically related to record trigger flow. So when we'll be implementing that I will explain it and this is the button that I'm going to hit new flow. So it will open a new tab where a UI will be available which will show you the options. So we already discussed screen flow record triggered flow scheduled triggered flow platform even triggered flow auto launched flow and sixth one is record triggered orchestration right. So it launches when a record is created or updated and orchestration lets you create a multi step multi user process right. So I also like used it a little bit. So I also need to explore. So like I think we will take this in next week. So till then I will do some hands on and we'll identify some use cases so that we can understand it together. Okay. So other five use cases are ready so that I will be explaining in the beginning and then we'll see record trigger orchestration as well. Okay. Now I'm clicking on the screen flow and also notice that if you click on any of the type so you will see different items under flow builder. So I will compare that as well. So I'm just clicking on create. So right now we are on screen flow. So this is actually flow builder. So here you can see we have a flow builder and we will be creating screen flow. So here different buttons are available. So this is the canvas where you will be creating the flow. So this is screen flow. Let me just click on new flow again and let me select record flow and I'm clicking on create. So here you will see different UI. So by default it is asking you to select an object. So let's say I'm selecting account and here you can see it will trigger whenever record is created, updated, created or updated or deleted. Then you can enter entry condition as well. Right. So these options are available and I'm clicking on done. So it is looking different. But the top bar. It is same. If you see the top bar here options are same in record trigger flow. If I take you to screen flow here also options are same few buttons are different like view test is available here. It is not available here. So this depends on the type of flow that you are using. Okay. So the main purpose of explaining flow builder is this like so that I can explain you the use of each and every button which is available on top. Okay. So first of all, if you see this button, so this button if you click so it will show you the toolbox where if you click on new resource, so you will see resource types. So if you remember in the beginning, I told you you will be using two things. One is the element. One is the element and second is the resources. So here you will see all the resources variable constant formula text template choice. So whatever you want to create those resources, you will be able to create like this. Okay. So that option is available at top left corner. If you click and it is a toggle button. If you click again, so it will disappear. Right. Now you might be thinking from where we can see the elements. So if you click on this plus. So here you can see the elements. Okay. So we have screen actions of flow. So let me show you those slides which I explained earlier. So if I take you back. So here you can see all the resources are listed and here you can see all the elements are listed. So this I already explained to you, right? Not in detail, but I just told you with the help of these elements and resources, you will be able to perform some operations. So here we have logical operations, logical elements. Here we have data elements. Okay. Now here we have this select element. So if you have created any element from this flow. So if you want to select that element, so we will be creating lots of element. So if you want to select any element, so this option will be useful. So it is clear by this name like select element. So we will be using them. Then these two options are for undo and redo. These two options are for undo and redo. Okay. And this is for setting. So if I say, okay, let me just create a simple. Screen here. So I'm just creating a test screen. So this I'm creating for test purpose, right? I'm not going to explain it. I will be explaining this tomorrow in tomorrow session. We will learn how we can create these elements. So I just created it for demo purpose, right? So as I created this so you can see here we have the resources. So if you create any resource here, so that will be listed here automatically. If you create new resource from here, so that also will be listed here. So if I create a variable from here, variable and let's say nums data type, I am picking number and I'm clicking on done. So as I created that so you can see here that variable is available. So whatever resource you will be creating that list you will find here. Okay. And if you click, so you will see its detail again. Okay. If you click here on this arrow, you will be able to see if you click on this lookup. So it will select where it is implemented in the flow. So if your flow is very big, it is having lots of element and you are unable to find whether that particular element is so you can simply click on this magnifier glass and you will be able to find that element, right? So this way you can see the change. Now you can go back. Okay. Here we have this undo button. So if you click so your operation will undo so you can see that variable is removed. It is just I just clicked on undo so it is removed. Then we have this redo button. So if you click on it so that variable will be available again. So this way by mistake if you perform any wrong operation so you can utilize undo and redo buttons. And if I save this flow, I'm just saving it. So I'm saving it with a demo flow name and clicking on save. So once I saved it, so here you can see it is activated. If I click on it so I can see the properties. What is the label? What is the API name description and other things? Okay. So I think this top left corner is clear to everyone. And here you can see one more thing. This is version. So once I saved the flow, so version one will be created automatically. Okay. Now I'm going to top right corner. So here you can see it is right now inactive. So I can just activate it. If I click on activate so it will be used. So it is active right now and this is version one. Now if I want to do some more changes, if I want to do some more changes of what I'm doing, so I'm clicking on it copying it and here clicking on plus and I'm going to paste it. So for paste, I need to. Okay. Let me just copy it again. So there is some issue in copy pasting. So, okay. No problem. Let me just create some new resource. I'm creating a variable. So this I'm creating as num to data type is number. So I created one more variable, right? So I just modified this flow. I created one more resource now when you update something in the flow, which is already active. So what you need to do you need to click on save as and there are two options available. A new version or a new flow. So generally we create new version because in the existing process we are adding some feature. So we will be clear. We will be creating a new version of that flow. But if you want a separate new flow, then you can go and click on this and here you need to provide the label and API name. Okay. So now what I need to do I'm just clicking on save. Right. So you can see this variable is created and now again, I have this active button enabled whenever you modify something. So whenever you modify something, so this active activate button will be disabled. So you just need to save as and then you will be able to activate again. Right. So this way I hope you are able to understand save save as an activate button. Right. So we have these two buttons as well run and debug. So right now I'm not going to explain these. So tomorrow I will be creating one flow from the scratch following a particular use case and then I will be explaining these two buttons how we can use them. Right. Now last I'm going to explain this auto layout. So this is also important. So right now you can see here flow lines are arranged automatically. You won't be able to place this screen anywhere. It is aligned automatically. So this is because of auto layout. Right. And if you want to insert any element. So what you need to do you need to click on plus and from here you can select any element. But we have different layout as well that is known as free form. If you click on free form so you can see it is changed. Now you can click and drag it drop anywhere and on left hand side you can see we have two buttons now two tabs elements and manager. So under manager you will see all the resources and under element you will see all the elements and if you want to create any element let's say you want to create one more screen. So what you need to do click and drag and drop and then you will fill all the details here and it will be available. So I'm just entering test to clicking on them. So this way one more screen is created and now manually you will be connecting it. Okay. So now you might be thinking like how or which form we need to use. So if you don't want to manage the flow lines then you can go with auto layout and if you want to manage flow lines yourself if it is very complicated then you can choose free form. Okay. So and here you can see if you click so you don't have any copy paste button. So those are shifted here. So if you click so here this is the copy button. This is the duplicate button. So if you click so you will be having duplicate and right now I'm not able to. So I think I just need to click on save. I'm clicking on it and duplicating so due to some issue it is not getting duplicated and like you are saying flow is active. That's why it is not creating duplicate. That is not true even if it is duplicate we can create sorry if even if it is activate we can create duplicates right. So maybe we just need to do refresh and then we'll be able to okay and at the bottom also we have these buttons. So if you click so I think it is for this like if you want this hand so that you can drag so this you can have this is for like these minus and pluses for zoom in zoom out and if you want to show your whole flow together on a same screen so you can just click here and it will be available right. So this this way you can zoom in zoom out and this way you can just arrange this on the canvas. So this is our flow builder so I just explained common things to you not much and with every use case you will be able to understand the requirement of these elements and the resources which are available here right. So have faith in me day by day week by week you will be able to understand the flow in detail and I will be giving you exercises on daily basis so you will be practicing them and you will be understanding like how we can implement simple and complex flow and we'll be building them together. Okay, so this is all about today's session so I just explained each and everything in detail which is related to like base for lightning flow now from tomorrow I will be starting screen flow then we'll discuss so I think this week we will be discussing screen flow only and next week I will pick other flows as well. So I just decided two weeks but I'm pretty much sure it will be taking almost three weeks right because you will be having lots of questions in between so I will try to wrap in two weeks but if we need three weeks so I will go beyond that as well because my aim is to explain each and everything in detail. So now if you have any more questions so you can ask and those who don't have any question they can leave and you can please join the session tomorrow same time and tomorrow's session will be more hands-on. So all the theoretical details I just gave you today and from tomorrow I will just say like this is the use case let's understand how we can implement the solution for that with the help of flow builder. Okay, so now I'm just scrolling the chat if I missed any question. Okay, Simi is asking brief description of the requirement for self-practice exercise. Okay, I will give them. Okay. So Anna is asking how to upgrade process builder and workflow rule to writing flow. So I think I already answered this then okay from you one is asking can you provide this comparison sheet for us to use? Okay, so what I will do in exercise sheet I will paste those tables. Okay screenshot of those tables I will paste in the exercise sheet so that you will be able to go through. Sameer is asking can we edit flows after activation? So yes, I did that as well. If you modify then you need to save as create a new version and then you need to activate it again. So if I take you to the flow when I save when I did save as so here you can see version two is available. So as you create new versions so your version will reflect here and after creating new version again you need to activate it Manoj is saying please use free form instead of auto layout. So this is not a hard code rule. So you can use any layout. It depends on your requirement. Right? So don't stick with any one type. You can use anyone. So there is one question. How many version am I added? So I think you can create lots of version. I worked upon lots of flow but never encountered any limit. So I don't think there is a limit but I will figure it out if there is so I will let you know. So after these flow session what I'm going to do I will give you all the flow best practices right. So there I will try to document each and everything that you can remember. I know this saying my weakest topic is flow. So I think after this bootcamp you won't say this statement anymore. Alex I don't think you won't be able to deploy admin project without implementation if you find like implementation somewhere so you can but I just customize that. So I don't think so. So Kate and as a fresher if you know the comparison that's enough. If you have never done implementation so you can simply say like I just started my Salesforce journey and last year Salesforce already retired. So I never implemented workflow rule and process builder. I'm working on flow builder only but in that case you should know flow builder because you will be having lots of questions through flow builder. So Archana is asking it is is it mandate to move apex trigger to flow now. So my answer will be no it depends on the project requirement whether to implement trigger or flow right. So flow is an option trigger is also another option. So nothing is mandate. So you are asking PPT so I won't be able to share because I continuously upgrade them so other than PPT I shared everything but slide decks. I won't be able to share for them. You just need to go through the recordings can may undelete operation is still not available with flows. It is available with trigger only they just funny. Okay. Thanks for letting me know like it has limits. So I will figure it out because I don't remember the exact number like what is the limit. So I will just research and we'll let you know. So go over them in apex we can do a lot of customization. So in apex and trigger we have lots of features but those features are available with flow as well. So you have both the options you can use flow you can use apex because with apex you can do a lot and nowadays sales force is also upgrading their flow. So we are able to do those things with flow as well. So it depends on the architect like which tool they are going to use for implementation in project. So Haritha is asking auto layout or free form which one is best so it also again depends on your requirement. So in my in my suggestion if your flow is small then go with auto layout if flow is big having lots of elements and if you want to drag and drop them at your own so you can go with free form. No we cannot convert apex class into flow. We can call apex classes through flow but we cannot convert apex class into flow automatically. Apex logic also you can implement through flow but you cannot convert them directly. Can we auto populate the lookup value through flow? Yes we can. So you need to query the data and then you can just fill the values. Rushabh is asking when you will start development part. So flow is also part of development but it is local development. So if you are not interested in local development so you need to wait for at least two or max three weeks after that I will be starting apex. Thank you Tejaswini for appreciating my effort. So I'm doing these efforts because nowadays like many people are facing issues like they are not able to understand things properly especially in Salesforce ecosystem. So I just started these boot camps because I have lots of experience of teaching and in IT I learned lots of things in Salesforce. So I'm trying to share as much as I can and I want everybody can have benefit. So Grinath you are you are also asking same question when flow is there what is the use of trigger. So let's build flow then we'll build trigger as well then you will be able to compare them. So don't think much. We have both features available through apex and trigger. We can do many things but through flow. We cannot do all the things that we can do through apex and trigger that's why still they are available but Salesforce is upgrading their flow so that flow builder can do more things. So it depends on the project requirement which tool you will be using. I won't be covering visual force pages in this bootcamp because it is completely outdated. Yeah, I will try to explain inbound and outbound later in the session. Okay. Yes, Amy. Thank you for reminding. So I will take this at the end because I'm just trying to cover all the flow related questions. So just have patience. Arjuna know we don't need to write test cases for flow for code coverage. But in record trigger flow like you can do unit testing but you don't need to write anything for code coverage and please ask a flow related questions so that I can just focus on that. If you are if you want to ask other questions, so I just created telegram group for that. So don't ask irrelevant questions. Please. So people is asking is it true that process builder not editable after activate so in process builder ripple. We just need to clone the process and then you will be able to edit that but existing you won't be able to edit. So Arjuna, I would say you should have like basic knowledge of visual force and aura but these two features are not used anymore because we have lightning web component. So practically you can learn them but theoretically you can learn visual force and aura. So for aura you can find the videos on my channel but for visual force you need to go through trailhead. So code coverage for record trigger flow is not needed. Yes, there is record trigger flow that is all always created on objects. Okay, so screen flow is independent to any object but record trigger flow is dependent on object. So record trigger flow is the option that is available against process builder and workflow rule. Okay, now I'm going to jump to project and there we had some self-paced exercises. So I'm going to explain them so that like Simee is asking she is facing some issues. So here like we have requirement create an Excel sheet and you will be creating the data for five candidates and then you need to import it through data loader and data import wizard. So I think it is easy straightforward. Then you need to update and absurd data using data import wizard and data loader. So in the above sheet you need to add ID of a couple of candidates that are already there in the org and you can update their phone numbers. Now you need to insert new ones and update existing ones together. Okay, then next is export candidate data where email is not null. So this you need to do through data loader. So you need to export the data. So through data loader your data will be exported and it will be available in form of Excel in your system. So make sure to select the ID field while export and now delete exported record using the data loader. Okay, so export you can do through data loader delete you can do through data loader and export you can do through reports as well. So here you don't need to create report. I saw your message in the telegram channel. You created report but after creation you need to export that as well and exported report you can use to delete the record but I would prefer like you can do this operation through data loader all as well. Then here also we have same operation insert now here export through reports. So you need to create a report where min pay is greater than 1000 and then you can export that report and I think I already explained how to export the report. Okay. Then yeah, these are very simple update and absurd then again. So first you need to do it through data import wizard. So in data import wizard, we don't have export option. So we will be using report but in data loader we have export option. So you don't need to use reports here. You can do it directly. Then the these are straightforward formula and validation rules and approval process. So I think now you will be able to do this still if you have any question. So I have created a telegram group. So you can ask your questions there. Okay. And Manos know I won't be covering that because I won't be teaching you like how to create process builder and flow builder. So I won't be doing that. Thank you. Saida ready for appreciating my efforts. So I think this is end of today's session and tomorrow we will be starting implementation of flow scenarios. So just share this information with everybody. Those who want to learn like development part free of cost, right? So everything is available free and you can see those who joined the session for the first time how depth the sessions are having. So I just covered the introduction of flows and it was to in depth. So every session I'm conducting in the same way. I completed 22 sessions and it will be about like a total almost 100 sessions. I will be covering and all those sessions will be having all the theoretical concept explanation demo implementation and question and answer. And I'm trying to pick each and every question so that I can answer. So I think it is taking at least one hour 30 minutes today took one hour 15 minute, but I'm sure like going forward. It will be taking at least one hour 30 minutes. So I'm ready to give my time. I just want you to practice whatever I'm saying so that you can master your skills. Okay. So thank you so much for joining today's session. And tomorrow like we'll be connecting and doing some hands-on with flow builder and I will be updating the exercise sheet so you can go through that and those who are behind in the project. So please try to complete because you have self practice exercise as well. So try to complete and share this information with everybody those who are interested to jump in the Salesforce ecosystem. And I would request like please connect graduate students as well those who are your juniors. So I think you are pass out from different different engineering colleges or different colleges. So pass this information to students as well because for students this is important to learn particular cloud and Salesforce will be very easy for them to follow and all these sessions are already available recorded sessions and the live sessions. So just include them with you so that they can also be benefited with this campaign that I'm running free of cost. So it will build our community as well and it will give strength to me so that like recent undergoing graduates and freshers will be learning those skills. Thank you Swati for appreciating my efforts. So please share the words and I just hope like now from onwards like everybody will be able to focus on the learning not like how to arrange the money. So this is the initiative. Yes, it is okay. I am from arts background still I am doing development. So background doesn't matter your attitude matters. Right. So if you do proper practice follow proper path and learn new skills have a good mindset interact with people like build your connections. So if you follow everything then your background degree doesn't matter you can do anything. So if you guys have more question you can ask I can see 81 people are still with me and I'm just talking other than the topic. So I'm happy like you you are here and learning the discussion. So if you still have question you can ask otherwise I'm going to end the stream and let's connect today and thank you for appreciating my efforts. So these motivational words really motivates me. So I daily I see lots of messages. So it it just boost me whenever I get up I see some like real good feedback. So it daily motivates me to do more efforts. Some me. Yes, so for that you can reach out to me but you should be expert in the topic because this is live platform and people will listen if you have proper knowledge and you should be having dedication. So I appreciate your like initiative you want to teach so you can reach out to me on LinkedIn some me if you are interested. So definitely I can include you on this platform so that you can share your knowledge and maybe we can have a chit chat so that you can you can share your experience. So I'm also planning those sessions like after boot camp maybe I will try to interact with few folks live so that they can share their experience with the community and they can motivate the fresher or students so that they can also start their journey with Salesforce ecosystem. So inclusion of our student is very important. Those are still in colleges because in college Salesforce is not part of the curriculum. So if if they are like in third year or fourth year of their graduation if they start learning this new or hot technology so they will get lots of benefit. Yes Manoj migration tool like it is very easy if you already have like workflow rule or process builder created so you just need to click on the button it will be converted automatically. It is like two minute task. Tarp it is a very difficult to crack job without degree but you can try. So if you try for startup so I think it will be easy because big companies ask for degrees so you just need to search for light company if you want to have a job without degree. Okay so I think I answered each and every question now I just take a leave. Thank you so much for joining this session. See you tomorrow. Same time. Thank you.