Index
Overview
Requirements within your Uplifter system give you control over who can register for various programs. While the most common requirements that clubs will introduce involve min and max age, gender, and similar, the system is flexible and powerful enough to introduce complex logic surrounding these factors, purchases, accomplishments, and more.
Where Requirements Can Be Added
Requirements can be adding into your system through both category levels and programs. The introduction of requirements in either of these locations is identical, but their impact can differ.
Category Level
- Navigate to Settings > Categories
- Select your desired category
- Use the Tools
to add requirements to your desired category level(s)
Adding requirements to your category levels can be completed by navigating to Settings > Categories. Here, you can select your desired category you wish to work with. Next, use the Tools icon to begin adding a requirement group and requirements to your category levels. By adding requirements to a category level the same requirements apply to all programs within that category level.
Programs
- Navigate to Products & Programs > Programs
- Select to Edit
your desired program
- Scroll down to the Requirements section
- Use the Tools
to add requirements to your program
Adding requirements to your programs can be completed by navigating to Products & Programs > Programs. Here, you can select to Edit your desired program. Next, scroll down to the bottom of the page to find the Requirements section. Use the Tools icon to begin adding a requirement group and requirements to your program. By adding requirements to a program the requirements apply only to that specific program. Please note that the Requirements section of a program is only accessible once the program has been initially created.
What's The Difference?
The primary difference in where you apply your requirements will be how wide-spread the effects are. That is, if you apply your requirements to your individual programs then only those programs will have the requirements. However, if you apply your requirements to a category level that will affect all programs within that category level.
An Important Note On Category Levels
While applying requirements to a category level will apply them to all programs within that category level, it is also true to say that a program may have more than one category level. When placing a participant into a program, the system will strive to take the "path of least resistance".
Because of this, if a program is built with Category Level A and Category Level B selected - and only Category Level A has any requirements - the system will take the "path of least resistance" and place the participant into the program at the Category Level B tier. To learn more about categories and category levels please see our article Categories.
Requirement Groups
Requirement groups are the "logic controllers" of your requirements. They will tell the system how strict to be about your requirements and how many requirements out of the list are actually required to be met in order to proceed.
A requirement group is required in order to add a requirement.
Adding A Requirement Group
- Click the Tools
icon
- Select Add Requirement Group
Adding a new requirement group can be done by selecting the Tools icon next to the desired item and selecting Add Requirement Group. For most situations the creation of only a single requirement group is needed. Once you have added the group you will want to add your desired requirements to said group. Thereafter, be sure to return to the requirement group and edit it for accuracy with regards to strictness and requirement count.
Editing A Requirement Group
- Click the Tools
icon
- Select Edit Requirement Group
Editing an existing requirement group can be done by selecting the Tools icon next to the group and choosing Edit Requirement Group. This opens the edit pop-up which lets you update the strictness and requirement count. Note that you will want to have added/removed any requirements to the group before editing the requirement group in this fashion. This is so the system knows the correct number of requirements you are working with.
Strictness
Strictness is the level of enforcement you would like your requirement group to have. This can be one of three levels:
Warn Only: A soft restriction that will show a warning when a user is checking out and does not meet one or more of your set requirements. Users can still proceed past a warning and continue the checkout process.
Prevent Adding To Cart: A hard restriction that stops users from adding the program to cart if they do not meet the requirements you have set.
Prevent Checkout: A hard restriction that stops users from checking out if they do not meet the requirements you have set.
When selecting a strictness you will want to be mindful of the requirements you have in your requirement group. For requirements like min/max age, gender, etc. you can rely on hard restrictions - even in your first season with Uplifter. However, for restrictions like achievements or category levels, you'll want to lean more towards using the Warn Only option. This is especially true for your first season with Uplifter. This is mainly because you will not yet have the history of your participants in your system as of yet, so you cannot yet rely on these types of requirements to be enforced correctly. As more seasons pass you can then increase the strictness on these requirements as you wish.
Requirement Count
The Requirement Count dictates how many requirements within your group are actually required. For example, if you had a series of 5 requirements in your requirement group you could note that only 3 out of those 5 are required. This way, your participant could qualify/pass the restrictions by having any 3 or the requirements listed.
Note that your requirement count is updated as you add and remove requirements to the group. Because of this, you will want to affect the Requirement Count at the end of the requirement adding/adjusting process to ensure accuracy.
Custom Message
A custom message can be set for your requirement groups. This message will be appended to the default error message at the bottom of the alert. If desired, the default error message can be disabled by checking off 'Exclude Default Error Message'. Please note that disabling the default message makes a custom message mandatory.
In the above example, the system notes the default message and the custom message. In the below example, the default message has been disabled.
Removing A Requirement Group
- Click the Tools
icon
- Select Remove Requirement Group
To remove a requirement group select the Tools icon next to the undesired requirement group. From the menu, select Remove Requirement Group. This will eliminate the group and all requirements therein. Please note that we do not offer the ability to undo this action so please be certain you wish to remove your group.
Copying A Requirement Group
- Click the Tools
icon
- Select Copy Requirement Group
To copy a requirement group select the Tools icon next to the group. From the menu select Copy Requirement Group. This will copy the group and all requirements therein. From there, you can move forward with pasting the copied content. Using the copy/paste options is a highly effective way to introduce the same requirement structure to many programs/category levels quickly.
Paste A Requirement Group
- Click the Tools
icon
- Select Paste Requirement Group
To paste a requirement group select the Tools icon next to the group. From the menu select Paste Requirement Group. This will paste any copied requirement group and the requirements therein. A copied Using the copy/paste options is a highly effective way to introduce the same requirement structure to many programs/category levels quickly.
Requirements
Requirements are the individual factors you would like to check against when a user registers. To add a requirement you must first add a requirement group.
Adding A Requirement
- Click Tools
next to the desired requirement group
- Select Add Requirement
- Enter requirement information
- Click Add Requirement
To add a new requirement to a requirement group simply click the Tools icon next to the requirement group in question. From the menu, select Add Requirement. In the requirement pop-up select your desired type, update the required fields for your selected type, then click Add Requirement to finalize.
Dragging And Dropping A Requirement
- Place your mouse over the category level or requirement in question
- Click and drag the item over top a requirement group
- Drop the item by releasing your mouse click
To drag and drop a requirement simply click and hold on an existing requirement or category level. Drag the item over top a requirement group and release your click. The requirement or category level will then be added a requirement to the group selected. Please note that performing this action with category levels will introduce a tiered structure in your system. This will be represented by an indentation of the category level listing. Additionally, if you have cyclical or intertwined category level requirements the system will present these individually, which may look a little confusing at first.
Editing A Requirement
- Click Edit next to the requirement
- Update the requirement data as desired
- Click Update Requirement
To edit an existing requirement click on the Edit icon next to the requirement listing. Update the requirement information as needed and click Update Requirement.
Removing A Requirement
- Click Delete next to the undesired requirement
To remove a requirement from the requirement group simply click on the Delete icon next to the requirement listing.
Note that your requirement group's Requirement Count might be affected by changes of this nature. Be mindful of the effects that removing a requirement might have.
Requirement Types
There are many different requirement types within Uplifter. Some types may not be available for use depending on your tier.
Min Age
Check Age By Month: Mark this box if you would like to check ages by month as well as year.
Age Is At Least (>=): Set the years(and months if enabled) old that a participant must be in order to register.
The Min Age requirement relies on the Age Cutoff settings you have added to your Season or Program settings.
Max Age
Check Age By Month: Mark this box if you would like to check ages by month as well as year.
Age Is: Toggle whether participants must be the age or younger, or only younger than the set max. Set the years(and months if enabled) old that a participant must be in order to register.
The Max Age requirement relies on the Age Cutoff settings you have added to your Season or Program settings.
Gender
Gender: Select the desired gender you wish to make a requirement. Note that you can update your gender options via Settings > Site Options > Age & Gender Settings.
Category Level
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the participant must meet anything but the requirement you set.
Status: The required status a participant must have in the selected category level.
Category Level: The desired category level you wish to check against.
Season: The required season if the Status is set to "Registered".
Be careful with your strictness settings when it comes to this requirement. If your Uplifter database does not contain historical data for your athletes yet then "Prevent" strictness options may stop valid registrations.
Achievement
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the participant must meet anything but the requirement you set.
Participant Has Achieved: The required achievement that must be completed before a participant can register.
Participant Product
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the participant must meet anything but the requirement you set.
Participant Has Purchased/Enrolled In Product: The target purchase the participant must have made.
This requirement option focuses on the individual participant's purchases/registrations. To focus on a per-account basis (often synonymous with a per-family basis) please see Account Product.
Account Product
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the account must meet anything but the requirement you set.
Account Member Has Purchased/Enrolled In Product: The target purchase the account must have made.
This requirement option focuses on the whole account's purchases/registrations. To focus on a per-participant basis please see Participant Product.
Participant Value
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the account must meet anything but the requirement you set.
Participant Must Have A Value Entered For: The target custom field that a participant must have a value entered in.
Please note that this requirement does not validate what has been entered into the field, only that there is a value.
Skate Canada Season
Requirement Should Not Be Met: Toggle this to invert the requirement, meaning the account must meet anything but the requirement you set.
Participant Is Registered in Skate Canada Season: The season you wish to target with the requirement. Note that this drop down is updated by the Skate Canada database, so if their latest season is not available then it will not be an option to target.
With: Focus your targeted season to a specific Skate Canada section.
And With: Focus your targeted season to a specific club. Note that this drop down is updated by participants registering with your club and connecting with Skate Canada.
Requirement Maintenance
Does your requirement group look something like this?
Unsorted requirement groups are rarely impactful. If you would like to rely on the system to enforce your requirements you will need to ensure you requirement groups are clean and concise. Let's take a look at some actions you can take to cleaning these items up.
1: The parent requirement group. All requirements and additional requirement groups will be children of this group. This item is required and should not be removed if you wish to use requirements for this program/category level. Please be sure the strictness and count are accurate to your desired outcome.
1.5: Requirements that are direct children of the main requirement group. If you are not using Either/Or Requirements this is the position your requirements should be in.
2: A superfluous requirement group. A child of the parent requirement group (1) but without any requirements of its own. An empty group like this will only have negative effects on your requirement logic. It can/should be removed by selecting Tools next to the group and choosing Remove Requirement Group.
3: A requirement group that is a child of the parent requirement group (1). It has its own requirement, but since there is only one requirement in the group, this structure is not needed. It can/should be removed by dragging and dropping the child requirement to the parent requirement group (1), then selecting Tools next to the group and choosing Remove Requirement Group.
3.5: A requirement that is a child of a secondary (child) requirement group. If there were multiple requirements within the requirement group it may make sense to retain it for logical applications. However, given that there is only one requirement listed the steps outlined in point 3 should be followed.
Requirement Setup Examples
Below are some example setups that can be created through the use of requirements. These examples can be augmented to your purposes, but if you are not sure how to do so, or if your desired use case is not shown below, please don't hesitate to reach out to us for assistance.
Tiered Category Levels
Tiered categories can help you ensure that your registrants are being placed into the correct category levels when registering. By tiering your category levels you can ensure that only those that have completed the previous level can register in the next. Note that new organizations should only use the Warn Only strictness with this option, as you will not have any historical data to rely upon.
Add Requirement: Navigate to Settings > Categories and select the Tools icon next to the category level you wish to add your requirement to. Select Add Requirement Group, then select the Tools
icon beside the new group and select Add Requirement. Select the Category Level requirement option. Select your desired status, then target the desired category level and click Add Requirement.
Add Requirement (Drag & Drop Alternative): Navigate to Settings > Categories and select the Tools icon next to the category level you wish to add your requirement to. Hover over the category level you wish to make a requirement and click and drag it to the new requirement group. Drop it once you see the green check mark and the system will add it as a requirement. Note that if you would like to use a category level from another category you must use the standard method instead of drag and drop.
Invite Only Restriction
The invite only requirement setup ensures that only participants your team have marked as "invited" may register for programs. This is best used on a small scale - restricting a handful of programs or a category level or two. However, this can also be used for priority registration if desired. Though, often alternative Priority Registration options are better suited for a larger, more global effect.
Create A Custom Field: Navigate to Settings > Global Settings > Custom Fields and create a Participant Field called "Invite Only" (or your desired name). Leave all "Where does this field appear?" check boxes unchecked. Set the Field Type to Free Form Text and leave all radio toggles to No. Click OK and be sure to click Save All.
Add Requirement: Navigate to Settings > Categories to affect category levels or Products & Programs > Programs to work with individual programs. Click the Tools icon and select to Add Requirement Group. Click Tools
next to the new group and select Add Requirement. Choose the Participant Value option and target the new Invite Only field you created. Click Add Requirement, then select the Tools
icon next to the requirement group again. This time, select Edit Requirement Group. Update the strictness to Prevent Add To Cart and ensure that the count is set to All and click Update Group.
Invite Participants: Finally, navigate to People & Accounts > Participants and enter the profile of each participant you wish to invite. On their profile you will now see an Invite Only field, visible only to you/the admin team. Add any value to this field to invite them. Remove any/all values from this field to remove their invited status.
Either/Or Requirements
Either/or requirements offer the ability to meet either one set of requirements or another in order to complete registration. This can be quite handy when there are various ways a user can qualify for registration.
Add Requirement Groups: To begin, you will want to add your initial requirement group to your program/category level. Once this is added, you will want to add one child requirement group for each optional series of requirements. For example, if someone can either "be 3 years old and have passed Category Level A" OR "be 5 years old" then you would add two child requirement groups.
Add Requirements: Once the sub-requirement groups are added you can then add the desired series of requirements to each. The below GIF is just an example, the requirements you add can be anything you need.
Update The Requirement Groups: Once your requirements are in place you can then begin to update the requirement groups to ensure their counts are accurate. For your parent requirement group, you will want to ensure that the count is 1, as this indicates that any one of the requirement groups within can be met in order to proceed. Your child requirement groups can then have their own counts based on the requirements therein. Note that only the parent requirement group can have a strictness.
Limited Registration
Limited registration requirement setups allow you ensure that participants are only registered for a small number (or even only 1) of programs. In this way you can help assure that more program spots are open for more people during restrictions on capacities. Limited registration can also be used for halting registration in opposing programs.
Add Inversed Requirements: Navigate to Products & Programs > Programs and select to Edit one of the programs involved in the limited registration. At the bottom of the edit for click the Tools
icon beside the SKU and add a requirement group. Click the Tools
icon next to the group and select to Add Requirement. For each of the programs involved including the one you are currently editing, add a Participant Product requirement that has "Requirement should not be met" selected and the program targeted. Click Add Requirement to add each once ready. Note that it is often best to list the program SKUs involved in a notepad so that you have quick and easy access to them during this process.
Update The Requirement Group: Now that the requirements are in place you can select the Tools icon beside the requirement group and click on Edit Requirement Group. Here you can update the strictness and count as desired. It is recommend to use Prevent Add To Cart as your strictness in this case. Further, the count you use will depend on your situation. In general, the number you select here is based on the number of programs a participant is allowed to register for. You would subtract this from the max number of programs to find your count. That is, if you had 3 programs involved and participants can only register for 1 each, then you would set the count to 2 (total programs - max registration for each participant).
Copy/Paste Requirement Group: With the requirements established on one of your programs you can now copy and paste it into other programs. For this, you will want to select the Tools icon next to the requirement group and select Copy Requirement Group. Next, navigate to Products& Programs > Programs and select to Edit
each program involved. Scroll to the bottom, click the Tools icon next to the SKU, and select Paste Requirement Group.