 Hello. Hi, everyone. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So today we have day 23 of this Salesforce learning bootcamp. And in today's session, I am going to discuss about the screen flow. So in yesterday's session, we discussed about the flow builder and we discussed all the basics of flow builder and type of flows. So we'll be picking first type of flow today and we'll discuss scenario of screen flow in today's session. And I have prepared some exercises for you and provided some reference videos as well. Okay. So once again, hi and welcome to everyone and happy holy to all my Indian friends. So this year like we are celebrating holy two different days today and tomorrow as well. So happy holy to everybody. So in Jaipur, we celebrated holy today, but we have vacation tomorrow. So it is like two days benefit. Okay. So now I'm moving forward. So those who started these development sessions only. So if you don't know about me so you can just go through this slide so that you know with whom you are learning. So I have variety of experience and work with big IT companies and acquired a lot of knowledge on Salesforce in last six years that I'm sharing with you live and lots of recorded videos are also available on the channel. And in each live session, we are following these best practices. So you might have heard about best practices when you implement anything in the Salesforce. So why not to follow best practices while learning something. So these best practices will go whenever you learn something new, right? So you need to follow all the sessions, write proper notes. So in today's session, you will be having lots of doubts. So I would request you to please note down all the doubts somewhere and whenever I will be completing the session, you can ask those doubts so that dedicatedly I can answer those questions. And one request like please ask relevant question related to screen flow only. Don't ask any other irrelevant question, right? Because in that case, I just need to skip those questions. So this week, I will be having one session, particularly for your certification preparation. So in that session, you can ask any DIFO question, right? So I will try to answer there. And I hope you are following all the sessions and each session is connected. So if you miss any session, you can just go through the recording. And I hope you are following the exercises as well. And like today also, I will be explaining topic for 50 to 60 minutes will do some demonstration as well. And then I will take all the question and answers live. And if you are not able to join the session live and you want to ask questions, so you have three platforms where you can ask questions. So you can just mention comments on YouTube videos, Telegram and Instagram, you can use. So this is our Salesforce development bootcamp timeline for upcoming six weeks. So we are in week seven and we already understood basics of flow. And today, we are starting screen flow. So today, tomorrow and day after tomorrow, three days, I just fixed for screen flow scenarios. So we'll do lots of hands on and I will be providing some exercises for you so that you can practice them. Okay. And like if you are following this bootcamp from beginning to end, so you can just add it to your LinkedIn profile. And you can also add your skill set, whatever you will be learning through bootcamp in your resume. And we will be like completing one project, which is recruitment application. So you can mention that application in your resume and along with the features that you are implementing, right? And please subscribe the channel and follow and share the information. And like I just modified this slide today and you can see there are three blocks available at the bottom. So I just want some gratitude and support from you. So you can see like weekly I'm sharing my knowledge through live sessions. So I'm conducting at least three to four sessions every week. So in return, if you can support and help me to reach like 100k subscribers, so that will have that will be helpful. So like whoever want to learn C C++ Java and Salesforce admin and development. So please share the YouTube channel link in your telegram groups or WhatsApp groups, those you have created so that I can reach to as many students as like students are available. So you all know my teaching methodology. So you can just promote and help me to grow. And here you can see I have lots of upcoming courses planned. So once this bootcamp will be completed or maybe in between, so I will be introducing cloud specific bootcamps, then you will be having four more bootcamps like which will be related to cyber security DevOps data science and web development, right? So these four bootcamps will be delivered by experts. So they are just preparing the content and soon they will be delivering like sessions on these topics. So if you know who want to learn these things freely, so just align them with this channel so that they will be connected and whenever sessions will be available, so they will be able to join. Okay, so now after this information, now let's jump on the topic. So which is screen flow. Okay, so yesterday I already explained you the use of screen flow. So I told you like screen flow is a spatial flow which gives you a process through which you can create a UI and that UI you can use to interact with the user. So today we are going to implement a UI with which we will be interacting with the user. So user will be providing some information and basis on that information a process will be performed. And I already told you like we can launch our flow through lightning page experience builder site or quick action. So lightning page and quick action we'll see today. Okay, so now I'm going to show you the screen flow scenario that we are going to implement. So with this scenario, you will get to know lots of things related to flow. Okay, so yesterday in yesterday's session, we discussed like in flow, we will be using two things mostly. First one was the elements. Right. And second is resources. Okay, so those two things we will be using today to implement the scenario. So scenario is very simple and always keep in mind like flow is very simple to implement because you don't need to write any single line of code. So if you don't know programming, still you will be able to build the logical problems. You can build their solutions. Right. So in this one hour, I will explain you like how easily you can create a screen flow. And here you can see the requirement is we need to create a screen flow to create an opportunity record related to an account. Okay, so we will be debugging the flow. We will be launching the flow through quick action. Then I will show you like if there is any error in the flow. So how you can handle that. And later we'll see like how we can place our screen flow on account record page. So one by one, I will like implement each and everything and I will cross verify whether I have implemented everything or not. Okay, so now jumping to the developer org. So here on the pit point, I just need to search for flows. So here this option is available. And I'm just clicking on flows. So here you can see this option is available. So at top right corner, we have this button, which will be used to create new flow. Okay, so now this UI is available to select the type. So I'm selecting screen flow from here and clicking on create. Right. So here I already told you we have two layouts auto layout and free form. So right now I'm going to select auto layout. Then after completion, I will be converting that auto layout into free form. So you will see like how auto layout implementation will be converted into a free form layout, right? Okay, and if I forget because that is not mentioned in the slide. So if I forget to convert auto layout into free form, so please just note it down. If I forget, so just mention this in the comments so that I recall and I will show you that in today's session. Okay, so now what we need to do, we need to create opportunity opportunity record related to account. Okay, so my requirement is through this screen flow, I just want to retrieve the information from user. Okay, so first of all, you need to click on this plus sign. And if you click on this plus sign, so here you can see we have all the elements. So yesterday I told you we will be using these elements to create flows. So if you have selected screen flow, then only this screen option will be available to you. This screen option is not available in record triggered scheduled or like auto launch flow. In those flow, the screen option is not available. It is available with screen flow only. So I'm just clicking on it. So as I clicked on that screen, so you will see this kind of UI. Okay, so this is basically screen builder. Through this you will be able to create a screen and through that screen, you can receive some input from the user. Okay, now first of all, we need to decide what are the required fields to create an opportunity record. So if I take you here, and if I open sales application, so under sales application, you will be able to see opportunities tab and on opportunities tab, if I click on new and it is very easy to identify what all are required fields. So what you what you need to do just click on save without filling anything just click on save. So you will see lots of error messages. And with those error messages, you will be able to identify what all required fields are available. So here you can see three required fields are available closed it opportunity name and stage. Right. So anyhow, if you want to create any opportunity record through screen flow, so you need to receive information these three information from the user. If you don't receive these three information, then you won't be able to create an opportunity. Right. So I hope it is very easy to understand now. Now I'm jumping here. So here you can see first of all, I just clicked on screen. So here you can see at right inside we have screen properties. So here you need to provide label of the screen and API name of the screen. So screen is also like an element inside the flow, which should be having an identification. So here I am labeling it as opportunity info one. So its API name will be upon OPP underscore info underscore one. Right. Okay. Now here you can see we have this header on the screen and we have this footer. So on header what will be displayed it will be displaying the flow label. So we will be saving this flow with a label. So whatever name you will be using to save this flow that label will be appeared at the top of each screen. So here you can see we have this option to configure the header. So if you want to remove that header, you can uncheck and you can see header is gone. Right. Similarly, you can configure the footer as well. So under footer, we have three buttons pause, previous and finish. So if you don't want any button, you can just uncheck. So your footer is also gone. If you want, you can check and then you can control them individually. So I think these are very easy to understand. So for next or finish button, if you want to use the standard label, so by default it is selected. If you want to use a custom label, so you can define that. So here you can write the label. And if you want to hide it, you can just select the third option. So if you select third option, so you can see only previous button is available. Next is not available. Again, if you select, so it is available like finish. So if you have multiple screens, so you will have next button instead of finish and finish will be available at the end of the screen. Okay. So right now I am having both header and footer and later we'll see like how we can remove that as well. Okay, so these are the properties of particular screen. Now what we are going to do, we are going to place some components here. So at left hand side, you can see we have some predefined components that we can place. So first of all, I'm going to receive opportunity name. So name is always a text data type. So I'm just selecting text. So what you can do search for text here and click on this text. If you click, so it will be available on right hand side. Okay. So this is a component that we placed on the screen. Now at right hand side, you can see this is the property of this text component that is placed on the screen. Okay. If I click on this header, so you will see the properties of screen. So you just need to go through this label. It is showing screen property. If I click on this component, so it will show the property of that component. So component is text. So here you can write label like opportunity name and API name will be available automatically. If you select required, so it will be having this red asterisk. It means anyhow, you need to fill the value in this particular component. Right. Then we have other options like set component visibility. So you can apply conditions like whether you want to show this component on the screen or not. So right now we are selecting always and if you want to validate the input, so here you can just add the error message and that error message will be available if you don't provide any input. Okay. So I just provided opportunity name here as text. Now I am going to select second one that is date. So I'm just clicking on date. So here date component is available. I'm moving on right hand side and here I'm typing closed date. So label I typed as closed date and API name will be closed date. And here I'm selecting required as well. If you want to place any default value, so you can provide that as well. But I think in our case that is not required. So this way on the screen, I just placed two components. One is text for opportunity name. One is closed date for reading closed date. Okay. Now we have third option that is stage. So knowingly, I'm not placing that stage on this screen because I just want to show you how you can create multiple screens. Right. So on one screen, you can add any number of components, but I'm going to show you how we can create more than one screens in screen flow. Okay. So these two inputs I am going to receive in the first screen. So I'm just clicking on done. So here you can see screen one is created. Its label is OPP info one. Now I'm going to click on plus and selecting screen again. So this is another screen new screen. And here I'm going to write OPP info two. So this is my second screen. Now I hope you will be able to relate like this is header footer and how we can control these options are available. So accordingly, you will be able to configure. Now here we need to provide stage. And here you can see stage is a pick list. Right. And it is already having lots of pick list values. So when we will be creating opportunity record through screen flow. So we want all these pick list values populated on that screen. Right. So how we will be doing that. So from here, I'm going to select pick list component. So I'm just clicking on it and it will be available here. Right. So here I'm labeling it as stage name. And it will be required. Okay. So it's data type is text. Now here we have this important thing that you need to understand. Okay. So here you can see we have this component type. So it will be pick list. And here we need to provide the choice. So now we have two options and listen it carefully. We have two options. First either we create all the pick list values manually in the flow. And those values will be available in this pick list. So this is first option. And second option is can we link the pick list field that is available on opportunity object with this pick list component. So I think you will select second option because in first option we need to create all the pick list values manually in the flow and that will take lots of time. So if we connect the existing pick list field that is available on opportunity object with this pick list component that we are creating in the flow. So that will be better because in that case you don't need to create fields pick list field values manually. And second benefit will be if you modify any pick list value on stage field under opportunity object. So this flow component will be receiving those modified values automatically. Okay. So we are not going to create pick list values manually here. We are going to link this pick list component of flow with pick list field of opportunity object. So I'm just clicking on new. And here you can see we have new choice resources. So this is the same resources that I showed you yesterday but it is showing some limited options because right now we are like working with specifically with pick list. Okay. And if you want to create or if you want to link flow pick list component with pick list field. So you will be choosing this fourth option that is pick list choice set. So here you need to provide the API name. So I'm writing stage name then select the object as opportunity. Now on opportunity we have two types of pick list. So I'm selecting pick list because I don't need multi select pick list as of now and field I want stage name. Right. Then we have sort order. So you can select that as well as per the requirement and click on done. That's it. So we just created record choice set. If you see here what we did we created record sorry not record choice set. We created pick list choice set right. And through this pick list choice set we are just connecting flow pick list with pick list field that is available on that object. Okay. So here it is configured if I click on this. So here you will be able to see this like here we have this stage and stage name it is pick list choice set. Now I am clicking on done. So we created these two screens. Now if I go here at top left corner and click on this icon. So here you will see all the resources that we have created so far. So what we did we created two screens OPP info one and OPP info two then we created three screen components. One is closed date one is opportunity name and third is stage name. And while creating stage name component we created one pick list choice set as well. That is stage name and this pick list choice set is basically connected with the pick list field that is available on opportunity object. So from opportunity object that stays field values will be available with this pick list choice set and it will be filling those values under stage name. Right. So this way I just created this. Okay. So someone is asking how we can create pick list values manually. So this I'm going to show you in tomorrow's session. So in tomorrow's session we will be having a scenario where knowingly we will be creating pick list values manually. Right. So right now I'm not going to show. So in tomorrow's session like I will be creating those and you will be able to understand them. Okay. So I just created two screens now and I'm going to show like I'm going to first save it. So I'm clicking on save button. So opportunity on so create an opportunity on account. Right. So this is my flow label. So flow label you can choose as per the requirement that you are implementing. So it can be anything and I'm just clicking on save. Right. So my flow is saved and before activation we have two options available here. So as I showed you in the slide like we will be creating the flow and I will show you how we can debug it. So I have not completely implemented the flow. I have implemented it half but still I just want to show you how we can debug this much. So we just created two screens and we'll see how we can debug so that we can verify they are working fine or not. Okay. So if I click on debug button. So here you will see the result of that flow. So I have not activated flow right now. So I'm clicking on run. So without activation you can just debug. So here you can see flow label is available. Create an opportunity on account because we didn't remove header. So that's why header is showing this and in the footer you can see next button is available. Right. And on this first screen we have two option opportunity name and closed date and both are required without filling. If I click on next. So you will see this error message. Right. And here on right hand side you will see all the debug details. Okay. So what I'm going to do I'm filling opportunity name. So let's say test OPP one zero one and here I need to provide the closed date. So from this calendar I am just selecting closed date. Okay. Now if I click on next so it will show me the next screen. So here you can see I have stage name and if I click so all these stage values are available automatically. So I didn't create these stage values manually. These are available automatically because we created pick list choice set. And if I go to right hand side so here you can see the debug thing. So I just clicked on next for screen one only. So here you can see what you provided on screen one is available here. So we provided opportunity name as test OPP one zero one and closed date we provided as March 23 two zero two three. Right. So whatever you do in your flow that will be available step by step here on right hand side. Right. Now if I click particular stage and click on finish. So here you can see it is showing opportunity info one and if I scroll down so it is showing opportunity info two as well and I selected choice as qualification. So that is also displayed. Right. So this way you can just debug your flow whatever you have implemented so that you can verify whether you are going in the right direction or not. And you can just close and you can come back on the canvas. Right. And I can see one question which is related to this requirement. So someone is asking like can we combine these two screens and have stage on OPP info one. So my answer will be yes. So knowingly I just created two screens so that I can show you how we can navigate from one screen to another. But if you want one screen and on one screen you want stage as well. So that is possible without creating second screen you can put stage pick list on screen one and you can follow the same process. Right. So I hope till here you are comfortable and you are able to understand things so we can see all the resources that we created are available here. So now after receiving all these information like we will be able to receive opportunity name we will be able to receive opportunity close date and opportunity stage name. Now after receiving all these information from the user in the background we need to create an opportunity record. So how you will be doing that again click on plus and here so we just use screen interaction element. Now I'm going down and I will be using another element that is available under data element. So I will be selecting this element that is create record. Okay. So I'm just clicking on it. So it will show another UI. So you can see without writing single line of code we are doing programming. Right. So we are building all the logics but we are not writing any code everything we are doing through point and click. So all the like pop up windows are available you get just you just need to configure things and accordingly your process will be completed. Okay. So here what we need to do we need to create opportunity record we need to create opportunity record and it is asking how many records to create. So we will be creating one in like one of the scenario we will be picking this as well like how to create multiple records but right now I am focusing on one record only but we can create multiple records as well then how to set the record field. So if you want to create multiple records so generally we go with this first option but if you are creating one record so you will be selecting the second option like use separate resources and literal values. So why separate resources because opportunity name close date and stage all three information are available into three separate resources. So that's why we are selecting this option and here you will be selecting opportunity object because we are trying to create opportunity record. Now what you need to do you need to do field mapping. So on screen you created three resources to receive opportunity name close date and stage. So you just need to map those input with actual fields those are available on opportunity object. Okay. So on left hand side you can see we need to select the field. So I'm selecting name. So this is opportunity name field and we need to map it with opportunity name text screen component that we created. Okay. Then again click on add field and here you just need to select close date and you will be linking it to close date that is screen component. So on right hand side whatever we are seeing these are screen components then we need to map stage. So here we have two stage name. So you will be selecting second one screen component because the screen component will be receiving value from the user and to show pick list values we created pick list choice set. So you don't need to select it here you will be selecting this one screen component. Okay. So this way all three values are set then we have this checkbox. So whenever opportunity record will be created. So for that opportunity record and ID will also be created. If you want to store that ID into a variable so for that you can just check this checkbox and here you can create a variable where you can store the opportunity ID. But right now in this example I am not going to use this checkbox but maybe tomorrow or day after tomorrow we will be having one example where we will be enabling this checkbox and we will be creating a variable where we will be storing the newly created record ID. Okay. So few things I am just ignoring in today's session but trust me tomorrow or day after tomorrow whatever we are skipping will be covered properly with other scenarios. Okay. So I just mapped all these values. So here you can see these values are screen flow values and these are fields which are available under opportunity object right. So right hand side will go to left hand side and you can see these arrows are available which are clearly indicating right hand side values we are assigning to left hand side. Okay. Now I am just clicking on done. So this way I just mapped all the resources with the fields and these three elements we created in this flow. So two screens we created and one we created this create opportunity record element and on left hand side you can see we have this element create record and its name is create underscore opportunity underscore record and here we have these find icon like find on canvas. So if you click on this so it will be able to select where it is available. So this way you will be able to find them on the screen. Okay. So now I am clicking on save again. Okay. So this flow is saved. Now first time I am going to activate it right. So I am just clicking on activate so it will be activated. Now if I go to slides so I just showed you like how we can debug the flow. So you can also debug this completely build flow so that you can test whether it will be working fine or not. So let's test it through debug first and then I will place that flow on a quick action and through that we will be testing it. Right. And I can see lots of questions are available in the chat. So I will be first finishing all the explanation because I don't want to break the sequence and then after completion of all the demonstration I will pick all the questions. Right. So I'm just clicking on run. So we are just debugging and always remember whenever we debug a flow and through debug process if you are creating updating any record. So it will actually modify your org as well. Like in this case a record will be created in the org. So here we need to fill opportunity name. So I am filling test one one zero one and we need to select the close date. So I am selecting the date. Now I am clicking on next. So here you can see debug information is available here. We need to select the states. So I selected qualification clicking on next. Now you can see the debug. So I'm going to show it step by step. So first of all we have screen one details. So we have a value for name. We have value for close date. Then if we scroll down so we have value for OPP info to that is our pick list states. So we selected qualification. So that is available here. And if I take you further so we have this create record element. So which is our third element. So here you can see values are mapped. So this is close date which is having March 16 2023. It will go to close date field opportunity name will go to name and stays will go to stays name. So in parenthesis we have actual value that is being provided. And this is the syntax like these are your flow elements. Okay. Flow resources you can say. And here you can see like this record is created and opportunity record ID is available. Okay. So now we need to verify whether this record is created in the org or not. So we will be comparing this ID. So I'm moving here and canceling it clicking on opportunities. And here you can see this test one one zero one is created if I open it. Okay. So if I go to details so I will be able to see the details. So here you can see opportunity name is test one one zero one close date as this and stages qualification. Right. And if I take this ID if I copy it and if I try to search it here. So I am just typing I am just pressing control F and control V. So you can see it is highlighting it means ID is matching. So the record which we are viewing is the record which is created through this flow when we debugged it. Right. So once you debug your flow so your record will be created. Okay. So now we just saw like how we can debug the completely implemented flow. And I just showed you a record is also created. Okay. Now there is one catch. There is one catch. If you go to the record and knowingly I didn't implement it. So I'm going to implement it now because I just wanted to have your attention. So here you can see this opportunity is not related to any account. Okay. This is not related to any account. So we need to do some we need to create some steps or process for that so that it will be linked to particular account. Right. So what we need to do just go to your flow and close this debug information. So we have this flow. Okay. So someone is reminding like I just need to show the free form layout. So like I'm just going to show you that thing. So if I click on free form so this way it will look like you can just drag and drop it anyway and all the elements are available here. Okay. So anytime if you create your flow in auto layout form so you can convert it into free form if you open it so all the details will be available as is. Right. So everything will be available as is and if you want to go back to auto layout. So here it is showing the warning like when you switch to auto layout all unsaved element positions are lost to keep all element position save the flow before switching to auto layout. Right. So this you need to take care if you want to convert. So right now I'm not converting because I don't want to take any risk and I just want to show you like how it will be working from the UI actual account record. Okay. So in your case like whenever you will be implementing so you can just switch in between okay. Now I was just showing you how we can relate this newly created opportunity with the account. So now listen it carefully whenever you will be placing your screen flow on account record page or quick action. Right. So you will be running this screen flow through particular record. Right. You will be running this flow through particular account record. Right. With which newly created opportunity will be related. So in screen flow there is a prebuilt functionality like if you create a variable so here you can see I am creating new resource. So let me show you how I opened it. So I just clicked on manager and clicked on new resource and this option will be available and I'm going to create new resource as variable. Right. So remember and see carefully this variable name should be always this record ID. So here I is capital and everything is in small. Okay. So whenever you place your screen flow on any record page or you link it through quick action or you place it on record page no matter whatever record you are opening that records ID will be available automatically into this record ID variable and always you need to use this record ID. Right. Record ID variable. So this name should be intact and here we have data type. So you will be selecting text because record IDs are available in text form and you need to enable this checkbox available for input because you will be receiving record ID outside the flow. Okay. So if you want to receive input values outside the flow so you will be checking this checkbox available for input and if you want to throw value of a variable that you're creating in flow outside the flow so then you can check this second checkbox but we want to receive input. So I'm checking this checkbox. So this is important and I'm clicking on done. Now one more thing we need to do. So here I just clicked on create opportunity element. So here I'm just clicking on add field. So here I'm selecting account ID. So account ID is a lookup that is available on opportunity. Right. So you need to fill it with record ID variable that you created. So whatever record ID you will be receiving that will be the idea of particular account record from where you are launching the flow so that account record ID will go to this account ID field that is lookup and the newly created opportunity will be automatically linked with that with that account. Okay. Now you can click on done. So now I just modified this flow and we already activated this flow. So what we need to do if you modify any activated flow so you just need to click on save as yes. And here you have two options. Either you can create new version or new flow. So generally we prefer to create new version so that anytime if you want to go back to the previous version so that will be possible. So just click on save. And at top you can see we have version two. Right. And from here you can activate. Okay. So someone is asking like what is the difference between debug and run. So if you click on run so you won't be seeing that debug information that I showed you at right inside. So run means you just can check whether it is working fine or not. You won't be able to see the debug messages. So if you want to see debug messages go with debug if you just want to run it click on run. So it is activated now I'm going to debug it. So once I debug so here you can see we created record ID variable and now that record ID variable is asking an input. So here we just check that checkbox available for input. So if you debug any flow and you created a variable that is having that checkbox available for input check so you just need to provide that ID as well so that because we are not launching this flow from any record page. We are just testing it in a debug window. So you just need to provide the account ID with which you want to link your newly created opportunity. So what you can do just go and open any account record with which you want to relate newly created opportunity. So here you can see we have zero opportunity created. So I am from this URL I am just copying the ID of account and here I am going to paste it clicking on run. So at right hand side you can see this record ID variable is receiving this value. It is also shown here. Now you can just fill the name of opportunity select the date click on next. Then you can select the stage. So click on next and this time if I show you the debugs. So here you can see four fields are mapped. So we have account ID lookup available which is mapped with record ID and record ID is containing the ID of account record and newly new opportunity is created. This is the ID of newly created opportunity. Now if you go here so we are on account so I am not moving to opportunity. I will be refreshing this page and on this related list you will see the opportunity. So I am just refreshing it and under the related list you will see a new opportunity that is created. Here it is. So from here you can open it and if you go to details so here you will see the account name. So this way I hope you understood the requirement of that record ID variable that we created. Why that is important. Okay and I hope most of the features you understood that is available in the flow builder. So those folks who are like learning flow for the first time so I hope for them this detailed explanation is very fruitful helpful and like I am going to place this flow now I am going to show you this third option how to launch screen flow through quick action and then I will show you how we can place screen flow on the record page. So all these requirements I placed here as well. So this is our exercise sheet if you go and see day 23 exercise and someone requested me to place these screenshots as well from yesterday's session. So I just placed. So it is the same sheet that we are following from the beginning. So here you will see day 23 questions. So first second I am explaining here and remaining you will be practicing yourself. Right. So I just provided reference videos. Those are already recorded by me. So first try to create them at yourself and then if you face any challenge so you can just go through the recording and you can just see how I implemented that. So this way if you do day by day practice so you will be able to understand these things properly. Right. So it will not be a burden for you because you are doing all the practice on daily basis. So generally people have a problem like they are not able to maintain a daily schedule. So I hope with the with this boot camp like we are on day 23 and now I hope many folks are able to maintain proper day wise schedule. So if you complete your exercises day wise so it won't be a burden and you will be having lots of scenarios implemented by your own. Okay. So I hope this information will help you out. So now I'm going to place our screen flow on quick action. Okay. So for that I'm moving to object manager. So if you want to place your screen flow on quick action so go to object manager and you need to select the object like for which you want to create related records. So we are creating opportunity but we will be creating opportunities through account record. So quick action we will be creating on account and in one of the session I just showed you how we can create quick action. So we created quick action through this button links in action. If you remember we created it to create new records but today we will be creating this action to launch the flow. So what I did I am just going to show you again I just clicked on this button new action. Right. If you click on this button so you will see this UI. So object that we are like working upon is account and here we will be selecting the option flow last option. You need to select last option that is flow and here all available screen flows will be listed. So we created create an opportunity on account. So this flow is available and if your flow is active then only it will be available here. So you will see only active version of the flow. Okay. Now let me show you one more thing. If I go to setup and if I search for flows so I'm going to show you how you can see the versions of the flow. So just search for flows and here is our flow that I created today. You can see data and time are available. So I'm just clicking here and clicking on view details and versions. So if you click here so you will be able to see different versions. So I created two versions and my second version is active. So wherever deactivate is available it means it is active. Okay. So two versions are available and second version is active. So that will be available to select from that list. Okay. So from here you can delete you can open deactivate activate whatever you want to control you can okay. So I am moving here. So I just selected the flow and here I am writing create OPP through flow. This will be the label of my action so that we can easily identify where it is available with this name and I'm clicking on save. So it is created and if I again click on object manager click on account and click on button links and actions. So here you can see it is available and it will be calling a flow. Okay. Now in one of the session where we discussed about global action and object specific action. So I just showed you like after creation of this action you just need to go to page layout and you need to place your quick action on particular layout. So from here I'm going to open account layout and here I'm clicking on mobile and lightning action. So here your action will be available. So it is create OPP through flow. So if I scroll and click drag and drop it here. So you need to drag and drop it under Salesforce mobile and lightning experience actions. Right. So you just need to click drag and drop it here and you need to click on save. So this way quick action is added to the layout. Right. Now if I come here and go to accounts tab and if I open any of the account records so here you can see this action is available create OPP through flow. Okay. If I open any other account so right now XYZ one is open. If I open any other like I'm opening edge communications. So here also this quick action is available. So it means on each record this quick action will be available. And if you click on this button so you will see flow will launch and we are able to see header. We are able to see footer and we can provide some information. Let's say test OPP through flow. We are selecting close date and writing action instead of flow because I will be showing you how we can place that on record page as well. Clicking on next going to click and select stage. Right. So here you won't see any debug information because now you are interacting on the UI. So you can see yesterday I told you through screen flow you can create UIs which will be useful for like building a business process and through that you will be able to interact with the user. So I think you are able to see how we are able to interact with the user. And now I'm clicking on next and your record will be created and it will be available under opportunity. So here it is test OPP through action. So opportunities created and it is automatically related to this account. So this time we did not pass record ID because I already told you when you place your action on record page. So particular account ID will be passed automatically into that record ID variable which we created in the flow. Right. So this way I hope you understood how we can place our screen flow on the quick action and we tested as well. Now before showing you how we can handle error I am going to show you how we can place our flow on record page. So as you all know if we open any of the account record so this is basically known as record page. So here we have activity and chatter component. So before this activity and chatter component I am going to place that flow. So I am clicking on this gear icon at top right corner. So if you click on this gear icon so you will find this edit page option just click on it and it will open lightning app builder. So under this lightning app builder at left hand side you will be searching for flow. So here you can see flow option is available. So what you can do just click on this flow and drag and drop it above activity and chatter and come to the right hand side. So here you will find all screen flows. You will see only screen flows. You won't see any record triggered flow or schedule triggered flow. So this is the flow create an opportunity on account. So I am selecting it. Here we have this option like if you want to edit the flow in flow builder so you can open it from here then we have a layout like one column or like if you have created columns in the flow so that you can use. Now this is important. So when we created quick action so at that time we didn't see this option because in case of quick action record ID will be passed automatically into flow. But when you place your flow on record page so in that case you need to enable this checkbox so that the current record that that you are viewing its ID will be passed to the flow. Right. So this is important to enable if you don't enable then your opportunity will be created but it won't be linked with your account then click on save changes are saved then go back and on each account record you will see your flow. So here you can see flow is available so we are on edge communications here we can see flow if I go to any other account record I am opening Dickinson PLC so here also you can see both quick action is available both quick action is available as well as we can see this flow and on this account we have only one opportunity now I am going to create one more so I am labeling it as test OPP through record page then I need to fill close date clicking on next selecting stage and next so it will be saved opportunity will be created here you can see now this record is having two opportunities right so this way I just showed you how you can launch your flow through quick action and how you can place your flow on record page and in upcoming sessions I will show you how you can place your screen flow on app page and home page but like if you complete the exercise so I just provided this question here like how to place the screen flow on home page or app page so if you go through this you will be able to understand it clearly now I am going to show you like what happens when flow fails and how we can see failed flow interviews okay and these questions you will be creating like how to create a related contact on account how we can create a related case on account so if you practice these two scenarios you will be able to understand the working of flow and if you get stuck somewhere just watch today's recording or you can see these recorded videos as well now I am going to show you how you can handle flow errors so let's jump to our flow and here I am going to open this create record element and just see carefully I am going to remove this close date mapping so close date I am going to read from user but I am not going to map it with the field so what will happen whenever I will be trying to create an opportunity so it won't be created because close date will be missing so this I am doing knowingly but it can happen unknowingly whenever you will be implementing the flow like if you forget to map particular field and that field is required so your flow will fail so I am just clicking on done now one more thing you need to understand if you modify the flow if you click on save as and create a new version and activate it so wherever you have used your flow so that place will be using the latest version automatically so now from this button or from this flow UI you will be launching the newly created version that is version 3 okay so if I create new opportunity now so it will break if I click on next if I select stage and if I click on next you will see okay I didn't refresh I am just refreshing the page and let me see whether flow activated or not yes it is active so I just refresh let me create it again so here you can see so earlier it worked because I didn't refresh the page so this is a another learning if you modify your flow so first of all create a version then activate it and then refresh the UI front end then only try to test it right so if I tested so here you can see it is showing this error and unhandled fault has occurred in this flow so the user who created it the logged in user will be receiving an email right and like if you are not a logged in user you didn't create this flow still you are seeing this error so what you can do just go here and search search this option pause then failed flow interviews so if you click on this option paused and failed flow interviews and if you go here so we have two option failed flow interviews and paused flow interviews so I am clicking on failed flow interviews and here it is so you can see today at this time it is failing api name is this version is this type is screen flow then here you can see last modified by last modified date and time then current flow api name and version so all the details are available flow interview guide so here you can see everything is available now if you click on this so complete detail will be available so here you can see why flow failed this information is available if you go through here it is showing the error required field missing and that is closed it so this way if your flow fails so you can just debug it through this option all failed flow interviews okay so it will show you the information and through this you will be able to identify so what will happen if you develop this flow as a developer and some qa will be testing it so qa will see this error so qa will take a screenshot of this and will create a bug and you will see that bug now what you need to do just go to that particular environment and open failed flow interviews and then just open the latest failure record and just see why it failed so this way you will be able to see like why your flow is failing okay so this way I just explained each and everything that I just planned for today's session right now I'm going to take the questions that you typed in the chat and those who are not having any issue they can leave and those who just want to attend this Q&A session they can be online and again I just want to request like please share the information and help me to reach 100k subscribers and just share the information with the person who need real knowledge on cc++ java so I just created more than 500 videos on these programming languages whole as a whole and on Salesforce admin and development like more than 300 videos are available so anyone who want to begin their programming journey so they will be benefited okay so thank you everyone those who want to leave and now I'm going to scroll the chat so that I can take questions so one question is warm see Krishna is saying Sanjay if possible can you do a one-to-one live video so this is not possible because I don't have enough time for one-on-one but soon I will be creating top-met account I hope you might know about that so it provides one-to-one meetings so I will like find out one hour from my daily schedule and I will be opening four slots of 15 minute seats there you will be having opportunity to interact one-on-one with me but that I will be starting later like first I just want to focus on this boot camp and then I will be starting so Mukda is asking can we bypass validation rule by a screen flow yeah so we can but you need to apply some hex if you want to bypass validation rule in screen flow right so I just created one flow in record triggered flow to bypass so if you come here so here you will find one video related to that not here so if you go to administrator flow builder so I think here you will have one video no I don't have here let me just see again the scenarios no bypass I don't have I will see I just remember like I created but I'm not recalling it so if you if you see this list carefully so I think you will be able to find a solution for that okay so taking more questions so there is one question how to use dependent pick list in screen flow so I think this won't be possible in screen flow as of now because I have never used dependent pick list in screen flow so like if you have created dependent pick list on under particular object so just try to create two pick list components and try to map them with the pick list resource and then see what happens because in real-time scenario I never use dependent pick list situation in the flow so I will try to practice and if I will be able to complete that so maybe in one of the session tomorrow or day after tomorrow I will try to include that okay so I'm just taking questions one by one so it will take time so if you like don't have enough time you can leave otherwise you can just be with me so Archana is saying I cannot debug it just shows black screen so I just showed you like in my case it is working so just make sure you are logged in as system administrator and Mangesh I think I already showed you a difference between run and debug and betha santi also showed you like if you activate then only we will be able to run so this is also good like before activation you can just debug so I would say like always prefer debug overrun so Bhakti is asking in back-end flow uses apex or anything else I'm not sure I think some apex related code will be there so that flow implementation converts automatically into code so I already showed you free form tongue so next question can explain what is transaction commit and debug log yes so Archana is asking can you explain what is transaction commit in debug log so transaction committed means like your record is created in the org so transaction means the process the flow debugging process is particularly a transaction committed means your record is successfully created in the org that is known as committed okay so so Ferris is asking how we can store multiple IDs so first like screen flow will be working on one record at a time so you won't be receiving multiple IDs right so you will be receiving one ID always so you can create record ID variable for that purpose okay so I'm going to pick next question so Aparna I think I already showed you how to identify debug records so Akula if it is happening so maybe some other automation is working in your org like if you are selecting qualification and it is showing prospect so some other automation is working next is can we create record ID for custom object and is it applicable for both master detail and lookup relationship yes so Sandeep my answer will be yes for both the questions you can create record ID for custom objects as well so Sankalp is asking if we if the button is added to account do we need to create a variable to get record ID like we did here yes so we created that record ID variable first then we placed that flow on button so that's why it was working if you don't create record ID variable and place your flow on the button then your newly created record won't be linked with that account so MEI is asking will you please create that deleted field from flow so I didn't delete any field after removed closed date okay deleted field you mean to say closed date mapping that I deleted I'm not sure which thing you are asking Akula is asking after removed closed date the record is creating how so I just showed you like I didn't refresh the screen at the time when I refreshed so it was not creating the record then can we create two column screen yes so Samiri is asking very good question like how we can create two column in screen so like quickly I'm going to show you that thing how we can create two columns so if I open the screen one so here we have a option it is like section yeah so if you place section so here you can see at right hand side you can select add columns so if you click on this add column so here we have two so I'm clicking and dragging and dropping opportunity in the first section and closed date I'm shifting in the second section so this way you can see in one row we have two columns like we have in the page layout right so if you click on it so this is field this is another field and if you hover above so this is for section and here we have two columns if you want third column as well you can add that as well okay if you want to include header so here you can see header is available which is having accordion and you can provide the label like please provide opportunity info so this way this label will be available so it is like making this UI similar to page layout and if you click on done save as save then activate so after activation if you come here and refresh so you will see that UI on front end so here you can see this way your flow is modified this is accordion you can just open and close the section and you can create more than one section as well if you open it so here you can have another section like if you search for section so you can just drag and drop it so you can have one more section right so on one screen you can have multiple sections so it is like similar to page layout okay so I hope this is helpful you can just try these two sections when you will be creating a contact screen flow or case screen flow so those are available in the exercise so at the time you can do this so we don't need to pass record ID in quick action like record page no we don't need to enable that checkbox that is happened automatically so you just need to create record ID variable in the flow when we choose freeform layout can we change again to auto layout if we need it yes umka so now I can do that for you so I'm just deleting it the section clicking on done and now I'm going to convert it because I just completed all the demonstration so this way you can see it is converted back into auto layout so ketan is asking about those two checkboxes that we saw when we created record ID variable so ketan basically the simple thing we are creating a flow if flow is receiving some value from outside of the flow so you will be creating a variable and you will be enabling this checkbox available for input and if you want to throw of a variables value outside the flow let's say through lightning web component or to apex class then you will be enabling this checkbox so right now what we are doing we are receiving account record ID into this flow right from record page or quick action so basically we are receiving ID from outside the flow so that's why we enable this checkbox right so I hope this makes sense and when you will be implementing this so you will be able to understand it more clearly okay so varicote is asking in the screen flow right side it has components and fields can you explain once so so I hope you are asking about this component and field so component we already used like if you if you search for any component like we use pick list we use text right so these we are using so these are the components which are provided by default and if you want to use fields so here fields are not available so here you can search record variable if you have created right and add record fields to your screen more info so basically right now this screen flow is not related to particular object that's why info is not available so just ignore this part you just need to focus on this component part because most of the flows will be implemented through this and I think this fields option is not available here let me just click on I because I also never use this so I don't know what is the actual purpose of this so this component we will be using for most of the flows okay bindo is asking we created only one variable record ID so here one more variable is available so bindo this variable is created automatically and this variable is basically storing the ID which is created after creation of this opportunity so whenever that opportunity will be created so its ID will be stored into this so it is opportunity ID you can see it it is opportunity ID and from create opportunity record it is created automatically so you don't need to create new variable to store opportunity ID it is created automatically but right now in this flow we are not using it it is created but we are not using it umka is asking in what case we need to choose variable in new resources so it depends on the requirement like in our case we we realized we need to receive record ID account record ID outside the flow so we created a resource so it depends and when we use to when we required pick list values to use in the flow so we created pick list choice set so by practice you will be able to know like in in what case you will be requiring a resource so that's why this exercise is important for you so if you go through with today's exercise you will be able to practice the things and only through practice you will become expert so flow builder is a powerful tool it is used by admin as well as developers and it is basically focusing on low code automation right so if you focus on this tool through practice only you will be able to realize like why we are doing things okay so archana in these two weeks session i am not going to focus on the deployment so deployment we will see whole together and i will be showing you how we can deploy from one developer addition org to another developer addition org because i don't have any like sandbox or production environment i have developer addition org so i will show you but if you want to deploy from sandbox to production so process will be saved so sunil is asking can we add background image okay let me just check whether this option is available so background image so for that yeah we have this display image and i think here okay so we have this option so i think you need to explore this so this way you will be able to display the image so you just you just need to figure out like from where you will be getting that image like source okay so just explore all these help text and through this you will be able to identify okay so we can do that as well so gabriel you are asking for enabling subtitles subtitles so i think if you enable subtitles in your youtube settings so you will be able to see those because i just tried that functionality but i was not able to enable that for the live session but i will try like if i will be able to enable once recording is available so check check it out at your end because i saw many viewers enabled that feature at their end so they are able to see the subtitles so very goody available for output will be used when you want to throw a value of variable outside the flow so for example if you have flow created and you want to connect that flow with apex apex class so if you want to throw your flow value to apex in that case you will be enabling that checkbox available for output because if you check that checkbox then only your variable will be able to throw its value outside the flow right so i hope i am able to answer each and every question so it took lots of time and if you have more questions so just ask otherwise i will be wrapping today's session and we'll be learning more flow scenarios tomorrow so tomorrow i will be picking more complex scenario and we'll see how we'll be able to understand that see me you are asking can we use for auto response rule so i think auto response rule runs in the background so like this is already an automation so i don't think screen flow we can use okay so thank you everybody so please show some gratitude and support and share my channel with your contacts and i i know like you all are passed out from renowned institutions so if your juniors need like videos related to cc plus plus java or sales force they want to begin their programming journey so please share channel in your telegram or whatsapp group so that i can grow along with you so my mission is your success and please help me to grow as well so that i can reach to many students okay so thank you everybody with this i am ending today's session here only thank you so much for joining today's session like i know this is a holy festival still you joined and i saw in today's session more than 100 folks were joining concurrently so it is great great achievement for me like in each and every session more than 100 like students are available concurrently so i will deliver more session with same enthusiasm and we'll be doing a lot for you thank you so much