RecChat: Rules Allow/Disallow and Not Mode - 03/30/2023
Table of Contents
Episode Summary
Join Zach, Bret, and Julia while they discuss Allow Rules verse Disallow Rules and how Not Mode fits into the mix. The group highlights the different use cases for each rule type and walks through how to set up these examples.
Recording
Transcript
Bret Alarcon 0:08
Hello and welcome to this week's edition RecChat. I'm your host Bret Alarcon. So in today's RecChat, we're going to be talking about rules, specifically rules that allow disallow and the not mode. So before we start, if you have any questions, please ask them in the live q&a section. That's a little q&a Button down at the bottom. And if you give us a question, we'll hopefully give you an answer and to help out with the questions. Julia is here, so she should be able to help you out there. With that, I'll hand it over to you, Zach, how you doing?
Zach Malloch 0:40
Not too bad. Bret Alarcon? How are you doing?
Bret Alarcon 0:43
Doing All right. Did I say other con? Oh, my gosh. I don't know.
Zach Malloch 0:49
It's okay to be a little out of it today.
Bret Alarcon 0:50
Yeah.
Zach Malloch 0:51
In a week. And yes. But happy to be here with everybody. And oh, there's already a question. What's going on here, Nancy? Yes, of course, it's great intro music written and performed by your very own Vermont systems employees actually. Thank you for that. It's always nice to, to hear that. And it's always fun to start RecChat with that awesome sound. So yeah, we're going to get into rules. And so these are kind of, normally when I do a rules training, it's, it's an hour long, at a minimum, we get into all sorts of different elements of it. But I wanted to focus on one really kind of core piece of understanding when it comes to rules. And so to do that, I have a couple of examples that we can run through right here. So as we go through, of course, at any point, go ahead and ask questions, I should be stopping every so often to ask if there are any questions. But if there's something really important, don't worry about just shouting over me. But we'll try not to need that. So in this case, we have a very basic item here, it's an inventory item, it's a t shirt. And let's just say for some reason, I wanted to make it so that I can only sell this to people who are between the ages of 12 and 20, it probably doesn't make a lot of sense. Maybe it's 12 to 18. And it's you know, teenager sort of stuff, or whatever the case is, whenever we make any rule, the first option we choose is whether it's an allow or disallow and the essential operation of this is based on the criteria, if you match the criteria, does that mean that you're allowed to do this transaction? Or do you want to specify the criteria that prevents you from doing the transaction? So I'm going to come back to this several times. But when I started looking at rules, and this was even way back to when we were developing 3.1? And, you know, initially presented with well, how do we train on this, it struck me that rules operate very much like sentences. So for somebody that's 1218 years old, to be allowed to purchase this, they have to match whatever the criteria are.
Zach Malloch 3:00
So in this case, we're saying to be to purchase this item, you're not allowed, you're disallowed from purchasing. If you match this criteria, or you can say to purchase this item, you're allowed as long as you match this criteria. So that's one of the main things to be aware of is what does the criteria do? Does it criteria to find those who can make the reservation or the purchase or the registration? Or does it define specifically the people that can't and there are certain situations where one is easier to define than the other. But there are some things to be aware of when we're doing this. So I'm going to start just by the way that I would do this, I think it's the most solid, the most resilient, when I talked about resiliency in rules, it's how likely is it to cover all situations and not allow somebody that kind of sneak through because we weren't anticipating something. So if I'm adding an age criteria, and I said it's between 12 and 18 years old, I would say between 12 and 18.99, right there, effectively, when we're putting in an upper age limit, it's just saying less than the next number. So this is the highest value that still counts is less than 19. Of course, we have our transaction date available there. But this is just the basic thing, as of the day that you purchase this this item, the only people that are allowed to purchase it are those that are older than 12 and younger than 18.99 younger than 19 effectively. So if we go to global sales, actually, let me save that record here first.
Zach Malloch 4:40
And we go to global sales, and I have somebody that's 30 years old, so they're outside of that range and I add it to the cart and I get a conflict. If I find somebody that is actually I don't think in this know in this household, I don't have anybody so let me make it 10 years real quick just so we can have a valid registration Once again, we're not trying to make this an actual rule for anybody's database, so I can play with it to make our examples work. So let's make it 10 to 18.99. And save that. So in this case, anybody that is not between 10, an 18 years old, for example, our initial guy right here, is not going to be able to register for it. So you have to be between 10 and 18.99. And he is 30.25, which, of course doesn't work. If I find somebody who is 10 years old, and add that to the cart, it gets in the car with no conflict whatsoever. So there's a couple of different ways we could potentially look at this. And I don't think it's necessarily something that anybody would do in this particular scenario. But hopefully, it defines some concepts that will be useful later on. So we could also while in this allow mode, technically speaking, let me scroll down here and change this. So we can try making it zero through 9.99. Make it a disallow, so you're not allowed to purchase this if you're under or if you're between zero and 999. And then the initial thought here would be to go to age and then put in the upper limit of it as well. So we don't also we don't either want to have anybody purchased this, that's over 19 years old. And so that, you know, we the only Window, the only thing that's not disallowed is that 10 to 18 years old, that's kind of the gap that we left between these things. So if I save that, and then go to global sales, and then try to add this person who was definitely outside of that range, and added that to the cart, well, it happened, we don't have any conflict happening right there. And that is also, I think, easily illustrated by considering the and are considering the sentence structure, especially if we understand that there is an end between all of our criteria. So you're not allowed to purchase this item if you are from zero to 999. And you are from 19 to 99.
Zach Malloch 7:20
So, in this case, you're always not both of those, if that makes sense. Nobody is both eight years old and 25 years old, that would be the requirement to make this actually work in the way that is configured right here because we have saved this and that. Now, if we got rid of the second criteria, we could still kind of make this happen. So we save that. And then we can clone it. And because we're making a separate rule, then we're not having that same and kind of thing happened with the criteria. So I'll just move this to the exact same settings 19 through 999. We'll hit save, and then I'll save that record. And so we go into global sales, and we try to add this to the cart for somebody that's outside of that range. And here we're getting a conflict on one of those two disallows. So they're not getting prevented from registering this because they're under 10 years old, they're getting prevented from registering for this because they're over 19 years old. And so that is kind of splitting those out. So what's happening here is within a single rule, all of the criteria have an end in between them. And actually, I'll just bring up a point out one more thing, that's a different big difference between disallow and allow you notice that with the disallow, we have no org groups, if we have allowed turned on, then we get this rule group, these are all groups that we've got available to us. The reason for that is when we switch to disallow, it kind of only uses the or if you've if you're disallowed from a single rule that's going to prevent you from registering. So you don't have to say, well, you can be disallowed from this rule or from that role, and either one of them will prevent you from registering because that's just the default of the way that the system works. So with disallow mode, you do not need an or group. So hopefully that makes sense. So if we're reading these as two separate sentences, we're saying you're not allowed to register you're not allowed to purchase this item. If you are old If you're between zero and 9.99 years old, and you're also not allowed to register this for this or you're not allowed to register for this to purchase this if you're between 19 and 1000 years old effectively. So that this is completely valid totally okay to you know, we probably change these rules descriptions and this is a not if you were under 10 We can even just say for this one, not if you're over 19.
Zach Malloch 10:12
So, you know, that's this is completely as I mentioned, it's completely valid. But we can get the exact same function in the system by specifying what somebody is allowed to do. So we'll say between 10 and 18, we'll just put in the same exact criteria we had before, which is a single age criteria, and the 10 to 18.99. So we can kind of see where maybe I'm hoping and you know, certainly give me feedback. If you're still confused about anything. If you have questions about things, we're we'll keep going, we'll have a couple more examples and the like. But when you're saying allow, it is basically saying the only people that are allowed are the people being defined by the criteria below. When you're saying disallow, you're saying the only people that aren't allowed are the people being defined by the criteria below. So by putting this in and saying you're only allowed if you're 10, to 18.99, the flip side of that the system understands is that anybody outside of that range is then not able to register. So in this case, it's easier to put this one value. And just as a little shortcut, a lot of times people are trying to figure out well, how do I actually Build a rule? And once again, even for that, I suggest starting with the sentence, if somebody called you and said, I want to buy this t shirt, can you tell me who's allowed to buy it? You would probably more quickly say, well, you're allowed to buy it. If you're between 10 and 18 years old, you would probably not that?
Bret Alarcon 12:06
Looks like we might have lost Zach. Let's see.
Julia Shefcheck 12:11
Yes.
Zach Malloch 12:12
Julia, can you see me?
Julia Shefcheck 12:14
Yep, we can see you now. You froze there for a few seconds.
Zach Malloch 12:17
I was a little bit worried about this. There's some utility work going on outside my house. Hopefully, we don't run into any other issues. Can you tell me where you lost me? Like 10 seconds ago. Okay. So I was talking about the way to describe to a customer, what the conditions under which you're allowed to purchase something are and how you're more likely to say you're allowed as long as you're within a particular range, rather than defining all of the conditions for which you're not allowed to do something. So that's a really good kind of shortcut, especially if you're starting from scratch, you're trying to figure out how to Build this rule. Start with the way it's defined in your brochure, or the way that you communicate these requirements to your customers. And that will probably give you some hints as far as how to set it up on the rule. Now, in technically, this is completely redundant, but this will still let exactly the same transactions go through or give you the same Prevention's. It's just we're having additional. So I'm outside of the allowance I'm outs inside the restrictions, it's just giving me more. So it's not breaking anything, it's just extra from what we would technically need as a minimal level. And this guy will be able to register with no prompts because they are not in the disallow and they are within the Allow. But once again, you'll only have to define one side because RecTrac assumes the other. So let's go ahead and delete these. And we'll start talking about the not mode. And the not mode really for me. There are certain rules that you can only create with using the not mode. But there's also some times when it's okay to use either a rule being defined with the not mode or without the non mode, sometimes you can get that extra resilience, the extra level of will make sure nobody slips through these cracks, Type of ideas the way that I normally describe it. So let's say that we have a rule here that says residents can register early it's one of the most common things residents can register early non residents have to wait to register. So we'll say residents can purchase April 1. So we're going to allow this if you are a resident and rather than using category, let's just make well actually let's just use this category because it works in this situation. So if your household category is resident then you're allowed to purchase this item and let's also just put that transaction date in here.
Zach Malloch 15:03
Let's say on or after April 1, right there. Okay, so by having this rule, if we only had this rule in place, you would only be able to purchase this item, if you're a resident, and it was after April 1, if you were non resident, you would never be able to purchase this because the first piece here says you have to be resident. If it's before April 1, nobody is going to be able to purchase this because this part is saying that it has to be April after April 1 for residence. So if we save that, then the flip side of this sorry for the coughing, I'll Click on that. And I can say that, let's just say it's going to be for eight, the week afterwards. So non residents have to wait a week after residents start. So then we can say this is non resident, save that, and then my transaction date, I'll just push out to the eighth. And save that. So now this covers our resident in our non resident transactions. But in my case, in this database, and a lot of people's databases, you might have more than just those two distinctions. So if I go to household management, and I look at any household that I've got here, this is going to be I believe this is a resident household.
Zach Malloch 16:44
But you can see that my categories are not a binary, it's not resident or non resident, I have nonprofit, I have military, I have a faculty or staff household, I have a department household, I have potentially an affiliate household student household, Park District resident may be different than a city resident. So a lot of people run into this situation, maybe not with categories, maybe with fee codes may be with membership types, where it's not just one or the other. So now if I wanted to try to take all that into account, I could just come into this, I need to change the description to make this one, say non resident. So I could go in here, and I can update this category criteria. And I can just make sure that I'm selecting all of the categories, aside from resident, so resident is the only one that's not defined here. And then I hit Save. And so now this will get me what I want to do. But let's say, mid year, next year, we have a board meeting, and we define that there has to be a different category for households. If we create that additional category, then we're going to run into the situation where we have to come in to all of these criteria, we have to open these up wherever they're assigned, whether it's activities, facilities, whatever. And we have to make sure that we add that new household category to this list. Otherwise, if somebody with that category tries to register for this, they're not going to find any allowances. And they're just never going to be able to register. It's that falling through the cracks. You're not accounting for somebody of that configuration registering for this particular program. I see there's a couple of questions, let me just get through this real quick here. The other way we could do this, that would be future proofing, the resiliency I talked about here is to turn on the not mode, and leave this as just resident. So anybody that is anything other than resident is now what we're defining here. So if we save this, you say if you're a resident, you can register anytime after the first if you're anything other than resident, then you can register after the eighth. And so, six months later, I create another household category. year later, there's another two or three, I never have to come in and update this criteria. Because no matter what those new categories are, they're definitely not resident categories. So this still works for all of those. So a little bit of future proofing there. And, Julia, do we have a question here?
Julia Shefcheck 19:11
There's just one question Heather's asking, why would the rural district description say resident purchase on 4/8
Zach Malloch 19:18
that's just me forgetting to update that part of it. So now that I saved that I just updated the description. You are still responsible for the description, it's not going to grab the the criteria and then Build a description out of it. So that was just me because I cloned this I updated the date. I forgot to put the non in front of it beforehand, but good question and keen eye for detail. Heather. All right. So that's not one of the other things that's maybe a little bit more persistent with this like, so this is baby swim. And let's say that you have to have an aquatics pass as an example. So we can have a rule And we'll say it's a new blank rule. And maybe member registration gets to start early. And so it's the same idea of what we had with the other one, I'm just going to use past prerequisite as my option here. And they can add that criteria. And so I could say, you know, my pass code or my, and then find all of my passes that have anything to do with aquatics. And let me just say, a queue here and make sure that set to contains is I guess, I don't have the word aquatics in anything. Maybe you have some pool or swim. Had a lot of passes, but nothing specific to what I'm looking for right here. Let's just, let's shift it just slightly and say that you have these happen at the fitness center, you have to have somebody in your household has this fitness pass. So we do that. And we can choose all of these four passes, and then hit Select. And then we can hit Save. And so anybody that registers for this has to have one of these passes. And then we would probably also have, you know, a days from so your your date specifically. So you're allowed to register for this more than 21 days before the registration date, I actually probably would use a particular transaction date for this.
Zach Malloch 21:33
And then we can come in here. And once again, maybe we can say you're you're able to register for this a little bit early on the first if you have one of those memberships. And then we can save that. And then once again, I'll try cloning this. And that's why that description stays the same to begin with, I just have to adjust it so that I can say, non member reg starts late or I put in the specific date or whatever, I come into here and adjust the date to the next week. And then I would come in here and I would make sure I'm choosing everything except for the fitness passes. Or, as we just learned, all I have to do is turn on this not mode. And I'd say as long as it's not one of those four, because it would be the same situation if you create a new membership Type. And you're specifying only people that have the the fitness passes can register early only people without with these other passes that are not fitness can register late and you created a new pass. If you don't come in here and update all of those rules with all of that criteria, those people that purchase a new pass, we'll never be able to register for this because they're never matching either of those conditions, having this specific list of fitness passes, or this specific list of passes that don't include fitness. And also don't include the new one that you just created. Because we don't auto add it.
Zach Malloch 22:57
So the not mode can be a super easy way. And you know, it's kind of that managing one thing versus managing many things. Sometimes it's easier just to put one thing on its head. That is saying you can't do these four, rather than saying you can do these 96. So just a different way of looking at things in a very powerful option to have available to you. And that's kind of the core of what I wanted to talk you know, this is a half hour, we don't have the time to get super deep into everything. But I think it's a pretty important thing and hopefully get some kind of curious if anybody wants to share. If if you see a new way of looking at rules based on considering that or is this just something that was you know, really basic, of course, we all understand that that's kind of the first thing that we learned. And it's a it's a lesson that we're all deeply aware of. Or if there are any questions, I'd be happy to answer those. And if there's no comments, feedback or question, we can certainly give people just a little bit of their time back today and and slightly early. Not seeing any feedback out there's Okay, so people have been asking for. Okay, great. So Heather's saying that they've been inputting the disallow rule for non resident registration, and just turning on the non resident might be an easier way to do that. So that's awesome. Sandy is asking for a brief description of what the fixed mode is because this definitely on every criteria, you have that not mode, and you also have this fixed mode. Now, I used to have a joke that you know, when something's easy to understand, you'll see that the help explaining what it is is pretty concise. And when something's difficult to understand the help explaining it is sometimes pretty in tense. So let me just find that area here. So there's not no there's our fixed node. So you know, not mode kind of complicated fixed mode. However, we've got a lot of different kinds In the considerations and understandings of it, it can basically be explained with these two images. And I think that we're still working on avoiding some 404 errors. Yeah. But basically, what the, the most concise way I can describe it is don't show people the stuff that they can never get around. So if there is a rule that says you have to be a resident to register early, there's no reason to tell non residents that they have to be a resident to register early, like they're not going to move just to register early, there's no reason for showing them that information. So in that case, if it's resident versus non resident, or you know, the the member versus non member, we would probably turn that fixed mode on for the part that define somebody as a member or a non member. So if somebody doesn't own er, it's really, I think, when you're doing more of the binary of the resident versus non resident. And I would say use it sparingly. And you probably will know when you need to use it when you do some test transactions. And actually, I see this is kind of related to it. So Missy is asking if there's a way to just to change the wording of the rule.
Zach Malloch 26:18
And absolutely, as of 3.1, point one, or point 10 point 15, we have this custom rule display. So anything you Type in here will display on WebTrac. Instead of just explaining like the criteria kind of almost the machine language that we use the logic language that defines what these criteria are. So yes, missy, you can absolutely use this custom rule display for that purpose. And we actually have a RecTrac, where we talked about WebTrac registration events and custom rule displays. So we have that in the archive as well. But getting back to Sandy with the fixed mode, if you have two rules, it's almost always when it's just one or the other. So resident or non resident, because you can very specifically saying we don't need to show the non residents, the resident message, we don't need to show residents the non resident message. So pretty clear to to choose those. If you use it too much, you could potentially be hiding messages from people. So they they can't add something to the cart, but it doesn't show them why they can't add it, add it to the cart. So if you have things happening like that, make sure the fixed mode is turned off. If you have people registering and they're getting confused as to why they're seeing all of this extra information for people who aren't, then that's when you would want to turn the fixed mode on. So it's kind of like, only show the right people this thing. And that's kind of what the fixed mode is for. Let's see, Shen DS, I hope I'm pronouncing that right. For your original t shirt sale rule, you had a shirt that was for sale for zero to nine, nine years old, 9.99 and 19 to 999. And after the 10 to 18, would you please show how you would use the org group to make that rule. I think in in this case, I probably would not suggest using an or group because setting it to allow is just going to let you specify the gap that is in there at the 10 to 18, which is the really the core piece of what you're trying to say is only people who are attend to 18 can register for that. The key piece as far as when to use an org group is when you're understanding that each criteria has an end attached to it. So if I had another let's say another criteria here that said like the age let's say let's use the same thing, 10 to 18.
Zach Malloch 26:39
So you have to be between 10 and 18 years old when you're registering for this. And you have to have one of those passes and it has to be after or and it cannot be one of those passes. And it has to be after four 823. And you have to be over 10 years old. So that's great. But let's just say for an example that I forget to go back and add that same age rule to the member start pieces. In that case, I'd probably want to break out the age rule to be a separate rule. Otherwise, I'm replicating that criteria in each kind of separate registration Window that I have there. The other way that we're using or groups is potentially when you have something that is it's an incompatibility if you have all of those ads in place. Let me see if I can pull up my rules PowerPoint real quick because that's probably going to have this spelled out a little bit better than I can just come off on the top of my head here. Well, actually, no, I don't even need to do this. The resident versus non resident piece. Not if you're using the not residence option. But if you're actually specifying residents can register on this wait this date non residents registered on this date. So that's sorry for my little confusion with that, but that's my biggest thing. So you notice all my registration pieces here have an org group to them. So non resident WebTrac WebTrac, starts resident WebTrac starts non resident RecTrac, and resident RecTrac. So, once again, let's consider that. And that's between everything when we're using the VI allow. So this is saying, we'll just look at RecTrac by itself here. So you have to be after January 1 2021, at 8am. And you have to be non resident, and then this one is saying you have to be after January 1 at 8am. And you have to be resident, but there's an end of between those rules also. And if we ignore the dates, it's basically saying to register for this, you have to be a resident, and you have to be a non resident. So that's when we're putting in the order group that allows us to get rid of that and and make it an or when we split between those rules. So you have to be a resident on this date, on or after this date. Or you can be a non resident on or after this date. So that's, that's when the order groups really come into play. Hopefully, that helps out. John makes a very good point that using the proof report for activities, Point Of Sale items, facilities, etc, helps you look at the rules that you have set up to make sure you have consistent rules. So the proof reports, I have to go to report output to get those.
Zach Malloch 31:38
So either from management or from listing, if I Type in proof here. And this is kind of a key that it's it's almost always like the setup reports is what it's going to say for the module. And you see that it says, fees, rules, questions, I'm just going to run this real quick because you this is a little bit different than most reports where you kind of get to make a choice after you hit process. So let me just choose one thing to make it simple. I hit process, and then it's asking, What do you want to prove. So if I'm really just focusing on rules, I can say just include rules. And I want to include the I want to see if there's a custom rule display, I want to see what it's linked to, if I'm needed, if there are any permissions, I want to see if it's a rule tight. You know, so putting on these different pieces, I think like criteria is an automatic piece that you're including. Or I would probably start with everything and then start to pare it down from there a little bit as you as you go. But this will list each activity section with all the rules and show whether they're linked at the section or at a higher level. And it is very good in RecTrac, you kind of have to go activity by activity, edit it, go to that Rules tab. This is way of doing it where you don't have to go into a section, close it go into next section, close it, go in the next section and close it, you get it all in a report. So very good point, John.
Zach Malloch 33:05
Let's see, so Shana is asking if there's a criteria that forced a one hour cleanup time after a facility Rental, we currently have that set up in the facility itself, but it cannot be overwritten. And sometimes you want to be able to override it. So there is a way to do that. Let me clean some of the stuff up here. Want to get into a facility to edit, that should clear it up. Alright, so if we go to facility management. So the first thing that I'll put in here, or I'll point out, is that we have this setup and cleanup minutes. So if you put your cleanup minutes as 60, it's going to include an internal reservation at the end of every reservation you make. So it would cause a conflict if somebody tried to make a reservation sooner than that. So this might be an easier way for you to do it. If you're especially if you're not worried about over. If you want to be able to override it, sometimes it's just a default. So this, let me turn off that court option, I leave the 60 Minute clean up. So this is facility room 440. And I'll save that. I'll go back to global sales here real quick. And I'll go to facility and room 440 should be up towards the top. There it is. And you see it just takes this as a default. So if the staff person making this reservation wants to change it to 30, they can just make that change. It's not. It's not preventing that. So if you're looking for that override, there's that possibility to do that override very easily from here. If you're looking for it to be a rule, this will get a little bit more complicated. Maybe we'll have a whole RecChat about the advanced criteria, because that's certainly one that could use some more explaining. But there is this option. Let's just call it It hour between reservations.
Zach Malloch 35:10
Okay, so you're allowed to reserve it as long as there's at least an hour between the start time of your reservation and the end of your last reservation is what I'm assuming you're looking for here. So if I go to the Advanced criteria, then we can decide who we want it to be within. So is it just within the household, you have to have an hour between? Is it between any other resident reservation, you have to have an hour between any other non resident reservation or member reservation? Or is it just everything, you have to have an hour between this no matter who it was that made the last reservation. So we'd say one, and then I, you know, this is one that I'm not there yet hours between is, is the value that we're looking for there. And then I'd come down. And I could say, like, I could specify how many facilities we're really looking for, including with this is it all facilities, in which case I just make this rule at the module level, and then it links to all facilities below it. Or I could say, any facility that has the category of the item that's currently selected. And then this is just the has to have at least one hour between your Facility Reservation here, or any Facility Reservation of the same category. Or once again, you could have a facility list or facility Type subtype category, or all facilities if you want it to. So that is how I would do it. And then because we're adding that criteria to a rule, then it still has all of the same override options, so you can make it so you have to have rights to override it, or you're just not allowed to override it or whatever the case might be. All right. John also recommends the transaction simulator, absolutely, we have an old RecChat about that, I know that there was a period of time where it wasn't getting results very well. But I believe that was fixed in either 16 or 17. So as long as you're on one of the more recent versions, then transaction simulators are really good way to do it. Particularly if you have a lot of trans or a lot of rules that are you can't do it until a certain date, you can put in a test date. So you're basically doing test registrations as of a particular date. So you don't have to worry about like trying to advance your system time and causing all sorts of complications that that would run into. And I think that that is.
Zach Malloch 37:29
So there's one more question here. And it's talking about linking sets. So this Button right here. You know, I think sets will also maybe make sense as a separate topic. But essentially, sets are a way of grouping either rules, fees, or questions together. So that you can assign them as like five different rules at one time without having to manually create them and assign them every single time. So I'll just try to get this done by I'll try to see what I can do in four in three minutes. And then we'll wrap things up. But we have set management. And when you create a set, you're creating either rule fee or question. And so we have that as a drop down option. And that changes what DataGrid we have down here right now. So you know, so this is asking for fee Type. So this is a Field DataGrid. If I change this to questions, then it's going to be a question DataGrid if I change it to rules, then it's going to be a rule DataGrid. So I can Build out four or five different rules, or even two or three, or even one rule that you're just using a lot would make sense to come in here. Let's see what a good one I have. Let's see if a drill has a couple of multiple things. Well, it's only got one thing set up here. Let's go to I think open and close times. Now this one, this is a little bit complicated. And this is one that I use as a test fairly often. So we have different age ranges, we have male enrollment, only resident enrollment only. You know, I haven't updated all these descriptions. But let's see what happens when we use this. So the description is called adult male resident only rule set. So when I save this, I go back to let's say the facility that I was working on. And I'll go ahead and add that as a set. So I have these two options, link it as a template, link it as unchangeable template means I'm going to post put down those four rules and then I can edit them in any way I want to once they're here, linking the set, lets me link those rules. But then I can't change anything at this level, I have to change it at that set level. So a lot of times we'll have admin come in, Build the sets that they want their people to use. And then when your coordinators can actually Build their activities. They can only pick from this list of predefined rules, and that will hopefully save some some work. So if I only get a template, once again, it's this adult male resident only.
Zach Malloch 39:59
So Once again, any of these, I can edit, I can change, I could delete one by itself if I wanted to. So it just copied, it's like a real quick clone to put those into place. So let me just go ahead and delete the rest of these. And then I'll link it as a unchangeable, and then we'll go ahead and wrap things up. So let's link that also. Alright, so let's link it as unchangeable. And we'll see use that same one. And you notice that it doesn't have the Edit Column, I can't edit right from here, if I clicked one thing and then tried to delete it, it's going to tell me that I delete the whole thing if I delete one of these, because it's an unchangeable set. Now, that being said, there's a benefit to this, let's say male enrollments only, we'll just highlight that I'll come back in here to set management. That was a rule set. So I'll filter this enrollment looking at the rule sets. And let's edit the male enrollment only rule. And we'll make this male instead of female. Or let's say that we would go yeah, in this case, we'll say, we could also just say anybody that's not a female, more and more often, we need to define things beyond just the binary, I hit Save. And so anywhere that this set has been linked, if I now refresh this, we see it's updated that that criteria. So it's, it's kind of two things, it allows you to pre Build your rules or fees or questions. So they're easier to assign later on, rather than having to rebuild the same thing over and over. And it's the ability of saying you can grab this in its finished state, and you can just link that one thing. You can't edit it, you can't change it. But then if we do change it at this core level, we know it's going to change everywhere else out in the system where it's been assigned. So that can certainly save a lot of work potentially, depending on your use case. So that's what sets are, they are ways of defining things early, so that they can be used over and over and hopefully save a lot of time based on how you use them. But very good question. Hopefully that five minute explanation. Made some sense. All right. So I think that that's going to wrap us up. If Julia or Brett, if you have any closing thoughts, I would invite them otherwise. Brent, I think we're ready to go in for a landing here.
Bret Alarcon 42:32
Take care everyone.
Zach Malloch 42:33
All right. Thanks, everybody.
Julia Shefcheck 42:34
Thank you
Delete