Summary
Join Brian Hatch as he reviews how to link your rule sets within RecTrac 3.1
Video
Transcript
The last step after creating your rule set for your registration dates, I'm gonna go ahead and save my set as a whole. So we created a brand new set, we set some parameters in there for potential registration date controls. But right now it's just a set sitting out there in a spot and RecTrac, it's not really applied to anything. If I were to go to one of my spring sessions of aquatics you'll notice that the rules are still just including an age, right, there is no other rules. So it really hasn't, I haven't introduced that set anywhere in the hierarchy. So our last step is really linking that set. So it is in play. And we decided that the season level would be the best place to do that. The season level is really considered a system code. So from my menu, I'm just going to Type System and choose system code management. And I can filter down to my season types. Okay, so in this database, we have a couple of different seasons, like auto created with a migration. So if I focus on spring, I'll just hit change. The same Tabs across the top that an activity or a section or a facility would have are still going to be located here, right, so I have the rules option at the top here. Now, rather than adding an independent rules here, I'm actually going to basically kind of a shortcut or a cheat here is I'm going to go to link set. And what I'm going to do is I'm going to choose to choose that, apply that set up already created as a template. Just when I choose that option, I have my set list. And I can just kind of filter it down. So there's that rule set I created in the previous step. And I can double Click or hit Create set template to apply it down to the level I'm, I'm at right now. So you notice now, basically, when you choose the template option, it's going to do a copy. So it copies everything from the set record down to be now independent of that set. And I could adjust these as needed. And this now applies and is going to apply throughout the database to the spring season. And to illustrate that, I'm just going to hit Save. And I still have my section open at the top. So my one of my spring sections. And if I hit refresh on that data grid for rules, you'll notice that they automatically populate. Again, because this section is linked to a season code. So I went to one place. And this could have you know, if I had 500 sections in my database that were tied to spring, this rule now essentially got pushed out to all 500 sections, I did it in one place. And it just automatically applies to all in this case, the set is using some criteria right to so even though I see my aquatics rule and my one that doesn't apply to aquatics, we know based off of their criteria, when I hover over that piece, that one of them will come into play based off of how the activities set up, and one of them won't. And we've just applied a registration dates to the season. And we could basically repeat that same step for all four plus seasons in the database. If I went back to system code management, I could lay down those same set, the same set setup. And each one could be you know, obviously adjusted once you apply it down as a template, it could be adjusted. The begin date, for example, would obviously be different per season, right? There's gonna be a start date for every individual season, but maybe even the cut offs might potentially change or the types might change depending on the season as well. But this is a very popular way to handle registration dates in 3.1 to make management of them going forward that much easier.