Understanding Validation Rules in Programming

Next topic validation rules right so how many times you have completed a form on web or anywhere online or on computer a lot of times so like when you were like when you were trying to When you were trying to enter your email and you went down at gmail.com and you tried to submit it, what did it say? The email is not in the right format. Okay. So when you try to enter the phone number, which was not of 10 digits, then what did it say? The phone number is not correct. When you entered an email or a name in which you accidentally entered a number, what did it say? Like, can there be a number in a name? No, right. So when, if you accidentally accidentally put a number into a name, the form says the name is not in the right format, right? This is what happens. So these are particular checks that are placed onto these forms and everything so that the data that gets entered into the database is validated and is right according to the standards of our business. Getting it? Yes or no? So validation rules, listen to this very carefully. Validation rules are used to validate whether the data is right or not or is according to the standards that we have or not. So that not anything can be entered into your database. You want the records to be created and the record should have values in a particular way, in a particular format or according to a particular standard. And for that you will implement a validation rule on that object which you want to validate or which you want to Yeah, on which you want the data to be standard. Getting it? Okay. So listen to me and see as well over here. Give me a second. Yeah, this is my ink. Okay, validation. So whenever you save a record, it goes to the validation rule. And validation rule has got only two things. Number one. is a formula and number two is error or error message you can say right so whenever you save a record it goes to the validation rule and evaluates this formula it evaluates this formula and this formula can only return one of the two things true or false It only returns a boolean value which is true or false. Listen to this very carefully. If it returns a false value, then what will happen? Okay, it's the opposite in here. and if it returns true then the error message will be shown getting it so in validation rules you write a formula which evaluates to true if the error should be shown and which evaluates to false if the there's no problem in the record and record should get saved into the database Good with this? Okay, so like let's say if I if I'll give you a situation you guys have to write down a formula now right now in your notebook and I'm going to check it right now and again that thing will happen if it is wrong. So the situation is listen to this very carefully. Whenever you're creating a student record the registration fees should not be less than 5000. If it is less than 5000 then the error should be shown that the student. registration fee should at least be 5000 or more than that but it cannot be less than that. So write down the formula for this. Write it down. You guys also write down in the chat. I'll check it. So the thing is no student can get registered unless the registration amount is 5000 or greater than 5000. So easy guys, how much time do you need to do it? Done? You have to write down all the problems. You do not have to write down the same or the other. You do not have to write down the same or the other. You just have to write down the condition. Just write down the condition. Registration fee is less than 5000. Exactly. Registration fee is less than 5000. Exactly. So many of you have written registration fee is greater than 5000 or greater than equals to 5000. So guys, you are right when it comes to that, like when describing the requirement that it should be greater than or equals to 5000. But as I told you that in the case, if it is true, it will show an error. And if it is false, then it will show, it will save the database. Save the record into the database. So if the formula is registration fees is less than 5000 and imagine you are entering 4000. So is 4000 less than 5000? True becomes error and if you enter 6000 then 6000 is less than 5000. No, false. False is record gets saved into the database. Make sense to everyone? This is how validation rules work. I think there is something on the chat. All the guys who are not participating in the chat make sure that I have to review or give your feedback as well. I am going to give you less numbers. You are not going to get more numbers if you are not participating in the chat or the question that I am specifying over here. I've got by the way, you will the certificate that you will get from here from S2 labs. And it's not more about certificate, but it's more about learning. But even if even into that, so like you've kept it this way, that your assignments, your tests, and your class performance will have a serious impact on your score at the end of this course. So please make sure that you're maintaining all three of it and you guys as well. I know you want to learn. I do not want. that certificate whatever that is but it's better for you to participate into questions like these and if you that that's that's how you learn and no one else will give you these opportunities later on so utilize the best of it Good. Are we good with validation rules? Okay. Now, I'll give you a situation. So, let me tell you first of all, validation rules are not that easy. You just don't have to check that registration fees is less than or greater than or something like that. They are more complex many a times. So, I'll give you a situation and you'll have to write down a program of it. Whether you can call it in C, in Java or whichever language you know. And you have to write it down like this. Let me explain it to you. The return type of this program would be Boolean and Val check. Let's say Val rule 1. And it is taking two arguments. Number one is what? Registration fees. And number two is course. Opted right you have to write down a program in here Listen to this Listen to the condition and if you want to write it down you can write it down as well so that you do not get Confused if if the student is registered if the student is registered in any other course in any other course then salesforce admin then salesforce admin salesforce developer or big data or big data then the Registration fees, then the registration fees should be, then the registration fees should be at least 5000 or more than that or more than that. Else it can be anything at least 5000 or more than that, at least 5000 or more than that. Else it can be anything. It can be anything. Write down the formula. Write down the program. Whatever you want to write it down. And show it to me. Opt it. I don't know any programming, no worries. You just have to write down the in condition, that's all what is required. You do not have to know the complete programming. And if this condition is there, return true if you want the error to be there. And if this is the condition and you want the report to get saved, return false. That's all what you have to do. Thank you. Let's go. Hi, I am Gaurav. I am working in a company. I am trying to get a job. Let me rephrase the question. Let me tell you what the question is. The question is, if the student is registered into Salesforce admin or Salesforce developer or big data. then in that case registration fees can be anything. Yeah, okay read it out. So am I right? You sure? Yeah, I am right. I know. So the thing is, if the student is registered in Salesforce admin or Salesforce developer or Big Data, then in that case registration fees can be anything. But if he or she is not registered into any of these three courses, then in that case, registration fee should at least be 5000 or more than 5000. Now do it. Do it the other way round. Done. I hate this thing that you guys optimize it. I want the syntax to be right. My brain is compiler. I can find out the mistakes. Like you have done it. All 10. Cannot do it in any program in Android like that. You have to again write down course object equals to equals to. Then again course object equals to equals to. Logically let me see. I haven't seen it. Again compilation is not very much simple. The first step that we do is we ask the person, do you know the reason how he can skip something? We ask the person, how can he do that? I heard it. What about this? It's very exciting, but what about other stuff? What is it that you want to do? I want it, but what if they say follow? ............. This is the first time I am seeing this. I am sure it will come inside. After coming inside, this station is 3500 feet. Now I have 6000 feet. I can see 4500 I have made a mistake in the story. This is the software we use and we are using it for testing. After that, we will see how it works. We will test it on the Android 6.0. We will test it on the Android 6.0. It will work. Here, the next thing is false. False and true. What are the reasons for the data? Return R-E-P-U-R-N space F-A-L-S-E You don't want? Only when you are in the market, once a month. You see? You are showing it either way. And for the resident case, it's a greater problem. Who knows? Mali. It's really hard. It's difficult. Hey, I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. Shall we move ahead with this? Shall we move ahead with this? Hi! I don't think you guys are... 2 if and 3 else Before that there is Harshita Harshita has sent me something Let me see if it is correct or not If a course opted in Salesforce developer Then if registration fee is greater than 5000 then return false greater than equals to 5000 then return false and no its not correct because what if someone has deposited 4000 and is registered for syswithadmin I don't want any error I don't want any error over there its not correct Hatsuka So I've checked the one course is going to Salesforce. First, if student is equals to course one common course to print. No, it's not about printing. It's more about writing down the conditions. Okay. Boolean. Okay. Boolean value check. Return false. Then else return false. Like I think there should be then and return something and else return something. else if registration fees is less than 5000 then return true else i think it's good if they shouldn't have been this else if you wouldn't have written this else uh before return false then it's correct harshita jeel of course operated uh sales admin dev and big data then falls good else register fees less down to good jeel it's it's correct uh vijay if course operated degree uh comma of course degree comma course update i never asked for degree Of course I have written SF, Dev, Big Data, Then, Then, Else, again you have written Then, Else, you have copied the one from Harsita. Don't fool me. It is the same. Nakal may be akal ki chara chate if you understand me. Okay. Okay, so let's see how we are going to go forward with this. Boolean well check there was there were two fields that was supposed to come in here like this right and Now what I have to write down is if sales was added if course opted double equals to Salesforce admin or later if course operator goes to sales admin course operator goes to sales developer or course operator goes to big data then it's simple you have to return false Because no matter what the registration piece is, there will be no error. Even if the student is depositing 5000, 8000 or not depositing anything, 0, 2000, 1000, it doesn't matter if they are in one of these courses. Now, let's talk about if they are not in one of these courses. Else part. If they are not in one of these courses, then the first thing that we have to do is check what is their registration piece. registration fees is less than 5000 then in that case return what true because there should be an error if the registration fees is less than 5000 else and that's what your program should be or should look like okay now now now now so all of you are uh are struggling at one position which is that position let me tell you to create the logic and once you create the logic the the next problem that you guys are facing Identifying that whether this logic is correct or not. You are like, okay, I think it is right according to me. Let's show it. No, you have to validate it or check it on your own. And let me show it to you how you need to check it. Give values on your own to both of the parameters. Okay, registration please tell me any random number. 5000 or 6000? 6000? And then comes course opted. what should be the post object? Salesforce admin? Okay. So if someone is depositing 6000 with Salesforce admin, let's see whether it will give an error or not. And before that, let me write down something. If we are returning false, then it equalates to save. And if we are returning true, then in that equivalence to error is it clear okay now these are the inputs 6000 and sales with admin so course update is sales with admin so this condition gets true right and it will not check the next one because there is or there is not and right so it will go and return what so it will get saved into the database this is exactly what we want okay now let me change the amount it's 2000. Now let's check it. Course update is used to Salesforce admin. It will return false. And this is exactly what we want. If the course is Salesforce admin, no matter what the fees is. So it is getting saved. No matter what the fees is. If I make it zero, then also same thing. Every time it's same thing. Okay. Now let's go and try on big data. So, course update is equals to salesforce admin. False. It will check the next one. Course update equals to salesforce developer. False. It will check the next one. Course update equals to big data. True. It will go to and return false means. This is what we want. Sure. Okay. If I will make it 1000 then again it will get saved. Why? Because course update equals to big data and return false means saved. That's it. Okay. Now let me change the situation. Android and 6000. So if it is Android, then course of it equals to equals to sales for admin. Is it true? False. Course of it equals to equals to a sales for developer. False. Course of it equals to equals to big data. So it will not go inside this block. It will go to the else block and an else block. the first condition is if registration fees is less than 5000 so 6000 is less than 5000 no so it is false and it will not go inside this it will go into the else part and in the else part it will return what and false means safe now one more thing if i'll make it 3000 now tell me it will go to if course update so android is going to salesman admin no android is going to salesman no Android is going to be data. No, so it will not go into this block. It will go to else block and an else block. There is again one condition registration fees is equal to 5000. So 3000 is less than 5000. Yes, and that will go into this block and execute this. And when we return true, what happens? An error. So this is what we want, right? If the course is other than Salesforce admin, Salesforce developer, big data. then the fee should at least be 5000 or more than that otherwise the record shouldn't get saved but if it is sales admin or sales developer or big data then it should get saved no matter what the registration piece is is it correct we have checked it in every situation now let's take it on 5000 what will happen in this case it will go into this first sales block and 5000 is less than 5000. So it will return false. So it will get saved. So that's how you need to check your own logic. So first you have to create the logic. And I'm actually, okay, by the way, you might be thinking that what I'm doing over here by putting so much time into this validation rules topic, let me tell you, this is the most important topic for all the administrators, for all the developers, for all the app builders and everyone. Because it's all about logic. Everyone can understand the concept. Everyone can read the books, but it's more about implementing in this industry. And the more hands-on you do, the more practice you do, the better you become into this. And I want you to become the best. And that's the reason I'm putting you guys into these situations. which no one else would. So make sure that you're trying to get the best out of it instead of just sitting and trying to, I cannot do it. I think, I don't know how to do it. Just try it for a minute. I don't know. You shouldn't do it like that. Try to create more and more answers, no matter how many times it is going wrong. You can check it on your own by just putting onto these values. What if the value is this? Then will it work fine? What if the value is this? Will it work fine? And that's how you need to create your logics. Is it clear? So first you need to create a log. So first you need to be a developer and then you need to be a QA. Testing your own thing, right? Whatever you have developed and how to test the things by giving the particular input. So if I want to test this remote, how I'm going to do that? When I click onto this button, the AC should get turned off. So I'll click onto this button and the AC, if it will get turned off, then the remote is fine and it will not get turned off. Then there's some problem in the room. That's how you need to do that. Does it make sense? Everyone in the chat got it. So happy that you got it. Any questions in the chat? No? Good to go? Are you good to go in here as well? Okay. So we understood how to implement, how to think about the logics and everything. Now is the time to implement the validation rules in our Salesforce data. Let's do this. Sure. Sleepy. Sure. We need to implement validation rules. Write down the steps to implement validation rules. Setup, object manager, then the object on which you want to create. Which object is it? Student. And then click on validation rules. There was validation rules in here. Click on validation rules. And by the way, you can create as many validation rules as you want on a single object. There is no problem with that. Get it? First let's create that one, right? Registration fees check. Simple one. So there are only two things. This is formula and this is error, right? So what should be the formula? Registration fee should be less than 5000. If you are not talking about this, I'm talking about that one. The first one that I asked you to do that right. Registration fee should be less than 5000. If you put that condition then it will always be more than or equivalent to 5000. Getting it? So how I'm going to do that? I'm going to insert the field. Over here, if you can see, where is it? Initial P it is, I guess. Initial P. I'll insert it. And then the operator. So see how much point and click it is. It will not give you a feel that you're coding. Yeah, you are. Initial piece is less than, checks and texts. See that you do not have to remember the name of the field. You can get it from here. And what is this? Initial underscore piece underscore underscore. Initial underscore piece we understand. That's the developer name. Whenever we write down any space between the label. When we created that field, we entered the label initial fees and like there was a space between initial and fees and then that underscore automatically gets added because there cannot be a space in the variable name in the code. So over here it's initial underscore fees. But what's the matter with this underscore underscore C? Exactly. Underscore underscore C always defines or always denotes that this is the custom field or a custom object. So in this case, it is a custom field. Is it clear? So and less than 5000. No errors found. And what should be the error? If the fees is less than 5000. I want to show it on the top of the page or in front of the field. I want to show it in front of the field. I'll select it like that. So if there are more than one field involved then show it on top of the page. If there is only one field involved then in that case show in front of that field only. And it depends on you. It's your choice. Save. Now what? I'll go and create a student. Name. Initial fees, I'll keep it 3000. I'll save the record. Legislation fees cannot be less than 5000. I'll make it 40. No, I'll make it 5000. Save and if I'll make it 6000. So, that's how easy it is. I hope it makes sense. So you now know how to implement validation rules. Now let's create another one. Again, I'll go to the object manager and go to the student object and over there I'll click on validation rules. And I'll implement the one that I want. So like, like I can create as many validation rules as I want, but I want to modify this one. Otherwise it will conflict because there is registration fees or initial fees involved. So let me change the formula. Okay, now the question is, if the course is Salesforce admin, Salesforce developer or big data, then in that case, there shouldn't be any error. And if it is other than that, then in that case, the registration fee should be equal to 5000 or more than 5000. Otherwise, there should be an error. That's what it is. So we have already created a... Program or a code for that. You just need to replicate it. You just need to replicate it And by the way, it's not the it's not always like you have to create it in any other programming language And then you have to replicate it over there This is just one of the ways in which I have made you understand how to do this You do not have to do it in the same way You can directly go and create the validation rule over there right over there But that's a little difficult to create it right over there because you guys are I guess I think that you guys are experiencing some of the programming languages like C or C++, Java, whatever you're experiencing. So that's the reason I created it over here first. And then we're going to make it work over there in the Salesforce validation. Does it make sense? So the first thing that I have to write down is if condition right over there. So over here, if it's not a statement. In C in Java, if is a statement over here, if is a function, and where are the functions? Here are all the functions. So your job for the day is you have to read each and every function about each and every function in here, you have to understand each and every function which is given in here and how you're going to do that is help on this function, you'll have to click on this link, and you'll go to the help and you'll read about it about each and every function. So currently we're talking about which function I'll search if what did it say what it says let's read it if first logical test comma value true comma value false so let me show it to you how what it means and how it works so if I'll insert it I can insert it like this if logical test value true value false Let me tell it to you how it will go. You guys able to hear me? Let me know if you are not. If condition true block Else false block. So in languages we write it down like this. First we write down the condition and if the condition is true then whatever you want to execute write it down over here and if it is false then write down whatever you want to execute over here. It makes sense? Okay now let's talk about how it is relevant to that. relevant to the function that we got. So over there, there is something called as logical test. You can see this, let me annotate it. There's something called as logical test. So this logical test is equivalent to the condition, right? And this value of true, let me just show it to you. So these are separated by a comma. So after first comma you have to write down the true block. Whatever you want to execute in that if that condition is true or if that logical test is true. And then there is value false. So in value false you have to write down the false block. You got it? You are able to relate with this? You sure? Everyone? In the output in Boolean form, output in true or false, not in S, always. So that means you have not created the validation rule in the right way. There is a problem in your logic. Give me a scenario. Who is creating the validation rule? Fire the developer What else can you do? Not the whole database but the records which gets inserted wrong Yeah so fire the developer I agree but fire the developer That's the only choice that you have got because he is not proficient enough in his profession or he's not capable enough of doing his own his or her own job and that's the reason i want you guys to grill over here rather than grilling over there and creating wrong formulas confusing yeah you have to yep so that's the reason i'm putting you in these situations so that you you get it into your head that true is always No, no, true is false. True is false. True is error and false is same. Right? True is error and false is same. You need to get it into your head. And that's the reason I created that diagram as well. So that you understand it very well. And if you'll not, you might get fired. Make sense? Okay. Yeah. So the false block after the second comma, the true block after the first comma, and the condition. just after the bracket or just after the parenthesis. So in this case what will be the logical test? What will be the logical test? Tell me. Course update equals to equals to Salesforce admin or course update equals to Salesforce developer and all of this stuff. So let's do that. Where is core software? Core software now operator equal salesforce admin Now what? or again you have to write down the same thing data got it if I want I can wrap up this condition into one as well like this there's no need but if you want you can do that so this is the condition and then if this condition is true what what do we need to do return false so over here you do not have to write down false return but you can just write down false and it will return the false value automatically. Is it clear? Okay. What if this condition is not true? Then again, again, if blocks over here, I should put another condition. You sure? If insert. Good. And what should be the logical test in this? Initial. Yes, yes. Initial piece is less than. If it is less than 5000 then? True. Else? Right. This is what it is. If you'll see, this is what we're doing. If registration fee is less than 5000, true. Else, false. Are we good with this everyone? Everyone in here? Everyone in the chat? Let me know. I think there are some messages that I'm missing out. If course operator is false, yeah, you're absolutely right. So that means if the developer big data falls, if initial piece is less than 5000 true or false. What else? Yeah, that's it. So shall we click on checks and texts? We're done with this? Okay. Someone was saying something. Error. First update is a picklist field. Picklist fields are only supported in certain functions. So listen to this. We cannot compare the value of a picklist field with the help of equal operator. We cannot do that. There is a different function to do that. And the name of that function is isPickVal. IsPickVal is picklist value, right? So I'll do one thing. I'll insert isPickVal in here. and let's see what's the catch so over here it's saying enter the picklist field so what's the picklist field and what is the text literal Instead of writing down like this, we have to write it down like so shall I replace this with this? Are we good with this now? So instead of equals to operator what I've done is is speak well and on the left hand side There is field and on the right hand side with which value I want to compare it good Similarly, I have to do it with other fields as well. So let me copy it over here. And by the way, I'm writing it down very well, like very neatly. You guys also have to do the same thing. Otherwise, you'll get confused with the brackets, with everything. Indentation needs to be proper. Do you guys understand what is indentation? Making the code more readable by giving the spaces, by using the tabs and everything. So this is what I'm doing in here. I am writing it down on the next line, I can do it like this as well. Then you might get confused. But I am not doing that. You should also follow the same thing. If you want your code to be readable or if you want your validation rule to be readable. And if it is more readable then you will implement the right logic and you will be able to identify the bugs easily. Make sure to write it down neatly. Even if it is not... Okay, let me tell you a situation. So, one day, a guy who works with us, he wrote down a code. And he was not able to implement the thing which we asked him to implement. And then he asked for the help. That I am not able to implement it, I need to get it delivered tonight. Please help me. And this guy, we've said him earlier that please comment on your code, please make the variable names correct. It should be meaningful. Not I1, I2, I5, I6, I7, I10, something like that, IJK. It should not be like that. It should not be meaningful to you. It should be meaningful to every other person who reads it. Write down the proper comments, make the proper indentation and everything. And this guy, he was so good with coding, but he was always like... This is boring for me. I don't want to indent, I don't want to write the comment, I don't want to give the variable names correct. And when he was not able to implement it, then he reached us out for help and we denied. We all denied that we are not going to help you all. Why? Because we do not want to spend our hours making this code indentation or understanding this code because even if it is not indented and even if it is not well commented. We do not have that much time. We cannot help you out in this situation. So this guy ended up learning a thing that now he's the best. He's one of the best coders who write the best comments and indent the code very well because he was unable to deliver it on that night and it got delayed and everything and it impacted on him. So I'll tell you one thing. Please follow these patterns no matter which technology you're working in, where you're working. Write down. the variable names at one place and write down the comments in front of them and the variable names and everything should be in camel notation and everything and it should make sense then write down the comments for each and every code that you're writing so that the other person who is reading that code should not able to he or she should not be wasting their time in understanding the code that what it is doing they should only read the comment and understand what this is what it is doing and then everything and it should be indented as well so that's how uh like you guys have to do, you guys have to work. And the funny part of it was, the problem was, he only had two semicolons at the same place. And Apex doesn't allow that. And because he was not able to deliver it. And why this problem was there, because his code was not indented and not written properly. He wrote the he wrote he wrote two statements onto a single line, two or three or onto a single line and there was two semi columns in between two functions something like that so he ended up learning this i hope you guys do not have to go learn it through the hard way learn it from the experiences of others and make it work like that uh okay is this good speak well check syntax nowhere else found save I'll show it on top of the page. Why? Because there are more than one field that are involved in here. It's again my choice. It's again your choice. It's done. Just pick one. Alignment. More than one field. Okay. What else? Student. I'll create a new student. You voted for him? Who is the candidate from BJP? Ramchand and Bohra. initial fees stream opted data science I will select I'll select sales with admin cloud computing sales with admin and the fees is 400 it should get saved it will get saved But if I change the Salesforce admin to Amazon AWS, will it get saved? It will not get saved. Resilience fees cannot be less than 5000 for a course other than Salesforce admin and Salesforce data. And what if I make it 6000? Got it. And if the courses have changed the course and we've seen everything and if the courses since with admin, and you have to test your functionalities on your own, by the way, you do not have to get it implemented and then leave it to the QA. Do it yourself as well. Or is this since we're admin and 6000 Obviously, if someone is depositing 6000 for sales for admin, it's good. That's how it goes. Okay, no problem. Are we good with validation rules? Understood it. sure any questions anyone in here or in the chart related to validation rules yeah any questions no we're good okay now i've got multiple questions for you as an assignment write it down Okay, so the student name, write down, you guys also write it down in your notebook. The student name should not include numbers or special symbols. Student name should not include numbers and special symbols. Next, birth date. Birth date should be at least 12 years old in order to get enrolled. And by the way, this is related to the birth date field, not to the age field that we have got in here. So let me tell you, today is 8th 5th 2019. So the one who was born on 8th 5th 2007 can get enrolled. But 9th 5th 2007 cannot get enrolled. That means 9th May 2019 cannot get enrolled today. It should be according to that. Right. Next. Registration date should not be less than 30 days from today. Oh sorry sorry sorry sorry sorry. Registration date cannot be greater than today as well as greater than today. So like you are getting registered today and I should not be able to enter the date for tomorrow. That she got registered tomorrow. Got it? And it should not be... It should not be less than 30 days from today. So that means if you got registered 30 days back, I should be able to register you up till now only because I didn't got the time up till now. But I should not be able to register you if your registration date is less than a month. Like that means if you got registered in January or in February or in March, I should not be able to register you. But if you got registered in April, after 8th April or on 8th April, I should be able to register you. Getting it? Then students contact. So the contact students contact should be exactly of 10 digits. It should exactly be of 10 digits and it should not contain any special symbols or alphabets. It should not contain any special symbols or alphabets. Okay, got it. Then Aadhaar card number should be of exact 12 digits, not less than that, not more than that. Aadhaar card number should be of exact 12 digits, not less than that, not more than that. I think that's it. So these are the questions that you have to work upon. Implement all of these validation rules into your student object and get it done by tomorrow. And that's all about validation rules in today's class. Thank you so much guys for attending. And if you've got any questions, then please stay and ask and else you can leave. Thank you.

The phone number is not correct. When you entered an email or a name in which you accidentally entered a number, what did it say? Like, can there be a number in a name?

No, right. So when, if you accidentally accidentally put a number into a name, the form says the name is not in the right format, right? This is what happens.

So these are particular checks that are placed onto these forms and everything so that the data that gets entered into the database is validated and is right according to the standards of our business. Getting it? Yes or no? So validation rules, listen to this very carefully. Validation rules are used to validate whether the data is right or not or is according to the standards that we have or not.

So that not anything can be entered into your database. You want the records to be created and the record should have values in a particular way, in a particular format or according to a particular standard. And for that you will implement a validation rule on that object which you want to validate or which you want to Yeah, on which you want the data to be standard. Getting it?

Okay. So listen to me and see as well over here. Give me a second. Yeah, this is my ink.

Okay, validation. So whenever you save a record, it goes to the validation rule. And validation rule has got only two things. Number one.

is a formula and number two is error or error message you can say right so whenever you save a record it goes to the validation rule and evaluates this formula it evaluates this formula and this formula can only return one of the two things true or false It only returns a boolean value which is true or false. Listen to this very carefully. If it returns a false value, then what will happen? Okay, it's the opposite in here. and if it returns true then the error message will be shown getting it so in validation rules you write a formula which evaluates to true if the error should be shown and which evaluates to false if the there's no problem in the record and record should get saved into the database Good with this?

Okay, so like let's say if I if I'll give you a situation you guys have to write down a formula now right now in your notebook and I'm going to check it right now and again that thing will happen if it is wrong. So the situation is listen to this very carefully. Whenever you're creating a student record the registration fees should not be less than 5000. If it is less than 5000 then the error should be shown that the student. registration fee should at least be 5000 or more than that but it cannot be less than that. So write down the formula for this.

Write it down. You guys also write down in the chat. I'll check it.

So the thing is no student can get registered unless the registration amount is 5000 or greater than 5000. So easy guys, how much time do you need to do it? Done? You have to write down all the problems.

You do not have to write down the same or the other. You do not have to write down the same or the other. You just have to write down the condition.

Just write down the condition. Registration fee is less than 5000. Exactly. Registration fee is less than 5000. Exactly. So many of you have written registration fee is greater than 5000 or greater than equals to 5000. So guys, you are right when it comes to that, like when describing the requirement that it should be greater than or equals to 5000. But as I told you that in the case, if it is true, it will show an error.

And if it is false, then it will show, it will save the database. Save the record into the database. So if the formula is registration fees is less than 5000 and imagine you are entering 4000. So is 4000 less than 5000? True becomes error and if you enter 6000 then 6000 is less than 5000. No, false.

False is record gets saved into the database. Make sense to everyone? This is how validation rules work.

I think there is something on the chat. All the guys who are not participating in the chat make sure that I have to review or give your feedback as well. I am going to give you less numbers.

You are not going to get more numbers if you are not participating in the chat or the question that I am specifying over here. I've got by the way, you will the certificate that you will get from here from S2 labs. And it's not more about certificate, but it's more about learning. But even if even into that, so like you've kept it this way, that your assignments, your tests, and your class performance will have a serious impact on your score at the end of this course.

So please make sure that you're maintaining all three of it and you guys as well. I know you want to learn. I do not want. that certificate whatever that is but it's better for you to participate into questions like these and if you that that's that's how you learn and no one else will give you these opportunities later on so utilize the best of it Good. Are we good with validation rules?

Okay. Now, I'll give you a situation. So, let me tell you first of all, validation rules are not that easy.

You just don't have to check that registration fees is less than or greater than or something like that. They are more complex many a times. So, I'll give you a situation and you'll have to write down a program of it.

Whether you can call it in C, in Java or whichever language you know. And you have to write it down like this. Let me explain it to you.

The return type of this program would be Boolean and Val check. Let's say Val rule 1. And it is taking two arguments. Number one is what?

Registration fees. And number two is course. Opted right you have to write down a program in here Listen to this Listen to the condition and if you want to write it down you can write it down as well so that you do not get Confused if if the student is registered if the student is registered in any other course in any other course then salesforce admin then salesforce admin salesforce developer or big data or big data then the Registration fees, then the registration fees should be, then the registration fees should be at least 5000 or more than that or more than that.

Else it can be anything at least 5000 or more than that, at least 5000 or more than that. Else it can be anything. It can be anything.

Write down the formula. Write down the program. Whatever you want to write it down.

And show it to me. Opt it. I don't know any programming, no worries.

You just have to write down the in condition, that's all what is required. You do not have to know the complete programming. And if this condition is there, return true if you want the error to be there. And if this is the condition and you want the report to get saved, return false.

That's all what you have to do. Thank you. Let's go.

Hi, I am Gaurav. I am working in a company. I am trying to get a job.

Let me rephrase the question. Let me tell you what the question is. The question is, if the student is registered into Salesforce admin or Salesforce developer or big data. then in that case registration fees can be anything. Yeah, okay read it out.

So am I right? You sure? Yeah, I am right.

I know. So the thing is, if the student is registered in Salesforce admin or Salesforce developer or Big Data, then in that case registration fees can be anything. But if he or she is not registered into any of these three courses, then in that case, registration fee should at least be 5000 or more than 5000. Now do it. Do it the other way round.

Done. I hate this thing that you guys optimize it. I want the syntax to be right. My brain is compiler. I can find out the mistakes.

Like you have done it. All 10. Cannot do it in any program in Android like that. You have to again write down course object equals to equals to.

Then again course object equals to equals to. Logically let me see. I haven't seen it. Again compilation is not very much simple.

The first step that we do is we ask the person, do you know the reason how he can skip something? We ask the person, how can he do that? I heard it. What about this? It's very exciting, but what about other stuff?

What is it that you want to do? I want it, but what if they say follow? ............. This is the first time I am seeing this. I am sure it will come inside.

After coming inside, this station is 3500 feet. Now I have 6000 feet. I can see 4500 I have made a mistake in the story.

This is the software we use and we are using it for testing. After that, we will see how it works. We will test it on the Android 6.0.

We will test it on the Android 6.0. It will work. Here, the next thing is false. False and true.

What are the reasons for the data? Return R-E-P-U-R-N space F-A-L-S-E You don't want? Only when you are in the market, once a month. You see? You are showing it either way.

And for the resident case, it's a greater problem. Who knows? Mali.

It's really hard. It's difficult. Hey, I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript.

I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript.

I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. I'm going to show you how to use API in JavaScript. Shall we move ahead with this? Shall we move ahead with this?

Hi! I don't think you guys are... 2 if and 3 else Before that there is Harshita Harshita has sent me something Let me see if it is correct or not If a course opted in Salesforce developer Then if registration fee is greater than 5000 then return false greater than equals to 5000 then return false and no its not correct because what if someone has deposited 4000 and is registered for syswithadmin I don't want any error I don't want any error over there its not correct Hatsuka So I've checked the one course is going to Salesforce. First, if student is equals to course one common course to print. No, it's not about printing.

It's more about writing down the conditions. Okay. Boolean. Okay. Boolean value check.

Return false. Then else return false. Like I think there should be then and return something and else return something. else if registration fees is less than 5000 then return true else i think it's good if they shouldn't have been this else if you wouldn't have written this else uh before return false then it's correct harshita jeel of course operated uh sales admin dev and big data then falls good else register fees less down to good jeel it's it's correct uh vijay if course operated degree uh comma of course degree comma course update i never asked for degree Of course I have written SF, Dev, Big Data, Then, Then, Else, again you have written Then, Else, you have copied the one from Harsita. Don't fool me.

It is the same. Nakal may be akal ki chara chate if you understand me. Okay. Okay, so let's see how we are going to go forward with this. Boolean well check there was there were two fields that was supposed to come in here like this right and Now what I have to write down is if sales was added if course opted double equals to Salesforce admin or later if course operator goes to sales admin course operator goes to sales developer or course operator goes to big data then it's simple you have to return false Because no matter what the registration piece is, there will be no error.

Even if the student is depositing 5000, 8000 or not depositing anything, 0, 2000, 1000, it doesn't matter if they are in one of these courses. Now, let's talk about if they are not in one of these courses. Else part. If they are not in one of these courses, then the first thing that we have to do is check what is their registration piece. registration fees is less than 5000 then in that case return what true because there should be an error if the registration fees is less than 5000 else and that's what your program should be or should look like okay now now now now so all of you are uh are struggling at one position which is that position let me tell you to create the logic and once you create the logic the the next problem that you guys are facing Identifying that whether this logic is correct or not.

You are like, okay, I think it is right according to me. Let's show it. No, you have to validate it or check it on your own.

And let me show it to you how you need to check it. Give values on your own to both of the parameters. Okay, registration please tell me any random number.

5000 or 6000? 6000? And then comes course opted. what should be the post object? Salesforce admin?

Okay. So if someone is depositing 6000 with Salesforce admin, let's see whether it will give an error or not. And before that, let me write down something.

If we are returning false, then it equalates to save. And if we are returning true, then in that equivalence to error is it clear okay now these are the inputs 6000 and sales with admin so course update is sales with admin so this condition gets true right and it will not check the next one because there is or there is not and right so it will go and return what so it will get saved into the database this is exactly what we want okay now let me change the amount it's 2000. Now let's check it. Course update is used to Salesforce admin.

It will return false. And this is exactly what we want. If the course is Salesforce admin, no matter what the fees is.

So it is getting saved. No matter what the fees is. If I make it zero, then also same thing.

Every time it's same thing. Okay. Now let's go and try on big data.

So, course update is equals to salesforce admin. False. It will check the next one.

Course update equals to salesforce developer. False. It will check the next one.

Course update equals to big data. True. It will go to and return false means.

This is what we want. Sure. Okay.

If I will make it 1000 then again it will get saved. Why? Because course update equals to big data and return false means saved. That's it. Okay.

Now let me change the situation. Android and 6000. So if it is Android, then course of it equals to equals to sales for admin. Is it true?

False. Course of it equals to equals to a sales for developer. False.

Course of it equals to equals to big data. So it will not go inside this block. It will go to the else block and an else block. the first condition is if registration fees is less than 5000 so 6000 is less than 5000 no so it is false and it will not go inside this it will go into the else part and in the else part it will return what and false means safe now one more thing if i'll make it 3000 now tell me it will go to if course update so android is going to salesman admin no android is going to salesman no Android is going to be data. No, so it will not go into this block.

It will go to else block and an else block. There is again one condition registration fees is equal to 5000. So 3000 is less than 5000. Yes, and that will go into this block and execute this. And when we return true, what happens? An error. So this is what we want, right?

If the course is other than Salesforce admin, Salesforce developer, big data. then the fee should at least be 5000 or more than that otherwise the record shouldn't get saved but if it is sales admin or sales developer or big data then it should get saved no matter what the registration piece is is it correct we have checked it in every situation now let's take it on 5000 what will happen in this case it will go into this first sales block and 5000 is less than 5000. So it will return false. So it will get saved. So that's how you need to check your own logic.

So first you have to create the logic. And I'm actually, okay, by the way, you might be thinking that what I'm doing over here by putting so much time into this validation rules topic, let me tell you, this is the most important topic for all the administrators, for all the developers, for all the app builders and everyone. Because it's all about logic. Everyone can understand the concept.

Everyone can read the books, but it's more about implementing in this industry. And the more hands-on you do, the more practice you do, the better you become into this. And I want you to become the best. And that's the reason I'm putting you guys into these situations. which no one else would.

So make sure that you're trying to get the best out of it instead of just sitting and trying to, I cannot do it. I think, I don't know how to do it. Just try it for a minute. I don't know. You shouldn't do it like that.

Try to create more and more answers, no matter how many times it is going wrong. You can check it on your own by just putting onto these values. What if the value is this? Then will it work fine? What if the value is this?

Will it work fine? And that's how you need to create your logics. Is it clear?

So first you need to create a log. So first you need to be a developer and then you need to be a QA. Testing your own thing, right? Whatever you have developed and how to test the things by giving the particular input. So if I want to test this remote, how I'm going to do that?

When I click onto this button, the AC should get turned off. So I'll click onto this button and the AC, if it will get turned off, then the remote is fine and it will not get turned off. Then there's some problem in the room.

That's how you need to do that. Does it make sense? Everyone in the chat got it.

So happy that you got it. Any questions in the chat? No? Good to go? Are you good to go in here as well?

Okay. So we understood how to implement, how to think about the logics and everything. Now is the time to implement the validation rules in our Salesforce data. Let's do this.

Sure. Sleepy. Sure.

We need to implement validation rules. Write down the steps to implement validation rules. Setup, object manager, then the object on which you want to create. Which object is it? Student.

And then click on validation rules. There was validation rules in here. Click on validation rules. And by the way, you can create as many validation rules as you want on a single object.

There is no problem with that. Get it? First let's create that one, right? Registration fees check.

Simple one. So there are only two things. This is formula and this is error, right?

So what should be the formula? Registration fee should be less than 5000. If you are not talking about this, I'm talking about that one. The first one that I asked you to do that right. Registration fee should be less than 5000. If you put that condition then it will always be more than or equivalent to 5000. Getting it?

So how I'm going to do that? I'm going to insert the field. Over here, if you can see, where is it?

Initial P it is, I guess. Initial P. I'll insert it. And then the operator. So see how much point and click it is. It will not give you a feel that you're coding.

Yeah, you are. Initial piece is less than, checks and texts. See that you do not have to remember the name of the field. You can get it from here. And what is this?

Initial underscore piece underscore underscore. Initial underscore piece we understand. That's the developer name.

Whenever we write down any space between the label. When we created that field, we entered the label initial fees and like there was a space between initial and fees and then that underscore automatically gets added because there cannot be a space in the variable name in the code. So over here it's initial underscore fees.

But what's the matter with this underscore underscore C? Exactly. Underscore underscore C always defines or always denotes that this is the custom field or a custom object.

So in this case, it is a custom field. Is it clear? So and less than 5000. No errors found. And what should be the error? If the fees is less than 5000. I want to show it on the top of the page or in front of the field.

I want to show it in front of the field. I'll select it like that. So if there are more than one field involved then show it on top of the page.

If there is only one field involved then in that case show in front of that field only. And it depends on you. It's your choice.

Save. Now what? I'll go and create a student.

Name. Initial fees, I'll keep it 3000. I'll save the record. Legislation fees cannot be less than 5000. I'll make it 40. No, I'll make it 5000. Save and if I'll make it 6000. So, that's how easy it is.

I hope it makes sense. So you now know how to implement validation rules. Now let's create another one. Again, I'll go to the object manager and go to the student object and over there I'll click on validation rules. And I'll implement the one that I want.

So like, like I can create as many validation rules as I want, but I want to modify this one. Otherwise it will conflict because there is registration fees or initial fees involved. So let me change the formula. Okay, now the question is, if the course is Salesforce admin, Salesforce developer or big data, then in that case, there shouldn't be any error.

And if it is other than that, then in that case, the registration fee should be equal to 5000 or more than 5000. Otherwise, there should be an error. That's what it is. So we have already created a...

Program or a code for that. You just need to replicate it. You just need to replicate it And by the way, it's not the it's not always like you have to create it in any other programming language And then you have to replicate it over there This is just one of the ways in which I have made you understand how to do this You do not have to do it in the same way You can directly go and create the validation rule over there right over there But that's a little difficult to create it right over there because you guys are I guess I think that you guys are experiencing some of the programming languages like C or C++, Java, whatever you're experiencing. So that's the reason I created it over here first. And then we're going to make it work over there in the Salesforce validation.

Does it make sense? So the first thing that I have to write down is if condition right over there. So over here, if it's not a statement.

In C in Java, if is a statement over here, if is a function, and where are the functions? Here are all the functions. So your job for the day is you have to read each and every function about each and every function in here, you have to understand each and every function which is given in here and how you're going to do that is help on this function, you'll have to click on this link, and you'll go to the help and you'll read about it about each and every function.

So currently we're talking about which function I'll search if what did it say what it says let's read it if first logical test comma value true comma value false so let me show it to you how what it means and how it works so if I'll insert it I can insert it like this if logical test value true value false Let me tell it to you how it will go. You guys able to hear me? Let me know if you are not. If condition true block Else false block. So in languages we write it down like this.

First we write down the condition and if the condition is true then whatever you want to execute write it down over here and if it is false then write down whatever you want to execute over here. It makes sense? Okay now let's talk about how it is relevant to that. relevant to the function that we got. So over there, there is something called as logical test.

You can see this, let me annotate it. There's something called as logical test. So this logical test is equivalent to the condition, right?

And this value of true, let me just show it to you. So these are separated by a comma. So after first comma you have to write down the true block.

Whatever you want to execute in that if that condition is true or if that logical test is true. And then there is value false. So in value false you have to write down the false block.

You got it? You are able to relate with this? You sure? Everyone? In the output in Boolean form, output in true or false, not in S, always.

So that means you have not created the validation rule in the right way. There is a problem in your logic. Give me a scenario. Who is creating the validation rule?

Fire the developer What else can you do? Not the whole database but the records which gets inserted wrong Yeah so fire the developer I agree but fire the developer That's the only choice that you have got because he is not proficient enough in his profession or he's not capable enough of doing his own his or her own job and that's the reason i want you guys to grill over here rather than grilling over there and creating wrong formulas confusing yeah you have to yep so that's the reason i'm putting you in these situations so that you you get it into your head that true is always No, no, true is false. True is false. True is error and false is same.

Right? True is error and false is same. You need to get it into your head.

And that's the reason I created that diagram as well. So that you understand it very well. And if you'll not, you might get fired.

Make sense? Okay. Yeah.

So the false block after the second comma, the true block after the first comma, and the condition. just after the bracket or just after the parenthesis. So in this case what will be the logical test? What will be the logical test?

Tell me. Course update equals to equals to Salesforce admin or course update equals to Salesforce developer and all of this stuff. So let's do that.

Where is core software? Core software now operator equal salesforce admin Now what? or again you have to write down the same thing data got it if I want I can wrap up this condition into one as well like this there's no need but if you want you can do that so this is the condition and then if this condition is true what what do we need to do return false so over here you do not have to write down false return but you can just write down false and it will return the false value automatically.

Is it clear? Okay. What if this condition is not true? Then again, again, if blocks over here, I should put another condition.

You sure? If insert. Good.

And what should be the logical test in this? Initial. Yes, yes. Initial piece is less than. If it is less than 5000 then?

True. Else? Right. This is what it is.

If you'll see, this is what we're doing. If registration fee is less than 5000, true. Else, false. Are we good with this everyone? Everyone in here?

Everyone in the chat? Let me know. I think there are some messages that I'm missing out.

If course operator is false, yeah, you're absolutely right. So that means if the developer big data falls, if initial piece is less than 5000 true or false. What else?

Yeah, that's it. So shall we click on checks and texts? We're done with this? Okay.

Someone was saying something. Error. First update is a picklist field. Picklist fields are only supported in certain functions.

So listen to this. We cannot compare the value of a picklist field with the help of equal operator. We cannot do that.

There is a different function to do that. And the name of that function is isPickVal. IsPickVal is picklist value, right?

So I'll do one thing. I'll insert isPickVal in here. and let's see what's the catch so over here it's saying enter the picklist field so what's the picklist field and what is the text literal Instead of writing down like this, we have to write it down like so shall I replace this with this? Are we good with this now? So instead of equals to operator what I've done is is speak well and on the left hand side There is field and on the right hand side with which value I want to compare it good Similarly, I have to do it with other fields as well.

So let me copy it over here. And by the way, I'm writing it down very well, like very neatly. You guys also have to do the same thing. Otherwise, you'll get confused with the brackets, with everything.

Indentation needs to be proper. Do you guys understand what is indentation? Making the code more readable by giving the spaces, by using the tabs and everything. So this is what I'm doing in here. I am writing it down on the next line, I can do it like this as well.

Then you might get confused. But I am not doing that. You should also follow the same thing.

If you want your code to be readable or if you want your validation rule to be readable. And if it is more readable then you will implement the right logic and you will be able to identify the bugs easily. Make sure to write it down neatly. Even if it is not...

Okay, let me tell you a situation. So, one day, a guy who works with us, he wrote down a code. And he was not able to implement the thing which we asked him to implement. And then he asked for the help.

That I am not able to implement it, I need to get it delivered tonight. Please help me. And this guy, we've said him earlier that please comment on your code, please make the variable names correct. It should be meaningful. Not I1, I2, I5, I6, I7, I10, something like that, IJK.

It should not be like that. It should not be meaningful to you. It should be meaningful to every other person who reads it. Write down the proper comments, make the proper indentation and everything. And this guy, he was so good with coding, but he was always like...

This is boring for me. I don't want to indent, I don't want to write the comment, I don't want to give the variable names correct. And when he was not able to implement it, then he reached us out for help and we denied. We all denied that we are not going to help you all.

Why? Because we do not want to spend our hours making this code indentation or understanding this code because even if it is not indented and even if it is not well commented. We do not have that much time. We cannot help you out in this situation.

So this guy ended up learning a thing that now he's the best. He's one of the best coders who write the best comments and indent the code very well because he was unable to deliver it on that night and it got delayed and everything and it impacted on him. So I'll tell you one thing. Please follow these patterns no matter which technology you're working in, where you're working. Write down.

the variable names at one place and write down the comments in front of them and the variable names and everything should be in camel notation and everything and it should make sense then write down the comments for each and every code that you're writing so that the other person who is reading that code should not able to he or she should not be wasting their time in understanding the code that what it is doing they should only read the comment and understand what this is what it is doing and then everything and it should be indented as well so that's how uh like you guys have to do, you guys have to work. And the funny part of it was, the problem was, he only had two semicolons at the same place. And Apex doesn't allow that.

And because he was not able to deliver it. And why this problem was there, because his code was not indented and not written properly. He wrote the he wrote he wrote two statements onto a single line, two or three or onto a single line and there was two semi columns in between two functions something like that so he ended up learning this i hope you guys do not have to go learn it through the hard way learn it from the experiences of others and make it work like that uh okay is this good speak well check syntax nowhere else found save I'll show it on top of the page.

Why? Because there are more than one field that are involved in here. It's again my choice. It's again your choice.

It's done. Just pick one. Alignment.

More than one field. Okay. What else? Student.

I'll create a new student. You voted for him? Who is the candidate from BJP? Ramchand and Bohra. initial fees stream opted data science I will select I'll select sales with admin cloud computing sales with admin and the fees is 400 it should get saved it will get saved But if I change the Salesforce admin to Amazon AWS, will it get saved?

It will not get saved. Resilience fees cannot be less than 5000 for a course other than Salesforce admin and Salesforce data. And what if I make it 6000? Got it. And if the courses have changed the course and we've seen everything and if the courses since with admin, and you have to test your functionalities on your own, by the way, you do not have to get it implemented and then leave it to the QA.

Do it yourself as well. Or is this since we're admin and 6000 Obviously, if someone is depositing 6000 for sales for admin, it's good. That's how it goes.

Okay, no problem. Are we good with validation rules? Understood it.

sure any questions anyone in here or in the chart related to validation rules yeah any questions no we're good okay now i've got multiple questions for you as an assignment write it down Okay, so the student name, write down, you guys also write it down in your notebook. The student name should not include numbers or special symbols. Student name should not include numbers and special symbols. Next, birth date.

Birth date should be at least 12 years old in order to get enrolled. And by the way, this is related to the birth date field, not to the age field that we have got in here. So let me tell you, today is 8th 5th 2019. So the one who was born on 8th 5th 2007 can get enrolled. But 9th 5th 2007 cannot get enrolled.

That means 9th May 2019 cannot get enrolled today. It should be according to that. Right. Next. Registration date should not be less than 30 days from today.

Oh sorry sorry sorry sorry sorry. Registration date cannot be greater than today as well as greater than today. So like you are getting registered today and I should not be able to enter the date for tomorrow.

That she got registered tomorrow. Got it? And it should not be... It should not be less than 30 days from today. So that means if you got registered 30 days back, I should be able to register you up till now only because I didn't got the time up till now.

But I should not be able to register you if your registration date is less than a month. Like that means if you got registered in January or in February or in March, I should not be able to register you. But if you got registered in April, after 8th April or on 8th April, I should be able to register you. Getting it? Then students contact.

So the contact students contact should be exactly of 10 digits. It should exactly be of 10 digits and it should not contain any special symbols or alphabets. It should not contain any special symbols or alphabets.

Okay, got it. Then Aadhaar card number should be of exact 12 digits, not less than that, not more than that. Aadhaar card number should be of exact 12 digits, not less than that, not more than that. I think that's it.

So these are the questions that you have to work upon. Implement all of these validation rules into your student object and get it done by tomorrow. And that's all about validation rules in today's class.

Thank you so much guys for attending. And if you've got any questions, then please stay and ask and else you can leave. Thank you.

Transcript for:Understanding Validation Rules in Programming

Transcript for:
Understanding Validation Rules in Programming