Name: The Power of Conditional Logic: Your Secret Weapon for Productivity
Uploaded: 2025-02-12T23:30:50.500Z
Duration: 46 min 44 s
Description: The Power of Conditional Logic: Your Secret Weapon for Productivity

Transcript for "The Power of Conditional Logic: Your Secret Weapon for Productivity": Great. I have to cough right as it begins and starts off. Well, good afternoon, good evening, good night wherever you are out there. If you are actually joining us from, one of our Blackbaud Pacific customers, a very early morning to you. Gonna give it just a minute here while, the numbers climb up and see if they, start to level off, and then we'll go ahead and get started. I would know also if you are joining us from, from Australia or thereabouts, you're probably enjoying some nice summer weather. I had to, shovel about eight inches of snow this morning, Nick, which you can smile about because my guess is that's not a whole heck of a lot to you. Normally, no. But this year, that is more than we've got in total. So yeah. Alright. This is the second one we've had this big this year after having essentially no snow for the past three, four years. At any rate, enough about the weather. Looks like these numbers have started leveling off, and I think we can go ahead and get started. And I may have to turn on a light because it's starting to get dark here. But, hello, everybody out there. Hope you're doing well. Welcome to the third in our series of monthly office hours that we're hosting for the new Blackbaud applicant grantee program. And I'm joined by Nick Mills. He'll do a little bit more of an intro when he starts, taking control of the screen and doing the talking. But I do wanna just lay a few things out here this more or this early on as we get going. I have dropped into the chat a number of resources for you. I apologize for the long URLs, but that seems to be the best way to let make sure people can actually click on them and they open. The one I would particularly draw your attention to is the top one there, the customer success enablement page. I checked this morning, Nick. It does now include the January instance of these office hours that's there. And it's a little bit redesigned if you haven't, been there in a little while. Hopefully, easier for you to identify the resources that you need. The others on there are the other resources I shared are also exceptional resources, and we have begun in case you're not familiar, we have begun doing instructor led trainings through Blackbaud University on the new applicant portal. And why are we doing all this stuff? We're doing all this stuff because we heard you guys say you need more resources. So I think we're getting a pretty good plethora of resources there, through BBU, through the enablement page, and through some of the connect for success sessions that our customer success team is doing. A couple housekeeping notes as we go through here. Please put any questions you have in the q and a section to the right of the docs there. We've got a team of people behind the scenes who are helping us out, answering questions as we move through this. And if you're having trouble visual or hearing, try refreshing your browser. That tends to do the trick, and get you back in. And even we had somebody yesterday tried that, still was not able to hear the session through the entire thing. Don't worry. We are recording this, and in a little while, this also will be posted to that customer success enablement page. And I will throw out one final thing that's just a note, to say we've got one more of these coming in April, a tips and tricks webinar that, I'm really looking forward to. But for today, I am a CSM here at Blackbaud. Like I said, joined by Nick. We're talking about some of the really cool conditional, logic functionality within the new applicant portal. And with that, I'll pass it on to you. Thanks, Ryan. Just a quick point of clarification. Is the next session, is that in March or April? My mistake. Yes. We do four sessions, so I keep on thinking it's the fourth month, but we started in December. So the fourth session is in the third month. Thank you for that clarification. Absolutely. Thank you. Hello, everyone. This is Managing Conditional Display Logic. We're let's see here. Get into my slideshow. My name is Nils. I am a business consultant in our professional services department. I work, with all sorts of organizations, consulting, and implementation regarding grant making. I have been with Blackbaud for, almost thirteen years now. And, for the last six or so, I've focused exclusively on grantmaking. And as you'll see here, I am located in Minneapolis, Minnesota where it's nice and cold today. For today, what we're going to cover, we're gonna talk about what is conditional display logic. We're gonna talk a little bit about what you can do with it, some things that you can't do with it, and potentially maybe some reasons why you wouldn't want to use conditional display logic, at least, you know, partially. We'll talk about how conditional display logic works, and then I have some examples of where you might consider using it. And then I'll go through a few live demonstrations, to kinda show exactly how to set it up. And then we also have some resources that I'll point out, a little bit later. And if we have time, which we should, we should have some time for some q and a. Again, we have a team of people behind the scenes who are answering any questions. So if you have questions, please throw them on that q and a tab, and we'll answer as as as we're able. If there are, you know, certain examples of things that you might wanna see live that I don't cover and we still have time, feel free to throw that in the q and a. And if we are able to demonstrate that for you, we certainly will. So moving on, what is conditional display logic? Conditional display logic in terms of this new applicant portal allows you to display or hide specific fields, entire layouts and sections, or even entire pages within an application form based on defined logic. Now what does that what does that really mean in in more, layman's terms? Basically, it allows you to, display or hide information on an application form based on conditions being met within that form. You'll note that I'm going to say application form a lot throughout this webinar. This does apply to any type of form in the new grantee portal. So that's request forms, LOIs, additional documentation, progress reports, your requirements, your applications, all of those different form types, you can apply conditional logic to. I just say application form because it's it's easier than having to, you know, mention a bunch of different types of forms, but this works for anything that you can create in the new applicant portal. So what can you do with conditional display logic? Here are just a few examples and things that you might consider using conditional display logic to help with. First, you can dynamically display or hide information within an application form based on the values found in other fields that are on that same application form. Now that's a very important part, that you need to keep in mind. This is, I start an application as an applicant, and it's the things that I do within that application that allow me to show or display or hide other, you know, fields, pages, or layouts. Any of that is based on other aspects of that application form. I couldn't say, for example, oh, if this is an organization applying and they've applied more than 15 times over the past five years, we're gonna show them this information. That's not really, possible. It it could potentially be possible, but just as a a basic use, you can't reference things like that outside of this application form. There are some more advanced uses where you could display specific values from grant making in your application, and then you could use that as the basis for conditional logic. But that's a more advanced use. What we're talking about today is gonna be a little bit more on the basic side, something that's consumable for everyone so that everyone may be it may be able to use these. Also, conditional display logic can provide a more streamlined application experience for your prospective grantees. This allows you to only display information that is applicable to that specific audience that is applying for that application form. You could also potentially reduce the number of forms that you need to maintain. Conditional display logic was not something that was available in the legacy grantee portal. So there are quite a few organizations who just had a ton of fields on their application forms, but only some of them were applicable to any given audience. They might you know, if you had specific conditions, you might add some fields, and then you just kinda put some some descriptive text that says, please only fill this out if you meet this criteria. And then it would just be an optional field. And and that doesn't really help collect accurate data all the time. If it's optional, you don't have to fill it out. So a lot of times, applicants will skip something that's not required. Because, you know, you couldn't do that in the grantee portal, there could be a ton of extraneous fields that you don't need. Conditional display logic can help you hide some of those things that may not be applicable based on other criteria in that application. There are also a number of organizations who have had to maintain a lot of different forms where they might have been, you know, substantially similar, but they only had a couple things that were different maybe based on a program area, maybe based on the location, that they served. So there were some some, you know, organizations that might have had 10 or 15 different applications that were almost exactly the same, but just had some slightly different questions based on specific criteria, something like that, there's a very good chance you could consolidate many of those forms, if not all of them, down to one. They could also display rich text messages under certain conditions. If you want to display a message, if somebody chooses a specific option, you can do that. You can hide text, and you can show text based on those other conditions. What can't you do with conditional display logic? Again, conditional display logic generally only works within a single application form, at the time that an applicant is filling it out. So conditions must be met within that application. You can't easily reference other information outside of that specific application. Conditional display logic is not available for fields within contact tables, although you can apply it to the entire table. So you can hide or show an entire table, and that is something that I'm going to demonstrate for you in a little bit. But you can't conditionally display or hide information within that table. For example, you could not only show the office extension field if the office telephone field was filled out with the phone number. It's either it's on there or it's not. You can't conditionally display it within the table. You also cannot utilize conditional display logic for a value entered into a contact table. For example, if you were collecting a contact title and you wanted to say, if somebody puts in finance director, we're going to display this field. Unfortunately, you can't do that. You can't reference anything in that contact table. You can't conditionally show or hide anything in that contact table, but you could hide the entire table in certain scenarios. And you could also, you know, display a finance director contact table. So if if many of you may have noticed, we have, all of those different contact roles now as individual tables, and that kinda takes away that whole contact rule drop down that was confusing for a lot of applicants. So there are a number of different ways we could do things. There are some ways to work around some of these limitations, but there are some things that you can't do with conditional display logic as it pertains to contact tables. Conditional display logic also cannot be used for, various functionality like esignatures or other aspects of program setup. Again, it's all contained within that single application as the applicant is filling it out. Okay. So are there instances when maybe you shouldn't use conditional display logic? Absolutely. If you're thinking about, gosh, I have a lot of these different forms that were in the legacy grantee portal, and I want to try to consolidate them down to a fewer number. If you are going to do so, you wanna consider the request types that you would typically use when those applications were considered. If you have three completely different application forms and they all have a a distinct request type that you use when you or when you consider them, it may or may not work for you to, try to consolidate all of those down to a single application. You still have to choose a single request type when you're considering that application. So if you were to consolidate all three of those applications into one, you could collect all that information, but you'd still need to know somehow which specific request type to choose. Again, there are ways we could work around that, but that could be a limitation if you're thinking, gosh. It would be really cool if we could consolidate all of these forms. Some organizations have applicants that want to kind of review the entire application, and, you know, fill it out, print it out, work through everything before they actually log in to the system and fill it out and submit it. When you are doing that, anything that's conditionally hidden, will stay conditionally hidden unless those criteria are met within that application. So if I load up a brand new application and I have certain fields that are set to only display under certain scenarios, those will stay hidden until I change something in the application that would expose those fields. So anything that is conditionally hidden will not be kind of on that nice, you know, nice unfilled view of that application. Now only fields meeting certain conditions, that display on the screen also come through on the PDF. So when your applicant submits the application, you consider it. It turns it into a request. And now with this new applicant portal, we have an attached PDF as opposed to that old HTML file, and that PDF will only show the fields that were filled out and conditionally display. So if you have certain fields that are hidden, certain fields that are only exposed under certain conditions, if if those were not exposed at the time of the application being submitted, those will not be on the PDF either. There is one little caveat to this, though. If you are in, managing your forms, there is an option, in the same place that you would, publish or edit an application form. If you preview that application form, that kind of brings up, sort of an intermediate step between editing and what the applicant will actually see. It gives you a better idea of what the applicant will see. It's not a % what the applicant sees, but it's it's a much closer approximation. When you're on that screen, there's also a download button so you can download that preview. When you do download in preview, view, that does give you the option of either showing all of your fields or, including that conditional logic so that only those where the conditions have been met will display. So that's the one place where you can get everything regardless, but that's not something that an applicant will be able to do. From an applicant perspective, if they go to try to download that application, they're only going to see what is always shown or what is set, with conditional logic to display at that time. So there are, as I mentioned, there are three different places that you can add conditional logic. You can do that on an individual field. You can do it an entire section or a layout. So if you have columns or you've got a panel layout where you have that nice little header at the top, you can hide that entire section, which then hides all of the fields that are contained in it. You can also do the entire page. So in all of these scenarios, there's kind of a display tab in the setup, with the exception of the page. Page is a little bit different. When you're looking at your pages across the top, and I'll I'll show you this in just a moment. But But when you're looking at the pages, there's the page name, which is two little dots. If you click that, that's where you're going to see the show and hide page, which we see here. For both panel you know, the layout configurations and individual fields, there's going to be a specific display tab. So how does conditional logic work? There are display settings, which is that display tab or that show hide. And so there are two always options. You can set a field, a panel, or a page to always show, or you can set it to always hide. By default, it's you know, everything you add to your application is going to be defaulting to always show. The vast majority of fields that you add to a form are there because you want the applicant to see it. You want them to fill out information. You want them to submit that. So by default, if you're putting it on the form, there's a good chance you want somebody to see that. You can also always hide things. A lot of organizations use this for some hidden coding, things like maybe organization type or an internal program code that you have where you want that to automatically apply to that resulting request record, but you don't need the applicant to see it. It's something that needs to come through on the back end, but the applicant it would just be confusing or they don't need to see it, so you can hide that all the time. There are also two other options in that always show or kind of the the display section. So there's the always show, always hide, and then there's show component when and hide component when. And those are the two where you can apply conditional logic. And that leverages what we call conditions or rules to adapt those display settings. So conditions, when you add a condition, these are simple single parameter equations. So if you want to think a requested amount is greater than or equal to $10,000, then I want to show other information. Program area equals health. Project budget is greater than requested amount. Population served includes homeless. Those are all kind of single yes, no binary answers. It's either this or it's not. The requested amount is greater than or equal to $10,000 or it's not. There aren't, multiple different types of, parameters that are going into this. It's just a simple single condition. Rules, on the other hand, are a set of complex parameters. So that's when you get more than one, and we introduce ands and ors. So in this example, requested amount is greater than or equal to $10,000, and the program area equals health. If both of those conditions are met, then we're going to display this information. Project budget is greater than requested amount or the grant term is greater than 12. If either of those conditions are met, we will display or hide this information. If the requested amount is greater than or equal to $10,000 and there's a request date between two specific dates, that's using both of those conditions. That's a little bit more complex. When you get into multiple parameters, you get multiple options, and you have the ands and the ors and the parentheses to make sure that it's, you know, doing exactly what you want. That's what we call rules. And so conditions are simple, just one one simple parameter. Rules are complex. They've got multiple sets that can either use ands and ors and parentheses and all that. The basic process for using conditional display logic is step one, you add all of your fields to your form. You cannot conditionally hide or display things if they're not on the form already. So the very first step, get everything on your form, you know, add in your layouts, add your explanatory text, add your descriptions, add in everything that you want, and then worry about adding in that conditional display logic. Second step is to edit the field or layout or page, then you go to the display tab. Step four, you want to click the manage conditional logic link. Step five, choose to either show it when or hide it when, then we're going to add that conditioner rule. We'll apply it. We'll save the field. We'll save the form, and then we'll test. This is just a basic process, just an outline. I will walk through exactly this whole thing step by step in just a moment. Some ideas for using conditional display logic. If you have perhaps a a classification table or a values field where you have kind of a drop down, you have multiple options. A lot of organizations have an other category. And if somebody chooses that other category, you can then conditionally display a text box that says, if you've chosen other, you know, show this text box and ask them to explain what they mean by other. Instead of having other on your form all the time, that's just what your, is only going to show if they choose that as a particular option. You can also hide the request primary contact table if you are using that same as the organization primary contact checkbox. And that's one of the examples. The other and this, hiding the request primary contact table under certain scenarios, I will show you those. I will also show or hide attachment fields based on other conditions. So those are the three that I'm going to show in just a moment. Some other options, showing a fiscal sponsor information page. If that applicant is using a fiscal sponsor, then you can expose a section, an entire page to collect that additional information about the fiscal sponsor that's only really applicable if they are using, a fiscal sponsor. You can show entire pages of additional information or fields based on specific conditions, and you can also display rich text messages based on those conditions. An example of that, let's say you have a minimum grant amount. You could set up a a content field. That's those text boxes where you can add in some of that rich text, and you could say, only expose this if they enter a requested amount that is less than our minimum. If my minimum is $10,000 and they put in that they're requesting 5,000, I could expose a little message that says, please note that our minimum is 10,000. Please increase your request amount. So there's lots of different options, and I I've seen some some very, very unique and very cool uses of display logic so far. So those are just some ideas. I encourage everyone to get creative, and I'm going to now move into our demonstration feed. So I'm gonna show three different uses of that conditional display logic. First one, exposing an other text box when you select other from a drop down. Second one is hiding the request primary contact table if you're using that checkbox that says same as organization primary contact. And third, hiding a file attachment field when it's not applicable. Let me see. Okay. Gonna hop over to my browser here, and you'll see I just have a simple application form here. I have my basic application, just some simple information. I'm gonna make this a little bit bigger so it's easier to see. So I'm gonna fill out some very basic information. My type of organization, I have two options. I'm gonna choose that I'm a government entity. I'm gonna give my organization a name, and we'll do Blackbaud's headquarters, and we'll do our tax ID. Alright. Now you'll see this first example in my other selections. I have a program area, and I have an other text box. No conditional logic at this point, so they're both always showing. In my program area, I have a number of different options. So if I were to choose other, I want this to display only if this is set to other. So here is what I'm going to do. I am going to go over to my application. I'm going to manage my forms and I'm going to edit that application. And we'll see on our other selection, I've got my program area and my other text box. So the first thing I'm gonna do, I have to make sure that all of my fields are on my form. Program area, other. Yep. They're all there. I'm going to edit the one that I want to either hide or show, And within that form field, I'm going to go to the display tab. You'll see I have the four options, always show, always hide. I'm going to show it under certain conditions, or I'm going to hide it under certain conditions. In this case, I only want this to show when that is set to other. So I'm going to set show component when. I'm going to manage my conditional logic. In this window, I can add either that simple single parameter, a condition, or I can add a rule which is a set of multiple conditions. In this case, it's very simple. If you choose other, display it. That's it. So I'm going to add a condition. I'm going to select my field and program area. Now this comparison can be a little tricky sometimes. In this case, program area is a classification table. When you have classification tables that can potentially accept multiple values, you're frequently going to see the one of option, and that is one that I'm going to use in this scenario. That may not always be the perfect one for you, and this list of comparison operators changes based on the type of field that you're choosing. So if I were to choose cash amount requested, I have different options. I now have an equal to, greater than, greater than or equal to. This is a currency field looking for a specific dollar amount, So the comparison operators make sense for that type of field. If I go back to my program area, I'm going to choose one of. It's going to default to specific value and that's basically where I say I'm going to dictate exactly which value I want that to be other. So then once I have this configured, I can look up here and I'm going to show the component when the program area is one of other. That sounds right to me. Let's apply. I'm going to save the field, then I'm going to save my form. And I am going to update the current revision and then I will come back here and I'm going to reload my application. So I still have the information that I submitted before, my other selections. Now you see I only have a program area. If I choose arts and culture or if I choose civic and community, education, but when I choose other, I now have this other text box and I can type in whatever I want there. The second thing that I'm going to show is the same as checkbox. So a lot of organizations collect contact information in this way. They've got their organization primary contact. That's, you know, your executive director, the president, whoever's in charge of the organization. And in this case, I'm just collecting first name, last name, email address. Then you have the same as organization primary contact and your request primary contact. So I've got same first name, last name, email address. What this checkbox does is it takes whatever you enter into this table and it uses it for both the organization primary contact and the request primary contact. Now in the legacy grantee portal, when you check this box, it would actually update the request primary contact fields, and it would show you on screen. It would copy exactly what you entered for that first table into that second. We don't do that anymore. It doesn't display. It doesn't change anything and show that that's the same information. But if you check this box, it will use whatever you enter here into both of those, primary contacts. So what I want to do, you'll see now if I add in my contacts and I want to check that box. Right now, if I were using this, I could still add something to this request primary contact. I don't necessarily want that because if we're using the same information, it's going to use this regardless of what they put in this table. So what I want to do is hide this entire table if this box is checked. So what am I going to do? I am going to go back over to my my, edit form. Here we have our contact tables and so I'm going to edit the one that I want to actually hide or show, because this one is showing by default. This in this case, I'm going to hide it. So I'm going to edit that component. I'm gonna go to my display tab. I will set this to hide component when and manage conditional logic. Again, this is simple. The checkbox, same as organization primary contact. Checkboxes are really, a binary. Yes, no. It's either checked or it's not. You can't 50% check a box, not as far as computers go, but, it it's not multiple options. It's either one or zero, yes or no, it's checked or it's unchecked. So this is a simple condition, single parameter. I'm going to add that condition. When my same as primary contact is equal to let's see. I gotta think about this. I'm going to hide it when that box is checked. So when it's checked, that is considered true. So hide component when the same as organization primary contact is equal to true. That sounds right to me. I'm going to apply that. I'm going to save my field, and then I'm going to save my form. And I'm going to update the current revision, and I'm going to test it. So let me refresh my application, and over to our same as checkbox. So now I come in here. Let's see. I'm going to add in my information again. So I've got this, and now, yeah, I'm the same person. I'm filling out the application. I'm also the head of the organization, so I'm gonna check that box. And now that request primary contact table is hidden. I don't have to worry about seeing it. It's going to take exactly what I have here and use it for both of those tables. But because I don't need to see that and I don't need to fill that out, I can just hide that completely, and I don't have to worry about it. Now the last option, attachments. So on my attachments page, I ask for a project budget and an IRS nine ninety. Now if you remember, if we go back to the basic application, my organization was a government entity. The vast majority of the time, government entities don't have nine nineties. So that's gonna be something where if I choose government entity, I want to hide the IRS nine ninety field because that's not applicable to that type of organization. So what am I going to do? I'm going to go back to my application. I'm going to edit it. Gonna go to my attachments page. I'm going to modify the one that I want to either show or hide, in this case, IRS nine ninety. Go to my display tab. So what do I want to do? I want to hide this if we're using government entity. So I'm going to hide component when, manage my conditional logic. Again, it's a simple simple condition. It's it's either it is government entity or it's something else. So I'm going to do my organization type. And when that is one of, again, this is a, a classification field, so it could be potentially multiple values. So we've got one of as an option, a specific value, and I'm going to use government entity. So I'll read up here just to verify. I'm going to hide this component, the IRS nine ninety attachment field, when the type of organization government entity is selected. That sounds right. I'm going to apply that, save the field, and update and save my application. Then I will reload over here. And again, you see the type of organization we chose is government entity. So when I go over to my attachments page, I now only see the project budget. If I go back and change that to a five zero one c three and I go back to my attachments page, I now have the IRS nine ninety that is required, and I have to fill that out. So those are just three examples of how you could use conditional display logic. One thing I do wanna show real quick is setting up a little bit more complex, using a rule as opposed to a condition. So let's just pretend that instead of hiding this when the type of organization is government entity, I'm going to clear that out and I'm going to add a new rule. And this looks a little bit different, but it's very, very similar to adding a condition. So really, this is one condition right now. I can add an additional condition, however many I'd like. In this case, let's go, back to my org type of organization is government entity. And if I want another condition, so there's a little bit more complex, I can add a condition. And then I'm going to say let's see if my program area is one of these again education. So if the type of organization is government entity or the program area is education, I look up here. I'm going to hide the component when either type of organization is one of government entity or the program area is one of education. So in this case, either of those conditions, if either of them is true, it will hide that field. Now the or and the and is easily toggled by checking this little slider bar. So now all of the conditions have to match. The type of organization has to be one of government entity and the program area has to be education. If both of those conditions are met, then we'll hide that component. If not, if only one of them or none of them, then we'll continue to show it. So you can get incredibly complex. You can kind of nest all these in together and get really, really complex if you want. I would encourage you to try to be as simple as possible just, to to maintain the ease of modifying things and making sure that it's functioning the way you expect it to. The more complex you get, the more opportunity there is for, the logic to not work exactly and to not, you know, show or hide things when you really need them to be shown or hidden. So try to be as simple as possible, but you can get as complex as necessary. Finally, I'm gonna jump back to my PowerPoint here. Here we go. So we did the demonstration, some resources. And, Ryan mentioned this a little bit before and I'm sure some of this has been posted in the chat or has been answered in questions, but there are three resources that I really wanna point out. There is the Blackbaud grant making customer success page, that has articles, videos, documentation, lots of different, guides to help with things. There's the Blackbaud grant making help center, which has release notes, help guides, link to Blackbaud community, the ideas portal, Blackbaud University, kCentral. It's kind of a one stop help center where you can get to all these different things from that one page. And then there is the applicant and grantee portal documentation, which is kind of that that, in you know, how to use everything. Other thing I want to show here, this is that customer success page, and this is newly redesigned as of this morning. So we have it a little bit, broken down a little bit better. So all of our webinars and recordings up here at the top, guides and worksheets, and some product documentation and training. The one thing I want to point out is this conditional logic, this handout, which is available on this page, and that is this guide. This was put together for a a BBCon session this past September. And, basically, this is a color coded guide that kind of explains what everything is and how to use it. It walks through step by step how to use it, talks about those different comparison operators, see different field types, hear all the different things that are available, you know, greater than, equal to, one of, betweens, two dates. There is a list of all of those that are available based on the type of field. So this guide could be helpful in thinking if you're gonna kinda work to design a new form and you think, I only want to display this in this scenario, what type of field do I want? This might be a good reference. And then there are also two scenarios in here that are completely different than the three I just showed you. There are actual scenarios that kinda walk through, you know, that scenario and what the organization wanted to do, and then it goes through step by step exactly how to do that in both of these scenarios. So everything's color coded step by step. It could be a very valuable resource for anybody who is maybe a little anxious about trying to use some conditional display logic, but that, hopefully will be helpful and kinda give you a really handy step by step guide that you can reference if needed. And with that, that is all I have for today. So I'm going to see if there are any questions that we need to answer. Thank you. Thank you. Thank you, Nick. Really appreciate that. As he stated, that handout is available on the customer success enablement page. I believe Kathleen also dropped a direct link into the chat on this on this session. Excuse me. Actually, we had a slightly smaller group today than we had last time we did this, and it does look like all of the questions were answered by the folks behind the scenes who are, following up with people. So I think we're good from that perspective. I would reiterate, grab that handout. It really is great just to have, whenever you're starting looking at this. And the conditional logic, I really think it's a valuable tool. Not only do I think it it is beneficial to you directly in helping you be able to build nicer looking forms and whatnot, but it's especially helpful to the applicant. It makes their process more seamless. It makes it more streamlined. I think it's a really valuable thing. And we would notice you saw, Nick go through there. I did mention it as to the top, but I will mention it here just so everyone on here is aware that the legacy portal does go away at the August. And I know a lot of people out there are like, well, so I need to get on. Maybe I don't have time to do some of this conditional logic stuff. I'm just trying to recreate forms and and keep my program, up and running. You can build this in after the fact. So you can get those forms up and then go back and say, hey. Let's tweak them. Let's alter them. Let's make them nicer as you go forward. Keep on evolving them. So I think that's a valuable thing. The last thing I will do, I will toss out there to this group is, we know some of you out there. You've got a lot on your plate. You're maybe a one or two person shop. You don't have time maybe to take this on. We do have offerings from our services team of which Nick is a part, that highlight for you that that can help you guys build these out. And they've got a few tiers that they've got built out, anything from just like, I have two forms. I need them in the new, applicant portal. I just need it to be done to I've got more than that many forms. I'd really like to take care take advantage of some of the new functionality, this conditional formatting. So if you're looking for assistance in that vein, reach out to your customer success manager. Let us know. We can, get that ball rolling. I say we had no questions, and I, I believe we've got some. I was told services is booked out. They they are pretty busy right now. I'm not gonna lie. But we've got time between now and August to help working that. Yeah. Right now, there's a little bit of a backlog just because there's a lot of people who are looking for assistance right now. That's usually just a couple weeks. So from the time that paperwork and all of that is figured out and we have a project in place, there's, you know, a little bit of a wait, a couple weeks before we can get started, but, there's certainly resources available. And if you are interested, reach out to your customer success manager and, discuss with them. They can help get that whole process taken care of of getting everything in place. And then that comes over to, someone in our services department who will reach out and schedule some time to kinda talk about what you want. Very good. I'm also in the in the q and a here. I'm seeing some people saying this was clear, looks great. So that's kudos to you, for building that out, running that down. Again, this will be, recorded. It will be posted to the enablement page in a in a few weeks, probably. It takes a little time, for that to run through. We do have one more of the tips and tricks coming up in March, not April. So please do register and sign up for that. It also will be recorded and posted to the page thereafter. And the last thing I will do is throw out a little teaser for the, twice annual product update briefing, essentially, the road map calls that our products team holds twice a year. These are, in my opinion, the best, product webinars we put on because you see what's recently been deployed, what's coming very soon, and what's coming a little further down the pike. So keep your eyes open for that. It should happen very April or the May. So know that that's coming. You can still review the one from November if you'd like. It's still a good, a good highlight. Those are recorded and kept for almost two years, I think. We hold them for a while. With that, Nick, anything else you'd add before we, say goodbye? The only thing I would like to say is, you know, start playing with conditional display logic, but make sure that you test your form and that it's, functioning exactly the way you expect it to. There's nothing worse than sending something out to applicants that isn't working the way you want it to. Test your form is becoming a bit of a mantra. I I dig it. Alright, Nick. Appreciate your time. Everyone who joined us, thank you so much. I hope you got something out of this, and we'll look forward to talking to you in March. Bye, everybody.