Last updated: July 223, 2019
inLeague
...
Architecture Update (Summer 2019) Announcement
As part of a years-long architectural update, inLeague is launching a short-term public beta for some production league systems to facilitate the replacement of the the development team at inLeague replaced the back-end software "engine" that runs the inLeague application. Some of the background for this change is described in more detail in our Founder's Blog (item #3); the short explanation is that inLeague is retiring the Adobe server software that has been in place since 2003 in favor of a more modern, open-source alternative that runs much of the same code. This is the largest single change to inLeague's technology stack in the company's history and requires required small-to-medium updates to nearly every piece of code.
Does this mean that our inLeague site has two sets of data?
No – all inLeague instances are connected to live, production data and a message on the login page will indicate this. Changes made on one site will impact the other, with the exception of control panel changes (e.g. 'current season') – these changes require the inLeague application to be reset, and so will not "take" between the regular and beta instances for up to a day unless the change is made in both places.
The best way to use the beta site is to do everything you would ordinarily do on the live site but use the beta URL instead.
Who should use the beta site and where should they send comments or feedback?
Administrators, registrars, and any board members that are comfortable doing so. You do not need to be technically savvy to use the beta site. Feedback can go to our support address: support@inleague.io
Why are you making this change?
Our theme for 2019 is borrowed from part of a keynote address presented by inLeague's chief architect in April: "Modernize or die." These changes will enable inLeague's development team to build better software without destroying the development investment that our regions and our team have made over the past fifteen years. In addition to better development practices, our new software engine also enables better deployment practices, allowing us to take advantage of modern, cloud infrastructure in areas like caching and API development.
Will this change be disruptive?
inLeague (the company) has been through this process with other applications prior to undertaking the update to inLeague (the software) and the bulk of the transition is already complete. Nevertheless, because these changes touch every corner of the software, we would rather have our power users kick the tires for a few weeks. Based on our previous experience, the bulk of the issues that users will encounter can be fixed rapidly, but as with any major system change, there will be some interruptions. Our goal is to get these out of the way during July of 2019 prior to the start of the Fall 2019 season.
What should beta users look out for?
Unexpected behavior. Crashes will be reported to inLeague automatically. Be on the lookout for functions that don't crash but don't perform in the manner you would expect: for instance, if you make a change to a user, a player, a game, or a roster assignment, and some or all of the changes do not persist.
How do I access the beta site?
...
Why are you making this change?
Our theme for 2019 is borrowed from part of a keynote address presented by inLeague's chief architect in April: "Modernize or die." These changes will enable inLeague's development team to build better software without destroying the development investment that our regions and our team have made over the past fifteen years. In addition to better development practices, our new software engine also enables better deployment practices, allowing us to take advantage of modern, cloud infrastructure in areas like caching and API development.
Will this change be disruptive?
inLeague (the company) has been through this process with other applications prior to undertaking the update to inLeague (the software) and the bulk of the transition is already complete. inLeague conducted a public beta test for most of July 2019 in parallel with the legacy architecture. Nevertheless, because these changes touch every corner of the software, some disruption is likely. Based on our previous experience, the bulk of the issues that users will encounter can be fixed rapidly.
What should users look out for?
Unexpected behavior. Crashes will be reported to inLeague automatically. Be on the lookout for functions that don't crash but don't perform in the manner you would expect: for instance, if you make a change to a user, a player, a game, or a roster assignment, and some or all of the changes do not persist.
What if my league isn't listed?
The initial beta rollout does not include every league. Since the beta system is run in parallel with the live, legacy site, we have provisioned separate hardware and need to balance the load against the desire for a larger testing pool. If you would like to participate, please contact inLeague Support.
Are there any changes in functionality between the
...
old system and the new one, or is it all "under the hood"?
There are several changes, including some new features. The new features are documented below under "Version 3.0.0".
Version 3.0.0: Summer 2019 ("Lucee") Update
...
- System Architecture: Underlying Java virtual machine language interpreter.
- Birth Certificates: Added new system for parents to upload birth certificates for league review and approval. Birth certificate files are stored securely and deleted after a (configurable) interval of days following approval.
- Report Builder Performance: While a major re-work of the report builder is underway, an incremental update has been released that greatly enhances performance on larger reports.
- Rosters / Line-Up Cards: The old HTML-to-PDF line-up cards have been retired and replaced by the official AYSO Line-up cards with edit-able form fields. They are automatically populated with the team roster, including player loans.
- Rosters / Line-Up Cards: The "traditional" (2 per page) line-up card has been updated with an edit-able PDF courtesy of Region 76. Alignment and borders have also been cleaned up.
- Rosters / Volunteer Membership: Coaches without valid AYSO Volunteer Membership will be highlighted as such on rosters. Replaced the 'work phone' field on the standard team roster format to make space for MY display.
- Volunteer Membership Queue: Removed the limit of 100 records and added a divisional view that will only show coach and referee volunteers in the selected division. Enabled sorting via datatables.
- Volunteer Membership Queue: Added league option to automatically pre-approve any user with an existing application that has already been assigned to a team as a coach or referee.
- User Custom Fields: User custom fields are now visible (for division directors) and editable (for registrars) in the user editor under the 'custom fields' tab.
- URL Shortening (/inleague): The /inleague portion of the URL is no longer necessary. If a page on your production site was underneath www.myleague.org/inleague/, you may now access it at www.myleague.org. The previous /inleague URL will continue to work as a redirect.
- URL Shortening (index): URLs containing /index.cfm/ no longer require it. For instance, if your login page was /inleague/index.cfm/Main/login then it is now accessible as /Main/login. Links containing index.cfm will continue to work.
- Event Administration: The user interface for the event list has been updated to enable the selection of several events and and a bulk email function to transfer the attendees for those events to the email manager. This feature is available on the legacy inLeague site as well.
- Housekeeping: Removed old line-up cards, divisional line-up cards (as the team roster line-up cards function allows a multi-select), and eAYSO sync functions.
...