|
|
|
This document outlines the most significant changes in the transition from the inLeague Legacy Platform to the 20th Anniversary Edition, launched in the Spring of 2022 for Fall 2022 registration.
|
|
|
|
|
|
|
|
The inLeague legacy platform will continue to operate until all previous functions have migrated off of it. We have prioritized the functions used by the largest groups of people (player and volunteer registration); check the Development Roadmap for more information on which functions will be migrated in the near future. We anticipate that the entire process will take several years, but league administrators should be the only users regularly having to use both paltforms.
|
|
|
|
|
|
|
|
1. [Player Registration Changes](#player-registration-changes)
|
|
|
|
2. [Volunteer Registration Changes](#volunteer-registration-changes)
|
|
|
|
|
|
|
|
## Player Registration Changes
|
|
|
|
|
|
|
|
The most significant difference between the legacy inLeague platform and the 20th Anniversary Edition is the model for Player Registration. We considered how inLeague had been used for over a decade and saw that the biggest growth (and the biggest pain point) was managing registration flow for multiple programs (also called competitions) under one umbrella, e.g. an intramural program vs. camps & clinics, or core vs. extra, or travel vs. tournament.
|
|
|
|
|
|
|
|
Before 2022, every season had "player registration" and a player was either registered or not. The 'sorting hat' -- placement of players into specific programs -- happened after registration, usually based on custom content from the registration form. This relied on a lot of custom fields in advance of player registration and the use of eligibility rules to manage team assignments.
|
|
|
|
|
|
|
|
Beginning with Fall 2022, **player registration is always for a specific program**:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Per-Season Settings Migrating to per-Competition, per-Season Settings
|
|
|
|
|
|
|
|
Consequently, several settings that were formerly **per-season** are now **per-season, per program** and some settings that were formerly **per-season, per-division** are now **per-season, per-program, per-division**.
|
|
|
|
|
|
|
|
#### Registration Dates, Season Starts, and Default Holdbacks
|
|
|
|
|
|
|
|
Different programs may open and close registration on different dates and automatically waitlist on different dates. The "season" for each program may begin on a different date and last for a different number of weeks.
|
|
|
|
|
|
|
|
The default refund holdback now varies by competition.
|
|
|
|
|
|
|
|
#### Eligibility Rules and Volunteer Requirements
|
|
|
|
|
|
|
|
Per-family and per-player eligibility rules may be applied differently (or not at all) for each program.
|
|
|
|
|
|
|
|
Volunteer requirements may also differ by program.
|
|
|
|
|
|
|
|
#### Division Assignments and Caps
|
|
|
|
|
|
|
|
Division caps and division placement are now handled on a per-program, per-season basis:
|
|
|
|
|
|
|
|
* Players registered for one program will not count towards caps in another (e.g. Travel players will not count for Core caps; this was sometimes the case previously, but only through special configuration on inLeague's end)
|
|
|
|
* Divisions may be opened or closed for one program but not another: Core can have U8, U9, and U10 while Travel might only have U8 and U110.
|
|
|
|
|
|
|
|
#### VIP Programs
|
|
|
|
|
|
|
|
VIP programs used to be managed through a question on the registration form that would place players into a VIP division. Leagues with VIP programs now have a VIP competition that has its own registration settings. There is a still a VIP division that may be used for the VIP competition if desired.
|
|
|
|
|
|
|
|
### Registration Eligibility Mechanisms
|
|
|
|
|
|
|
|
By default, all players are eligible to register for all programs. This is the **default eligibility** setting under the new Competition Administration page. If this setting is changed to **false**, then the settings under the **Competition Eligibility (Rules)** and **Competition Eligibility (Player)** tabs apply:
|
|
|
|
|
|
|
|
* **Existing Player Eligibility**: Specific players who already exist in the system may be invited to register by searching for their name and selecting their record.
|
|
|
|
* **Name/DOB Eligibility**: Instead of linking to a specific player record, you may supply a player's last name and date of birth. This allows you to invite players who may not yet have records in the system, or to bypass having to search for each player.
|
|
|
|
* **Eligibility Rules**: The previous mechanism restricting player registration to only those players who satisfy the result set of an eligibility rule still functions, but should only be necessary in rare cases.
|
|
|
|
|
|
|
|
### E-Signatures
|
|
|
|
|
|
|
|
Previously, families were re-directed to AYSO's e-signature provider (Yozons) partway through registration, and then returned to inLeague. Yozons has been retired and replaced with AYSO "Electronic Legal Agreements" (ELAs) which originate from the Affinity Association Management Platform but are implemented entirely by inLeague. This means that e-signatures now occur within the context of the regular registration flow and are not routed outside of inLeague at any time.
|
|
|
|
|
|
|
|
The ELA signature data is transmitted to AYSO after the registration is paid and active (not waitlisted).
|
|
|
|
|
|
|
|
## Volunteer Registration Changes
|
|
|
|
|
|
|
|
While the underlying model for volunteer registration hasn't changed, the workflow and user interface has been streamlined and optimized:
|
|
|
|
|
|
|
|
* During new account creation, we emphasize the importance of using your **full, legal name**.
|
|
|
|
* We no longer collect date of birth on account creation.
|
|
|
|
* When a user volunteers for the very first time (and only for the very first time), they are prompted to confirm their full name and to enter their date of birth.
|
|
|
|
* The 'prior disclosures' page where we previously collected the last 4 digits of the volunteer's SSN has been retired; there are no more disclosures and we do not collect any part of the SSN
|
|
|
|
* The Yozons e-signature page has been retired and replaced with AYSO Electronic Legal Agreements (ELAs) similar to those used for player registration.
|
|
|
|
* Background checks are no longer tied to membership year, but last for 455 calendar days from the date they are submitted to Sterling.
|
|
|
|
|
|
|
|
The regional approval step prior to background checks getting sent to Sterling has not changed; volunteers are placed in a queue for regional review and are only sent to Sterling after the region selects 'Approve' for or 'Always Approve.' |
|
|
\ No newline at end of file |
