APRIL 7, 2023
COMMIT #: c8ae1d4
UPDATES
Sales
Discount Codes: Previously, discount codes could only be setup by User, Program, or Product. This has been updated so discount codes can now also be setup by Product Category. (GWU-2488)
Discount Codes: The field “Apply After Item Count” has been added. This allows a user to set a quantity and then the discount code will apply after that item count. For example, if the item count is set to 2, everything from item 3 and on will get that discount, if eligible per the discount requirements. (GWU-2488)
Discount Codes: The ability to “Auto Apply” a discount code to a cart based on discount requirements has been added. For example, if the discount requirements are limited to a specific program and user, when that user add the program to their cart, the discount code will auto apply. (GWU-2488)
Team
Team Reporting: There was no indication of athletes being double rostered on the Rosters page. This has been updated to display a) nothing when an athlete is not double rostered b) a green checkmark when the athlete is double rostered, but approved - either by an exemption or a program setting allowing double rostering c) a red x when the athlete is double rostered, but not approved - either no exemption or a program setting that does not allow double rostering. (GWU-2336)
BUGS
Front End
Guardians & Contacts: When a user tried to create a new Guardian/Contact or edit an existing Guarding/Contact - and all fields were completed- a error message appeared saying “correct the errors below to continue.” This has been corrected so that a user may now create or edit Guardian/Contact without the error message appearing. (GWU-2535)
Program
Registration Details: When a user entered a Program Cost, left Division Cost blank and then entered $0 for Team Cost, the Team Cost was incorrectly overriding the Program Cost. This has been corrected so the Team Cost is only applied when an athlete is accepting their roster spot. (GWU-2508)
Sales
Invoices: Column headers were not in alignment with column details in the Payment Schedule And History table. This has been corrected so that all column headers and details are now in alignment in the table. (GWU-1834)
Invoices: When a user signed up for a payment plan, but then paid the invoice in full later that same day, scheduled payments were still displaying. This has been corrected so that once an invoice is paid in full, any future scheduled payments will no longer display. (GWU-2401)
Waitlist: This change corrects an issue where, when an athlete is waitlisted for a program, then removed from the waitlist and registered for the program, the maximum payment a parent/guardian can make is $0.01. After the once cent payment is complete, they are able to pay the remaining balance. Now, when a parent/guardian selects “pay in full” for the registration while accepting their roster spot, they are able to pay the full amount on the first attempt. (GWU-2507)
APRIL 3, 2023
COMMIT #: 3f43dae
FEATURES
Sales
Payment Plans: A setting has been added, per brand, to automatically run payment plans when turned on. The feature will run any day that there is a scheduled payment plan. (GWU-1599)
UPDATES
Communication
Create Message: Blue guided text has been added noting “each unique email address will only receive this message once, regardless of the number of times it may appear on this list.” (GWU-2414)
Team
Team Management: If an athlete was registered for a program and had accepted a spot on a team, but then they were removed from the program by an admin deleting the line item on the invoice, the athlete was treated as if they were double rostered. This has been updated with a filter to check if the invoice line item was deleted before auto-accepting a spot on the team. The athlete would now have an “undetermined” acceptance and an option to send a roster acceptance email would be available. (GWU-2000)
Sales
Payment Plan Status: Column added to flag any items that have been “Removed From Program” but still have a payment plan scheduled for that item. These items are not selectable on the Payment Plan Status page and will not be automatically processed. (GWU-2483)
BUGS
Communication
Data Tokens: Data Tokens - ex: [[Athlete_First_Name]] were appearing correctly in the body of a message, but not in the subject line of the message. This has been corrected so the Data Tokens work as expected in both the body and subject line of a message. (GWU-2476)
Location
Fields: Changes to existing field availability were not saving correctly. This has been corrected so that edits made to field reservations will now save as expected when clicking “Save Availability Changes.” Additionally, instances of field reservation dates incorrectly adjusting back a day when a user made a change has also been corrected. (GWU-2362)