 Hello. Hi everyone. I'm Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So today we are on day 17 of this Salesforce learning bootcamp and yesterday we started learning admin project. So this is part two of admin project and I hope you are already started implementing that project. So yesterday we implemented few steps. So today also I will be implementing few steps and if you have already implemented those steps, so while I will be implementing, so you can verify those steps. So if you can follow my speed, so you can implement with me, if you cannot follow, so just watch what I'm doing and then with the help of the recording and the document which I already shared with you, you can complete all the steps. Okay. So once again, hello to everyone. So let's start with today's session. So this is last session for this month fab and we will be having new month starting tomorrow. So like this week, this admin project will be completed and from next week, we will be starting sessions related to flow that is kind of part of local development. Okay. So moving forward, so those who just joined this project and not attending regular sessions. So for them, this slide is very important because you should know with whom you are interacting and who is your instructor. Right. So this is about me. So you can just know like what I have and what I can give you. Right. So this is the bootcamp timeline which I showed you yesterday and I'm showing you in each of the sessions so that you can have a trust in me. You can have trust in Sanjay Gupta Tech School because I just founded this organization so that you can have quality knowledge. Right. So along with this bootcamp, I'm also planning to launch bootcamps related to other technologies like data science, web development, app development, cyber security. So soon I'm going to launch those bootcamps as well. So I'm in connection with the experts and whenever they will be ready. So those bootcamps will also be started soon. Right. So we are in week week six and in this week six, we are going to complete our admin project. Right. And those who missed yesterday's session, please share the link with them so that they can also start and implement the project so that they can have proper skills so that they can have a job as a Salesforce admin or QA or BA. So for any role admin knowledge is required. If you want to apply a job in Salesforce ecosystem, so admin knowledge is very much required. Right. And those who are searching for the link of project. So I just provided that link in the description of this video. Right. So in the live stream, if you go to the description, you can find that document. Otherwise, that document is available in our exercise sheet as well. Right. So here this admin project link is available. So now I'm going to this project and yesterday we started implementing this recruitment app and I just created one object along with its tab fields and few records. And I added that tab into recruitment app. So today I'm going forward to implement other steps. So yesterday we implemented dependent pick list and I just showed you how we can create this days open formula. Right. So now I'm going to implement one more formula field that is for severity. Right. So basis on this days open, we will be calculating severity. So here you can see the description of this formula field. It says displays a text value of red, yellow or green. Now, what is the criteria if days open is greater than 20, then you need to show red. If days open is greater than 10, then you need to show yellow. Otherwise, you need to show green. And for that you will be creating a formula field named as severity and its data type will be text. So I'm going to create this formula field on position object. So jumping onto Salesforce org and like yesterday I was struggling to see days open. So let me just see whether I have that today or not. So I'm just refreshing this page. Yeah. Here you can see at the bottom days open field is available and basis on this days open. I'm going to create one more formula field. So moving to object manager. So now if I click on object manager, so from here under quick find, I can just search for position. Right. So my position object will be available here. So you just need to click on this label. So position object will be open. Then you will be clicking on fields and relationships so that you can create new field. And to create new field, we just need to click on this new button. Once you click on new button, so you will see all the data types. So we need to select formula because we are going to create formula field. Then I'm clicking on next. Now here I'm providing field label as severity. It's field name API name will be populated automatically. And from this list, I'm going to select text. And then next. So now here I need to create the formula. So in the question, you can see we have the conditions and for condition implementation, we need to apply if right. So what we can do here, I'm going to insert a function named as if. So I just selected if then clicking on insert selected function. So it is available here. Now here I'm going to apply logical test. Right. So my logical test will depend on days open. So from this insert field, I'm going to select days open insert. So this field is available here. Now if it is greater than equals to 20, let me check it again. Days open is greater than 20, then we need to populate red. So in this true part, I'm just writing red in double quotes. So if this condition days open greater than 20 is true, then red will be stored in the severity field. If it is false, so I'm removing this false part. And I need one more if condition so that I can check another condition. So I'm moving to right side and clicking on if and selecting insert selected function. So before selecting this if if function, I just clicked here so that it will be available here automatically. Okay, so this is initial condition. If it is true, then red will be populated in the severity field. If it is false, then this if condition will be checked. Now here I can apply one more condition. So it will be days open greater than and another condition is greater than 10. So if it is greater than 10, so in that case, I just need to fill yellow. And if it is also false, then green. So that you can write directly. So if days open is greater than 20, red will be filled. If it is false, then days open will be checked or compared with 10. If it is true, then yellow will be populated. Otherwise green will be populated. So this way you can implement your formula. And then you can just click on next. And I'm clicking on visible to all the profiles and clicking on next and saving it. So this way my formula field is created. And if I go to the UI and refresh the page so that formula field will display value basis on this days open. So in my or it is not visible right now. It will take some time. So I again refreshed. Still it is not available. Again, I'm refreshing. Okay. So it is not available, but it will be calculated as per this days open. So right now days open value is 27. So that formula field will be displaying value as red. Right. So let me create one new position. Let's see what happens. So if I create new position, so for example, I need to hire program manager. And if you want to fill job description, responsibilities, other field you can I'm leaving them blank. I'm just filling open date and I'm leaving rest of the field as is and clicking on save. Still that field is not available. So we just need to wait. If in your system, it is available, then you will be able to see the severity. Right. So I will be checking it later on. It will be available. So sometimes it happens like if you create something in the background, so immediately it won't reflect on the UI. So you can just do multiple refreshes and then it will be available. So someone is asking that formulas about that formula. So I'm going to search for severity. And if I open this, so from here, I am just copying this and I'm going to paste it in the chat. So those who missed, they can just copy the formula from the chat and you will be able to implement it now. Okay. Now moving forward, we need to create validation rules. So I hope everybody is familiar with validation rule. We implemented validation rule in one of the session. Yes, olhas that field is added to page layout because whenever we create any field, so it is automatically added to the page layout. But due to some cash issue, it is not reflected on the UI immediately. So that is not to worry. We just need to do refresh multiple time and it will be available. So now I'm going to implement the validation rule on position object. Okay. And those who are not able to relate what this project is all about. So no need to worry in between maybe tomorrow or day after tomorrow when we will be having few things implemented. So I will explain the beginning image end to end like what all objects are doing and why we are implementing this project. Right. So trust on me. Have faith. Right. Have patience and just implement whatever is being asked. Then we'll see end to end like flow how this is implemented and what each object is doing and how objects are related. Right. So first we are implementing the things and then we'll see like how everything is related. So next is we need to validate min pay should never be greater than max pay. So on position object, we have two fields min pay and max pay. So by any chance or by mistake, if you enter min pay greater than max pay, then there should be a validation rule applied. It should not happen. Okay. So I'm going to create that. So moving to position object then from this list at the bottom, I'm selecting validation rule and clicking on new. Okay. Again, I'm clicking on new. So here I just need to type rule name. So min pay should not be greater than max pay. Right. So here we have limits. So I'm just erasing this and setting it. Right. So this is basically rule name here. You cannot provide blank spaces you can use underscore. If you don't want to use underscore, then you can just start each word with capital letter. Right. Now here we need to build this condition. Okay. So here you just need to understand this carefully. If this formula expression is true, then error will be displayed. Right. So what we need to write if min pay is greater than max pay, then only a validation rule should fire. So I'm going to insert the field. So field will be min pay. So first time going to have min pay inserted if it is greater than max pay. So now I'm going to insert max pay. So if min pay is greater than max pay, then this validation rule should fire. So now I'm just clicking on check syntax. So no errors found and scrolling down here. I can just provide the condition. Sorry. Here I can provide the error message. So you can write min pay should not be greater than max pay. Right. And from here you can select the error location. It can be top of the page or it can be a field. So right now in validation rule we have two fields included. So in this case we can select top of the page and just click on save. Right. So this validation rule will work on record creation as well as on record updation. So it is being saved. So I'm just refreshing the page. So here you can see validation rule is created. I'm moving back to position object. If I click on validation rule, so it is available and it is active. Now if I go here, so whenever you implement something you need to test. So just add it a record and fill min pay greater than max pay and click on save. You will see this error. Min pay should not be greater than max pay. Right. And if you correct this value, then you will be able to save the record. Right. So this way you can just create your validation rule. Now I'm going to show you one more validation rule. So here it is another validation rule, which is a little bit complicated. So please understand it carefully. So the requirement says if the closed date is not specified. Right. So what does it mean if closed date is blank? So first I'm going to implement this part. If the closed date is not specified. So moving here, creating new validation rule. So we need to identify its name. So basically its rule name will be closed. It is not specified. So specify closed date or you can say validate closed date. Okay. So here I'm writing validate closed date. Okay. And here in the description you can write more details about that. Now here I need to select is blank. So I'm just searching for is blank and inserting it. So it is available here under expression. I need to insert the field. So field will be closed date and I'm inserting it. So it is available here. So first part is implemented. Right. So if is blank is available and you are providing a field, so it will check whether it is having some value or not. And like whatever questions are available in the chat. So first I'm going to implement a few steps. Then I will try to answer your questions. So keep on asking questions. I will take those questions together. So now this this piece is implemented. Now here you can see we have and and means both the conditions should should be true. So this part we implemented closed date is not specified through is blank. Now next is on status field. Right. So status is closed field or close not approved or closed canceled. So here you can see we have or in between and we have three statuses. So if closed date is not specified and status is anyone from these three. Right. Then you need to throw an error message. Okay. So now I'm going to put and the condition here. So and and then I'm opening a bracket then putting a comma and then closing this parenthesis. Right. And here I will be implementing second part of this and so this and is having first parameter as this is blank closed date after comma I will be implementing second parameter. But that second parameter itself is having three options or because we have or in between. So now what I need to do I need to write or then opening and closing bracket or parenthesis then inside this or I will be checking the status. Right. So for checking status we can have is pick well. Right. So this status is basically a pick list. If you go above so we created status field and status is a pick list. Here it is. Right. And if you want to verify a pick list value. So you can use is pick well. So here you need to provide the pick list field API. So that I'm inserting from here. That is status inserting it. So it is available and here I need to provide the text literal. So in single quotes I'm writing the text literal. So that text literal is closed filled. I'm copying it and I'm pasting it here. Right. So this is my first option for this or now here I'm putting or sorry here I'm putting a comma and I'm just copying it and pasting it then again comma and I'm pasting it. Right. So this way I implemented this or part which is having three options. This or is basically having three options. Now status field will be same. We just need to change these values. So now what I need to do next is closed not approved. So I'm copying it and I'm pasting it here then I'm again copying the value and I'm going to paste it here. Right. So this way you can see we implemented and for and this is first parameter and this whole is second parameter for this or we have three parameters. So from this or if anyone is true. So this or will be considered as true and for this and if anyone from this part is true and if your close date is blank then it will be fired. So if close date is blank and status is having any one value from these. So you will see a validation error and validation error messages close date is not specified. So we can write please populate close date. So please populate close date. So this will be your error message. Right. So this way you need to implement and you can implement this formula or this validation condition in different way as well. You can apply any like if condition and through that also you can do. But this is the simplest way to implement this. Right. So we just need to apply the simple approach. We don't need to apply complicated approach. And if you want to check the syntax you can click on this check syntax. No errors found. And now I'm just clicking on save. So this way my formula is created. Sorry. My validation rule is created and let me just check whether it is active or not. So it is active. Now I'm moving to UI. So here you can see close date is blank and I'm choosing status as closed filled and clicking on save. So you can see it is showing error. Please populate close date. And if I specify closed date then it will be saved. Right. So this way basis on closed date and status. We are applying our validation rule. And you can see I just updated close date. So days open formula field values automatically modified earlier it was 27. Now it is 20. Right. So this way things are working automatically. So I hope you understood this. Now we need to work upon the UI part. So here you can see if I open this record. So here all the fields are listed in a single column. It is not attractive. So I will be modifying this UI and I will be creating record types as well. Okay. So now what I'm going to do. So yeah, so people are asking formula to be pasted. So I'm just opening this validation rule and I'm going to copy this and I'm pasting it in the chat so that everybody can verify whatever you have implemented. Right. Now I'm moving on to the next part. So if you are not able to implement this validation rule, no need to worry. Just skip that part as of now and just focus on what I'm explaining because later on through this recording you can also will be able to implement. Right. So no need to hurry. No need to go in hurry because you have enough time later on as well. So whenever you find time, you can just go through with the implementation. Okay. And I will answer all the questions at the end. So we have just completed 25 minutes of the session. So let me complete at least one hour, 10 minutes. Then I will be picking all the questions. Right. So now what we need to do, we need to create record types. I hope you remember record types because if you want to have different set of fields on your layout, then we need to create record type and through record type, we can control the page layouts as well as we can control the pick list values. So if you see here, we need two page layouts, technical and non-technical. Now I hope you will be able to relate like we created position object and in a recruitment system, there can be two types of positions, one technical and one non-technical. And I'm taking example of IT sector. In IT, we hire technical people and we hire non-technical people as well. So basis on that, I just segregated this page layout into different sections. So section one will be information for both the layouts. Section two will be compensation for both the layouts. But here there is a difference working days. So for technical working days will be Monday to Friday. And for non-technical working days will be Monday to Saturday. This is just an example. Right. If you want different days to be available, you can modify as per your requirement. Then section three will be description. It is again common for both. Then section four is required skill. So here you can see for technical Java, C sharp, JavaScript and apex, these four checkboxes should be available on technical position layout and Excel PowerPoint world team building these should be available on non-technical position layout. Right. So what I'm going to do first of all, I will be creating the page layouts and then I will be creating the record type. So this is the best practice to create record type. First manage your page layouts and then create record type because at the time of record type creation, you need to map particular page layout as well. Okay. So I can see people are saying this validation is not working. So no need to worry. Just after this session try it out and still you will be having any issue. So you can just comment in the, you can, you can send a message in the video comment or you can use the telegram channel so that you can interact. Otherwise I will see whatever is the issue at the end of this session. So right now I'm going to create page layouts. So first I will be creating technical position layout and what I will do I will just manage technical position layout according to these sections and then I will be cloning that technical position layout so that while creating non-technical position layout, I don't need to do rework. So technical position layout will be cloned and non-technical will be just created and we will be doing some minor changes, right? So moving here clicking on page layout. So here right now we have position layout. So I am just opening it and I just need to click here beside save on this drop down and I'm clicking on save as and here I'm writing technical position layout, okay? And clicking on save. So this way my position layout is cloned and here you can see we have two layouts position and technical position, right? Now I can scroll down. Now here now here I need to arrange all these fields and I need to create sections as well, okay? So first section will be information and here we need to place position title owner status. So I'm just going to place them, okay? So position title is already available from here. I can search the field. So owner owner is already available. Then we need to place status location and type. So here we have status. So I'm shifting it above. Then we have location. I'm shifting it above. So I'm shifting it to right side. Then we have type. So I'm shifting it above as well, right? So this way you can just drag fields. Now before moving fields what I'm going to do I'm creating these sections as well so that I can shift fields into different sections. So first section is already available. Section one information is already available here you can see. So I'm creating section two that is compensation. Now how I can create section? So just scroll down and click here on section and just drag and drop. Now and you can paste the name here compensation and you can leave things as is and click on, okay? So you can see compensation section is created, okay? So now I'm going to create one more section after compensation and its label will be description. So I just copied the label and pasting it. So one more section is created. Now I'm going to create one more section and this section label will be required skills. And here I'm going to place this label and clicking on, okay, right? So these sections are created. Now I can simply place the fields, right? So in compensation I need minpay, maxpay and working day. So in compensation I'm just going to drop maxpay, I'm going to drop minpay and working days, right? Then these required skills, so in required skills what I need to do, I need to place Java so I'm just zooming out. So here in required skills I'm placing Java, then I'm placing JavaScript, then I'm placing C sharp and I'm placing apex, right? And these fields I don't require on technical. So Excel I'm removing, PowerPoint I'm removing, word I'm removing and team building I'm removing, right? Now you can see required skill section is created, compensation is created. Now under description we need to set the field. So job description, responsibilities. So here we have job description, I'm shifting responsibilities, then skill required, then educational requirement. So these I moved, then certification. So certification is also here, I just moved, right? And all these fields we need to manage here, right? So hire by this way, travel required, then here you can see close date, open date I'm keeping together, functional area, job level I'm keeping together, days open and severity I'm shifting here. So this way you can see how need and clear page layout is created, having different sections and each field is related to particular section as per the requirement. So in real time projects also when you will be working on different tasks, so you will be having these kind of requirement, tool may be different, it can be zero or any other software and you will be having specific requirement like how you need to design your page layout, having different sections and fields, right? So this way you just need to apply the implementation. Now I'm just clicking on save. So this way you will see two layouts, right? Now we need to create one more layout and we can just clone technical position layout now. So don't clone position layout, just clone technical position layout because here you already did all the configuration. So I'm just clicking here and I'm again clicking on the save drop down and here save as is available. And this time it will be non technical, right? So it is non technical position layout. I'm clicking on save. So all the sections will be same. So we don't need to create sections again. So here you can see all the sections are available automatically, right? We just need to change these required skills. So I'm removing these required skills from here, okay? And I'm just going to place Excel, then PowerPoint, team building and world, right? So this way this is non technical page layout, okay? So these are just sample fields. If you need to modify, if you need to add more fields, if you want to remove these fields and if you want to modify this project in your own way, so that is also possible, right? So now I'm going to save it. So this way I just configured two page layouts. So you can see non technical page layout and technical position page layout is available, right? So after creation of these two page layouts, now we need to move on record type creation. And you can see I just configured this section for basis on the requirement on technical, I just placed specific field on non technical, I placed specific field. And this requirement working days requirement will be controlled by the record type. So this working days field will be available on both the page layouts, but its pick list values will be controlled by the record type, because fields we will be able sorry pick list field, we will be able to control with the help of record type, right? So now I'm going to create these two record types, technical position and non technical position. Okay, so I'm just copying this name and from here I'm clicking on new and I'm going to create this. So label will be technical position record type name will be technical underscore position will be available automatically. If you want to provide any description you can write. So here you can write select to create a technical position record also I'm removing. And you can put any other description as well. So it is just for demo purpose. It will be available for all the profiles and default and I'm clicking on next. So in the next step, I need to select the page layout. So right now I'm selecting same page layout for all the profile that is technical position layout. Okay, so whenever at the time of record creation, if you select a technical record type, so this layout will be launched. And I'm clicking on save and new. So you can see a button is available, save and new. So I'm clicking on that. So save and new button is available at bottom right corner. So I hope you are not able to see that because of my picture. So you can just click on that. Now here we need to click we need to create another one. So I'm just copying non technical position. And here I'm filling it. So non technical position. And here create a non technical position. Right. And select this active. Don't forget to select this active at the time of second record type creation. And here you can make it default. Sorry, make it available for all the profiles. Don't make it default because default is technical. If you want to make default non technical, then you can select this checkbox. Right. So it will also depend on the requirement of the project. Then click on next from bottom right corner. And you will see this page. And here you can select non technical position layout. Right. So this way you will be able to create record type, then click on save from bottom right corner and record type and page layout are assigned. Now we need to do one more thing. So here we need to configure this working days pick list. So on technical Monday to Friday on non technical Monday to Saturday. So right now we are on non technical position record type. So here you can see working days pick list is available. So I'm clicking on edit. And from here I'm just removing Sunday so that these six days will be available. And I'm clicking on save. Now from here I'm clicking on record type and selecting technical position. And again I'm clicking on edit. And from here I will be removing these two. So five days will be available. And I'm clicking on save. Right. So this way everything is done as per the requirement. Right. So in projects there may be chances requirement will be not clear like this. So you just need to understand if requirement is not clear. You need to discuss with your architect business analyst or you can say BA or project manager whoever is responsible technically for that project. So you can discuss the requirement and accordingly you will be implementing. So number eight is implemented we created to record type two page layouts. It is configured. Right. Now I'm going to test it out. Okay. So first of all I'm refreshing the page and it is not modified because all the existing records that we created they belongs to master record type now. So once you create record type and if you have existing records so those will be related to master record type and that master record type may have different page layout. So let me show you that as well. So if you go to record types so at top right corner you will find page layout assignment. Click on that button and here you will see the assignment. Right. So see this carefully. We have three record types master non-technical and technical. So for existing this master will go for new ones non-technical and technical will work. Right. So now I'm going to create new position records. Okay. So first of all I'm refreshing the page. Okay. So first I will be creating a technical position. So in my organization I have a requirement for a technical position. So here you can see record type is available. Description is also available. So by default technical position record type is selected. So I'm clicking on next and you can see page layout is available in the format we designed information section then we have compensation then we have description and then we have required skills. So with this you can create a record. So I need application architect for one project. So I'm creating this position so that in my organization my recruitment team can hire this can hire a person for this position. Right. Then you can select the status like it is new position. So for the first time I'm going to create this record by filling most of the information. Right. So you can choose location then you can select the hire by date like by which date this resource should be hired. So you can you can fill the expected date. Let's say 22nd March till 22nd March. This resource should be hired type like full-time part-time internship contractor. So you can select as per the requirement then you can select open date. So we are opening it today. So open date then like hire by 23 if not then you can select close date as well. So let's say close date is also 22nd. If no person is available till 22nd March then position will be closed functional area. You can select it because architect role is related to it then here we have job level. So this is dependent pick list. So only it related. So this 100 200 300 and 400 is basically for experience 100 beginner then intermediate then like experience more experience than more experience. So this is some identification digits. So let's say it-3 double zero and then min pay max pay. So you can propose min pay and max pay. So let's say 100 K and here I can write 150 K. So recruitment team will be negotiating between this range then working days you can see five are available here. So you can choose like I need that resource for three days only. So you can choose these days then job description. These you can fill as per the requirement. You can write required certifications then you can provide required skills. So let's say JavaScript and apex and then click on save. So this way a position record will be created and you can see how neat and clean this layout is all the information is available in different sections. Now here you can see severity is also available. Earlier it was not available. Now days open is 22 because we created it on 28 Fab and it will be closed by 22nd March and number of days 22 and severity is read. So as days open will be more than 20. So it will show the severity. Right. So this way I hope you understood how we created record types and how we configured the page layout. Right. So this I created for technical position. Now I'm going to create one more record for non technical position. Right. So I hope now you are able to relate like why we created this position object so that in an organization if you want to hire any candidate for particular position so you can create a record for that position and basis on that your recruitment team will be working. So here I'm writing sales executive status new position part time then hire by I am leaving unfilled. So we don't have any targeted date. Right. Functional area finance not no finance. It will be retail operations. Let's say beginner level and then here you can see six days are available because we controlled it through. So I'm just having five days selected and min pay for example 50 K and max pay 80 K and you can fill this description then these are the required skills and I'm clicking on sales. So this way my non technical position layout is also created. Right. Now there can be a question how we can identify this record is related to technical or non technical. So answer to this question is we can have a field named as record type populated on both the layouts. So what I'm going to do here I'm clicking on page layout opening technical position layout. So here you will find a field known as record type. So here you can see this record type field is available. So you can just search it here and you can place it at top and so you can just click on quick save so that it will be opened and you can immediately test it. So I just placed it on technical. So I'm opening this application architect and I'm going to refresh the page and that field will be available on the layout. Here you can see this record type is available which is showing technical position. Right. If I go here now if I want to change non technical page layout so instead of closing it I can just use this pick list. Here I have this option non technical position layout and again I'm searching record type scrolling down and I'm placing it here and I'm clicking on save. So this way I just configured it. Now if I open my another record and refresh the page so I'm going to open sales executive and here you can see record type is available as non technical. Right. So this way I hope you understood this step. Okay. Now along with this I'm going to show you how we can create this compact layout. So basically compact layout is this. So here you can see for this position we have this compact layout and it is having only one field. So I'm going to configure this. So here we can see we have to design a compact layout and we need to assign these fields position name or number whatever we have created status higher by and job level. So moving here. So here you will see an option compact layout. So just click on it. Right now it is system default. So I'm going to click on new and I will be creating new compact layout. So from here I am just selecting the name. Okay name is not given. So I am labeling it as position compact layout. Right. Now from here I need to select the fields. So first one will be position name. Then we have status higher by and job level. So status then we need to place higher by and then job level. Right. And then click on save. So this way compact layout is created. Now you need to click on this button compact layout assignment. And from here click on added assignment and you can choose this position compact layout from both the pick list and save it. Right. So if you click on save so it is saved and you can move here and just refresh the page. Okay. It is not reflected. I'm refreshing it again. Still it is not reflected. So I'm going to open another record refreshing it. Still not available. Okay. Let me just check whether it is applied. Yeah. It is applied. So right now position compact layout is the primary one. So again you can see it is taking time. So it happens whenever you implement things. So if you refresh it won't be reflected automatically. So let me create one more position. So non-technical next. So I'm just filling the title and creating it. Okay. Still that is not available. So it is right now not updated compact layout. Yeah. Now it is updated. So here you can see under position we have position name then we have status higher by and job level. Earlier it was not available. If I go to existing one there also it will be available. You can see. So this is the compact layout any specific field that you want to show on top of the page. You can just show it right. So it will be helpful for the recruitment team so that they can just see this high these highlighted fields and they don't need to search particular information in full page. Right. So this way we are able to complete this. Now we have one more requirement. We need to create a lookup relationship field named as hiring manager. So field label will be hiring manager. You need to create it on position object and the parent will be user object which is standard one. Right. And you need to put this field in the information section of on both position layout. Right. So I'm going to create it. So clicking on fields and relationships clicking on new from here I will be selecting lookup relationship and clicking on next from here I need to search for user. So I just selected related to as user then clicking on next. Now this field label should be hiring manager. Okay. So if you have already implemented it and if you placed this label incorrectly. So you need to modify that if you haven't implemented. So I think you're watching this and you will be implementing implementing it accordingly. So this is available in the requirement like field as hiring manager. So this is the label on position object and it will be related to the user object. Okay. Now click on next visible to all the profiles click on next. Now here you can see we have three page layouts. So all three are listed here and we need to place it on two page layouts. So from here I am going to uncheck position layout and it will be available on these two technical and non technical. Right. Now I'm just clicking on save and that field is created and it will be available on both the page layouts. So if I go to the UI and refresh. So maybe it will take time or maybe available immediately. Yeah. It is available immediately. So here you can select the hiring manager as well like who is the hiring manager for this position. Okay. And if you added this so you will be able to search people. So I'm selecting test user and saving it so that recruitment team know like who is the hiring manager for this position. Right. So this way we added this field and it is available on the page layout. Okay. So this position object piece is completed. Now we need to move to this next object. So I'm going to create this quickly as you can see we have lots of fields. So what I'm going to do I will be creating object tab and few fields and then rest of the fields we will be creating in tomorrow's session. Right. So I think I'm just explaining each and every step in detail. So that's why it is taking time and if in four or five days this project implementation is not completed. So maybe we can stretch it for one or two more days because I just want to give you enough information because I'm just targeting all the beginners if they are having any issue on any step. So that should be resolved. Right. So I'm going to implement step number 11. So we need to create new object named as candidate. So I'm going to create it. So clicking on object manager and from top right corner I'm clicking on create and creating custom object. So here I need to provide the label as candidate. Plural label will be candidates. Right. Now if we see this requirement carefully. So here record name should be candidate number. So at the time of object creation you just need to see this record name. It is candidate number and it is mentioned like it should be auto number. Okay. So it should be auto number and the format should be like this. So from here I'm selecting auto number providing display format. If you want to read about these display format, click on this. What is this? You will see lots of formats and accordingly you can choose and starting number will be one. Then I'm going to allow these options and this time I'm not selecting this checkbox. This time I'm not selecting this checkbox. So tab won't be created immediately after object creation. Why I'm doing this because I want to show you another way of tab creation and how we can add that tab to recruitment tab. So I'm just going to click on save option which is available at the bottom. So you won't see tab creation steps. If you have created with this way so that is also okay. But I just want to cover both the aspects. So it is just saved and here you can see object is created. This is the API name having underscore underscore C then if we go to fields and relationships or some standard fields are created. Now if I move here, okay, no, we need to go to home and we need to create a tab. So here you can search for tabs. So I'm selecting tabs and from here I need to click on you. So you can see custom object tabs are available and candidate tab is not created yet. So I'm clicking on new and from here I'm going to click create. Sorry, I'm going to select object as candidate then I need to select tab style. So any tab style you can select I selected headset and then I'm going to click on next. So it is asking for tab visibility. I'm keeping it as default on and from bottom right corner clicking on next. Now this is important. Here we need to select the application where we want to place the tab. So I'm unchecking all the options and I will be selecting recruitment app checkbox which is available at the bottom. Right. I selected this checkbox and this checkbox is for recruitment app. Right. And at bottom right corner, you will see save button. So click on that and now here you can see a tab is created for candidates object. Okay. And it is also placed on the application. So I'm moving to the application and refreshing it. So here you can see along with position candidates tab is available. But here right now we don't have any record. So it is just blank. Right now it is a placeholder and when we'll be able to create fields then that object will be able to create records also. Right now position and candidate is created. So if I take you above in the beginning to understand the relationship. So if we take an example of any organization, let's say Sanjay Gupta Tech School and I need to hire any person. So in my organization, if this app is installed, if I'm using sales force as CRM. So what I will do or any any person from my organization, they will be creating a position. Right. Technical or non technical. So for whatever positions we want to hire candidates, the those position records will be created. And we will post that position open position on social media platforms and we will be receiving some candidate CVs through reference or through emails or whatever ways. So shortlisted candidate records, we will be creating on under the candidate object. Right. So position object will be having all the open positions or close position or whatever position we have. And all the shortlisted candidate records will be available under the candidate object. Right. Later on job application object will be a bridge between these two. So this job application will be having information of position as well as candidate so that we can apply the interview process and that process will be done with the help of review objects. So this way these objects are related. Right. So maybe tomorrow and day after tomorrow when we will be creating these objects, so you will be having you will be understanding the proper relationship between these objects. And then we have job posting and employment website objects as well, which are like directly related to position object. So this way total six objects we need to create to implement this project. Okay. So I think this is it for today. And now I'm going to answer a few questions. Those are available in the chat. And I'm assuming like you are implementing this project and you are enjoying implementation as well. And as a beginner, if you want to master your admin skill, this project is very much important. It will give you enough confidence. And if you are ahead from me, so just join these sessions or watch the recording so that you can verify whatever you have implemented and to understand the end to end process because I'm just implementing everything from the scratch. Right. And we we I'm not in hurry and I hope you are also not in hurry. You want to understand everything related to Salesforce and detail. So that's why I'm just trying to help everybody to understand each and every concept in detail. Right. So I hope now I can take questions. So if you have any questions, so you can just type it in the chat. And if you don't have any question, so you can just leave and you can implement few steps yourself. And in tomorrow's session, you can verify whatever you have implemented so far and make sure whatever you implement, just try to test it through proper record creation. So there is one question like what what skills are required for QA. So for QA, basically you need admin knowledge. Development knowledge is not required. So you need two types of information. One is admin knowledge and one is cloud specific knowledge because as a QA, you will be testing particular clouds. So you if you are working on sales cloud, you need to know sales cloud. If you're working on a service cloud, you need to know service cloud. So I think Priyanka, this is the answer for your question. Yes, I will try to take community cloud sessions as well. If I'm not able to, I will arrange any expert for you. So initially, I'm targeting on admin and development and lots of folks are asking about integration sessions. So I just connected one expert. So soon, like in in development sessions, one week, I will be dedicating for integration related session. So I'm considering each and everything in mind so that I can give enough knowledge to you freely this year. Yes, Vishal, web development and data science both are hot topic right now in the market. So I will try to arrange those boot camps as well. So Vishal, if your formula field is not working, so I would prefer like please connect with anyone so that you can discuss things together. Yes, first, I already told you integration related sessions will be in future. Okay, so now so there is a question from Kishore, what is the best practice for validation rules? So best practice will be like your validation rule will be simple. If you have any complex validation rules, so it should be divided into separate lines. You should provide proper description so that any other developer can understand what you have implemented. There should be proper error message and you should test it thoroughly for record creation as well as for record updation. And if you have any requirement like your validation rule should work for particular profile or particular record type, so you can apply those checks as well. So I'm going to see more questions. So there is one question, is it possible? So Abhishek, I'm not getting your question. So you say you're saying I have idea that sir have done it by using duplicate records but I was just wondering it. Okay, I think you already got the answer. We can use position name for title. Okay, I can't see proper questions in today's chat because everything was very easy. So let me see one more time. Alex is asking please start development. So Alex be with me from next week development will be started. So first I will be picking flows and then apex. Yeah, yeah, Abhishek, if you copy paste so that comma comma or single quote or double quote pattern will be different. So you just need to remove and you need to retype them. Isha welcome to this bootcamp. So this bootcamp is for beginners only. So you are on right place. Jigna. Thank you for meeting your requirement. Manisha. Thank you. Isha same time every session is happening on 8 30 p.m. IST right. So you can find session tracker link in the description of each bootcamp session recording so that you can follow the sessions. So the hiring manager is not populated automatically. I just edited the field and I selected a user record. So you can do that as well. Vira. Thank you for appreciating my efforts. Vamsi. Yes, I will be explaining LWC and integration. My friend will be explaining. He is preparing the content. So I will pitch in him in between. Alex. Thank you. So people, those who are still live or maybe if you will be watching or you are watching the recording, you can see Alex is saying because of me, he got a placement. So have faith in me, have faith in my sessions and all the courses that I'm providing for you. So if Alex got the job, so you will also be getting the job. So I appreciate your efforts, Alex. Enjoy the time. So she is asking page layout versus record type versus permissions at which one choose first. So first you can create page layout, then record type and then you can choose the permission set. Yes, Asit will be helping you on release and deployment sessions. So those are related to DevOps. So I will be arranging DevOps sessions as well. Bhozraj, thank you for appreciating my efforts. I am totally committed and dedicated to this whole Salesforce ecosystem and IT world. Thank you, Anuj. Yes, Pallavi, you can inactive record type. Varan Dube in record type junction object is not visible in record type junction object. I didn't get your question Varun. Deepa is asking, I'm watching your flow videos. How