SquadFusion registrations allow you to configure many registration options. You can easily build forms tailored to your registration needs.
We also allow you to include your own processing rules, in the Rules tab. Rules allow you to conditionally set the display of fields and field choices. They also allow you to conditionally increase, decrease, or set the registration fee.
For example, let's say you are creating the registration for an upcoming league. As part of that registration, you ask which days the participant is available for practices.
But for participants 6 years old or less, you only have facilities on Monday and Wednesday, plus you charge them $25 less than everyone else.
You could provide instructions for those under 6 to only pick from Monday and Wednesday. And you could add a 2nd fee option for them to pick, which is $25 lower.
Using Rules, you can hide all the days other than Monday and Wednesday so they don't even have the option to pick an invalid day. And you could automatically reduce the fee by $25 so people don't pick the wrong one for their participant age.
If you have done programming or have included formulas on spreadsheets, you are familiar with If-Then logic. Essentially, registration rules do the same thing. We call it Triggers and Actions.
You define a trigger and specify what to do when that trigger is either met or not met.
Triggers
Triggers can be based on participant fields, prior registrations, or program assignments. Most of the rules we see have participant triggers. In the example above, the trigger would be on the participant field birthdate. And the setting for it would be to trigger the rule when the birthdate is less than whatever date makes them 6 years old (league age, age on registration date, etc.).
Actions
Actions are what happens when the trigger is met. In the example above, when the birthdate is greater than the birthdate which makes them 6 years old.
You can set Actions for registration fees and participant fields.
in the example above, you would actions on participant fields to hide the days not applicable to 6 year olds and also to decrease the fee by $25.
The actions and triggers should work in concert. For instance, you could set up for a rule based on the birthdate trigger of birthdate being greater than or equal to make them 6 years old, and a lower price for 6 year olds or younger.
- Main registration fee is the higher price. Reduce the fee by $25 when the trigger criteria is met.
- Main registration fee is the lower price. Increase the fee by $25 when the trigger criteria is not met.
Conflicts/Duplicates
You may have multiple rules acting on the same thing. For instance, if you want to add $15 to the fee for every item the user checks on the registration, you will have multiple rules, with different triggers, all increasing the registration fee by $15.
This is a completely valid (and common) scenario.
In this case, you want them all to be triggered.
It's also possible to write rules in such a way that even if the triggers are met, the action cannot be taken (or more accurately, the action can be undone).
For instance, let's say you have one rule which sets the fee to $100 for anyone whose favorite color is red. And you have another fee which sets the fee to $75 for anyone whose favorite number is 7.
Only one of these rules can be applied, since they set the fee to different values.
Similarly, you may have a rule which hides a field and another rule which makes the same field visible. If both rules' trigger conditions apply, only one can process.
We apply the rules in the order they appear in the Rules list, and the last one "wins."
So in the example with the color and number, if the first rule is set to $100 for red and the second rule is set to $75 for 7, when both are true, the fee will be set to $75.
Related to this, if you have rules which both increase/decrease the fee and at least one rule which sets the fee to a certain value, if the rule which sets the value is triggered, the increases and decreases will not be applied.