This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
release_19.0 [2023/11/16 17:07] admin [Release 18.3 - Key Features] |
release_19.0 [2024/05/13 18:23] (current) admin [Display Format] |
||
---|---|---|---|
Line 2: | Line 2: | ||
====== Release 19.0 - Key Features ====== | ====== Release 19.0 - Key Features ====== | ||
+ | ===== ScoutsTracker Skills (Training) ===== | ||
+ | ScoutsTracker now includes embedded self-training. | ||
+ | |||
+ | ==== Design Intent ==== | ||
+ | The purpose of adding training is to use gamification to introduce users to different areas of ScoutsTracker that they might not otherwise think to visit. | ||
+ | |||
+ | The training is modeled after the OAS requirements, | ||
+ | |||
+ | There are then some instructions that explain how to complete the training skill. | ||
+ | * For the "I know..." | ||
+ | * But most other training skills, the training skill is marked as complete when the user goes to particular page, or flips a switch, or presses a button | ||
+ | |||
+ | Consequently, | ||
+ | |||
+ | However, if a user is ever has questions about how to do something, the training does serve as a knowledge base... e.g., they can search the training for " | ||
+ | |||
+ | Training skills can be tackled in any order, i.e., although there are "next steps", | ||
+ | |||
+ | ==== Display Format ==== | ||
+ | The training is presented in two formats: | ||
+ | * A list. By default, the list shows the " | ||
+ | * A tree. This shows all the skills that the user can earn, displayed in a radial tree. Hovering the mouse over any node in the tree will show a tooltip with the basic competency, and clicking on the node will actually drilled down to the detailed view of the skill. | ||
+ | |||
+ | ==== Rewards ==== | ||
+ | As a user completes more and more training skills, they' | ||
+ | |||
+ | There' | ||
+ | |||
+ | ===== Miscellaneous Enhancements ===== | ||
+ | * Minor tweaks to the display of account creation page (hiding Area, for example) | ||
+ | * SS-5555: Tweaks to visibility of items under " | ||
+ | * SS-5679: Inactive members with no entry/exit dates and no event participation (ever!) are now culled from the Attendance report | ||
+ | * SS-5615: More consistent used of " | ||
+ | * IMPORT: Strip underscores out of column names to compensate for Excel quirk | ||
+ | * IMPORT: Update the instructions to include just 2023 members or 2023+2024 members | ||
+ | * COMMITTEE: Better presentation of custom names when creating section accounts | ||
+ | * Improved the display of Scouters with the " | ||
+ | * When other participants who are default ineligible to attend events are marked as attending an event that has signup disabled, the divider has an annoying habit of constantly collapsing | ||
+ | * SS-5645: Support colon-less event start/end times like " | ||
+ | |||
+ | ===== Bug Fixes ===== | ||
+ | * SS-5473: Pre-existing unverified email addresses could be used as delegate emails, but then the user got a cryptic message about being unable to verified " | ||
+ | * SS-5474: Could not attach documents to non-Scouting events | ||
+ | * SS-5474: Risk Management controls were visible for virtual events, leading to confusion | ||
+ | * SS-5527: Can't give credit on a Personal Event | ||
+ | * Remove hard-coded reference to edition name | ||
+ | * SS-5568: Possible use of old signup deadline logic? | ||
+ | * WIKI: SS-5595: Update the Member Type documentionation to align with the code | ||
+ | * COMMITTEE: SS-5594: Couldn' | ||
+ | * SS-5684: Active members with exit dates should be in the attendance report, because they are actually active | ||
+ | * Recover from the "OMG all my data disappeared bug" by always setting the sync timestamp to zero if no records exist | ||
+ | * SIGNUP: SS-5628: Couple of annoyances with members who are default ineligible to attend events | ||
+ | * SIGNUP: SS-5609: Couldn' | ||
+ | * SS-5636: Math error meant " | ||
+ | * SS-5643: Saving a login was clearing the reply-to address | ||
+ | * SS-5650: Better job of handling of malformed MessageTemplate records | ||
+ | * RSVP: SS-5658: Need to do a check to make sure that a corrupted email that contains *|HTML: | ||
+ | * RSVP: SS-5664: Signup was ending a few hours too soon | ||
+ | * SS-5661: Printing signup/ | ||
+ | * SS-5662: Other Participants weren' | ||
+ | * ADMIN: When connecting to a specific account after attaching a support login, you were asked to sign in, every time | ||
+ | * When other participants who are default ineligible to attend events are marked as attending an event that has signup disabled and a non-zero event fee for other participants, | ||
+ | * COMMITTEE: SS-5682: When creating a new committee account, the preview was incorrectly saying it would display as "- Cubs" | ||
+ | * HELLO: SS-5686: News Feed should only ever contain posts with " | ||
+ | * SS-5688: The isEmailAddressVerified check was being done on the fromEmail address rather than the senderEmailAddress (which takes into account delegates) | ||
+ | * Removed a red-herring " | ||
+ | |||
+ | ===== Patch (2023-11-23) ===== | ||
+ | ==== Miscellaneous Enhancements ==== | ||
+ | * SS-5705: Use access annotations for logins, even if a display name is provided | ||
+ | * SS-5705: Be smarter about culling redundant usage of last names in logins' | ||
+ | * SS-5501: Members with "Can see private" | ||
+ | * Nicer display of "Use a different login" | ||
+ | * Message telling user's they don't have perm-superuser or perm-private now lets them contact the account admins, easily | ||
+ | * Improvements to the "Email Addresses & Communication" | ||
+ | * TRAINING: Improved creole formatting of instructions | ||
+ | * TRAINING: SS-5726: Topic wjoiq937 is automatically marked as complete if you're a parent/ | ||
+ | |||
+ | ==== Bug Fixes ==== | ||
+ | * SS-5701: Rare conflict between event IDs could result in AAF approval notifications going to the wrong event contacts | ||
+ | * WIKI: SS-5694: Updated the Import Format documentation | ||
+ | * SS-5706: Tweaked wording of the creating a new member dialog, so that it wasn't making assumptions about the person being imported | ||
+ | * SS-5684: Multi-section Master/ | ||
+ | * Clicking " | ||
+ | * Members with perm-private but not perm-email couldn' | ||
+ | * Two 'Send Email'/' | ||
+ | * SS-5673: Custom quals with an equivalent (e.g., RFA grants WFA) that didn't a category were being ignored | ||
+ | * SS-5700: Duplicate quals were being shown | ||
+ | |||
+ | |||
+ | ===== Patch (2023-11-29) ===== | ||
+ | ==== Miscellaneous Enhancements ==== | ||
+ | * Improved change detection when editing away from a partially-editing AAF | ||
+ | * If a member' | ||
+ | * SS-5560: show opted-out notifications people in lists of outing contacts, signup notifications, | ||
+ | * TRAINING: Add training score to ADMIN: | ||
+ | * Removing "is a two-deep contact person" | ||
+ | * Prevent being an account contact if you've opted out of receiving notifications | ||
+ | * Don't complete any training skills unless signed in | ||
+ | * NEWSFEED: Don't bother trying to display the news feed until initialization is complete | ||
+ | * ADMIN: Welcome Message to new admins should include link for initial sign in | ||
+ | * COLONY: SS-5740: Add Progression (brown/ | ||
+ | * ADMIN: Added a cullBlacklist method | ||
+ | ==== Bug Fixes ==== | ||
+ | * SS-5732: Signup notifications could go to multiple sections if they both had events with the same ID | ||
+ | * " | ||
+ | * SS-5734: The toReversed array function wasn't supported by most browsers until recently, so added a wrapper to implement it in a safe way | ||
+ | * SS-5744: SQL error in signup notification recipients generation | ||
+ | * Going to Signup/ | ||
+ | |||
+ | ===== Patch (2023-12-08) ===== | ||
+ | ==== ScoutsTracker " | ||
+ | The ScoutsTracker " | ||
+ | |||
+ | Rather than bundling requirements into rigid pre-defined Stages, this Continuous Learning approach allows you to focus on and build up expertise in specific areas, as befits your needs and your interests. In other words, it lets you chart your own path through the " | ||
+ | |||
+ | While the badge requirements shown below are all chained together into sequences, that's mostly just a way to suggest logical next steps for you to consider. There' | ||
+ | ==== Miscellaneous Enhancements ==== | ||
+ | * SS-5578: Add " | ||
+ | * SS-5523: If an event is Personal, and it’s in a previous Scouting year, and there are no attendees, then put up a message saying that you need to add at least one attendee, rather than saving | ||
+ | * Add prompt when cancelling a subscription to a multi-section event that is hosted by your account... e.g., "do you want to cancel for all sections, or just your own?" | ||
+ | * COMMITTEE: Can now "Add Recipients" | ||
+ | * SS-5760: Parents/ | ||
+ | * SS-5760: Logins that accessed absolutely *no* progression records in that section' | ||
+ | |||
+ | ==== Bug Fixes ==== | ||
+ | * " | ||
+ | * Editing a cancelled event uncancels it | ||
+ | * MULTIACCOUNT: | ||
+ | * MULTIACCOUNT: | ||
+ | * Picking PAB as Related Requirement shows really wonky column alignment for the requirements | ||
+ | * SS-5761: Clicking next/prev while picking related requirements incorrectly changes some wrong headers | ||
+ | * SS-5766: Gallery headers for Other Participants are wrong | ||
+ | * TRAINING: SS-5764: Tweaked wording of topic rtuqm801 | ||