Every member now (optionally) has a second “ScoutBucks” wallet that can be used to track funds that aren't real money (those are tracked in the original “Top-Up” wallet). The types of members (i.e., Youth, Youth & Scouters, Everyone, No one) that have this new wallet can be configured under “Account” | “Payment tracking”. E.g., a Section can offer it only to Youth, or disable the “ScoutsBuck” wallet entirely, if they want.

The ScoutBucks wallet functions identically to the original Top-Up wallet. E.g., amounts can be deposited into a member's ScoutBucks wallet, and they can then use it to pay for events. However, the ability for a member to self-pay for an event when RSVP'ing using the funds in their ScoutBucks wallet is an event-specific option (found under “Signup & Fee options”), and also has a default value (under “Account” | “Event defaults”). Some Sections may want to restrict the use of fundraising dollars to just marquis events (e.g., Jamborees), whereas other Sections might be happy if their members use their ScoutBucks in whatever way the families find helpful.

The Section also has a ScoutsBuck wallet, this means that a Section can put aside money (e.g., that was given a donation) into a separate wallet, and use it for their own NOLB program or saving up for expensive gear acquisition, without having that balance muddled with the Section's general operating funds.

Members who have a ScoutBucks wallet (and the troop) now see a second column of Money IN/OUT and Balance when viewing their statements (e.g., “Home” | “My Wallet”, or “Account” | “Wallets” | “Troop”.

There is now also better support for fundraising activities. Of note, after a fundraising event is complete, the Section can now record a fundraiser's proceeds in the event's wallet (including doing the behind-the-scenes double-entry accounting so that the Group's Treasurer can follow along).

And, there is now the ability to share a fundraiser's profit amongst some/all members. E.g., the profits can be shared across all members of the Section, or just select members (e.g., those that participated in the fundraiser). There are flexible ways to specify how much money is to be shared, so it's easy to do things like share one portion of the profits amongst all members, and another bonus share among the participants, and reserve a portion to be put towards the Section's “new canoe fund”.

Note that the Profit (or loss) sharing isn't just for fundraisers. If an event encounters some unanticipated expenses and you want to recoup the losses from all the participants, then the same sharing mechanism can be used to distribute the loss across the selected members' wallets. When sharing a profit (or loss), you are able to specify which of the members' wallets are impacted. Profit/Loss Shares can be edited, so if you realize that you overlooked one participant, or if an after-the-fact donation towards your fundraiser came in, you can go back and re-jig the numbers and all impacted members' wallets will be appropriately credited.

Now that there is a fully-supported ScoutBucks wallet, and built-in support for tracking fundraisers, the old “Targeted Fundraising” pseudo-badge has been deprecated, and any credit towards that badge has been migrated to a ScoutBucks balance.

• Can now claim/reimburse expenses from an event wallet (e.g., useful for events with $0 fees, but which have expenses such as craft supplies)
• Upcoming meetings with fees but no signup now have a “Manage Payments” option
• Reworded “Add Entry” transaction types to be more task-oriented
• Only show the options for member debt write-off and/or overpayment claim if they apply to one or both of the members wallets
• Improved presentation of event wallet statement for transactions involving deleted members
• Added “ScoutsTracker Skills” topics for all the new functionality
• Memory of members' preferred ledgers for deposits/withdrawals/reimbursements are no longer scrubbed during a “reload from server”
• Bulk payment of members' outstanding fees using “We've already received the money” now supports “Via what Method” option

• Deleting a transaction didn't clear the sync of other other affected ledgers (if any)
• Go to “Account” | “Wallets” | “Event Wallets” | <event>, then delete payments and delete the event, and go back, and the deleted event still shows in the list of wallets
• Fixed incorrect label in member wallet statement when itemizing member profit claim by troop
• Editing a member transaction for an event correctly updates the DB, but on the next reload, the old cached amount was re-used (until the next reload, or the next edit to the event)
• SS-6875: In the payment history of Manage Signups, show fees as $0 for any members who are ineligible, or who signed up NO, or if the event is cancelled
• Bad HTML encoding when describing wallet sharers in confirmation dialog

• SS-6791: Blank space was being added to Personal Journey Cards for training “skills”
• SS-6794: Incorrect text displayed in “Back” link on “My Path” report
• SS-6815: HTML entity code being shown in email subject (date range) if the event is more than a year in the future
• SS-6815: HTML entity code being shown in email subject (date range) if the event is more than a year in the future
• SS-6805: Zero per-member costs shouldn't be shown in the quick event overview, in some situations (emails, newsfeed post view on /hello)
• SS-6867: If you pick a joined Scouting Date in the future (e.g., next month), it could say that they'd joined Scouting 11 months ago
• SS-6825: Navigating to old link of “https://scoutstracker.ca/sc/main” wasn't redirecting to “https://scoutstracker.ca/sc/info”
• SS-6889: When pasting content from 3rd-party apps into event descriptions, Scouter-only notes, etc., strip out CSS that could muck up subsequently display
• “Manage Signups” didn't have a bottom border for consent and signup notes cells

There have been a number of requests to improve the ability to find which requirements the Youth could focus on to advance through the program (e.g., earn their next stage).

Previously, the best you could do was use the “Reports” | “Completion” report, that shows all the requirements for all the Youth, for just a single badge. But the feedback was that this required too much “hunting” through multiple stages in multiple OAS, looking for good opportunities. And, you couldn't easily apply what you'd just discovered to your Program planning.

A more useful workflow would be to allow you to work with the Leadership team to easily identify those requirements that would offer either the “biggest bang for the buck” (benefiting the most Youth) or “low-hanging fruit” (i.e., the last couple of remaining requirements that will complete a badge for a number of Youth), and then with a couple of clicks add those requirements to one of your upcoming events.

To accomplish this goal, there is now a new “Program progression planning” report that can show a selectable number of multiple badges, and reduces the report to just the requirements that have NOT been universally completed, and then lets you select a number of the displayed requirements and add them as Related Requirements to an upcoming event.

The report focuses on what the youth can/should be working on. E.g., if every Youth in your Section has Camping Skills #1.4, there's no point in including that requirement in a planning report. Similarly, if any badge has been entirely completed/awarded by the whole Section, then it is also omitted from the report.

The set of analyzed badges can be automatically fine-tuned to suit the needs of your youth. In particular, there's an “auto pick” option that not only includes the fundamental Personal Progression and Top Section awards, but also reviews the Youths' current OAS progress in order to pick just enough Stages in each OAS to allow all Youth in your Section to advance. E.g., if your Pack has a couple of senior Cubs who have completed Camping Skills 3, then the set of selected Camping Skills to display will include Stages 1-4, so everyone has something to work on in that OAS; whereas if the maximum completed Paddling Skill is just Stage 1, then the set of selected Padding Skills will include Stages 1-2. Or, if none of the Cubs have completed any Emergency Skills, then the set of selected Emergency Skills will be just Stage 1.

Alternatively, you can also preselect just the OAS, in a particular range of Stages. E.g., you can select all OAS stages 1-2, or 1-3, or 1-4 with a single click.

And, of course, you can manually (de)select specific badges, too.

If a displayed requirement is already included in the Related Requirements for an upcoming event, then it is annotated with a scheduled icon, and hovering your cursor over the icon will explain for which event(s) the requirement is included as a Related Requirement.

There is a requirement filter input field, so you can search through the displayed requirements to show only those that match your text (e.g., find all requirements that mention “menu plan”).

The report also supports member filtering, by Patrol or Adventure Team, so you can reduce the number of youth down to just a particular subset. This allows you to work with just a single Patrol to help them find what they want to build into their Program.

The new “Program progression planning” report shows a synopsis of the requirement text in the first column of each row, so you can easily see what the requirement involves (e.g., you can see explicitly that Camping Skills #3.9 is “I can get a weather forecast”, so you don't need to look it up).

And finally, the report allows you to select one or more of the listed requirements, and then click “Add to Event” in the toolbar to include the selected requirements in one of your upcoming event's Related Requirements.

Anywhere that supports searching or text-based filtering is now improved, so as to feel much more similar to common search engines. In particular, multiple search terms are possible.

For example, previously, if you had searched for 'day pack' it would have matched text that contained exactly that string (i.e., the 'day' and 'pack' would have had to be adjacent in the text, in that order). However, now, it'll match any text that contains BOTH the words 'day' AND 'pack' (in any order). However, if you actually do want to an exact multi-word search like before, you can put some of the search terms in quotation marks. E.g., searching for '“day pack” hike' will find text that contains BOTH the two-word term 'day pack' AND the one-word term 'hike' (in any order).

Additionally, searches now use word boundaries, so searching for 'age' will no longer match 'bandage'.

As before, searching for a plural term (e.g., 'canoes') will also match the singular (e.g., 'canoe')

• SS-6907: Added “select all/none” to multi-event owing/signup reports
• MyPath report now includes reqs to complete next stage of each OAS
• More items under “Reports” now contain explanatory text, items reorder, some lesser-value reports removed
• FROZEN: Improved frozen table scrolling
• Improvement in indenting when radio button subtext wraps multiple lines

• SS-6908: Wrong language setting in the info website
• SS-6687: Make sure that any subscription attachments in duplicated events have .issubscription cleared
• SS-6929: Fixed some non-localized uses of “Fundraising”
• SS-6917: Signup summary was not listing default ineligible members who were made eligible for just this event
• SS-6917: “Manage Signups” for Scouter-only events wasn't listing default inelegible members
• Minor vertical alignment issue with radios in event push dialog
• “Home” | “Pond Map” | “Print” is showing the page title, which is causing the map to overflow

• PERFORMANCE: Remember scorecardings (faster initial viewing of big reports), faster switching between members, slightly faster initial connection
• PAYMENT: Eliminated “netting”. Fee payments and expenses are now shown in different tables / columns so that a member can have an outstanding balance on either/both fees and expenses
• PAYMENT: Grouped new wallet entries by general activity
• PAYMENT: Allow expenses to be immediately reimbursed (creates two transactions)
• PAYMENT: Grouped new wallet entry types by general activity
• Better sorting of Collaboration accounts
• SS-6942: Improved the “this is a subscription” message when editing a subscriber of a master/overview event that is also defined in your section
• SS-6959: Add “.ics” to the webcal URL's to prevent Outlook from raising a red-herring error message
• BADGE IMPORT: Spreadsheet reader now include “requirements” column (for <details>) and “synopsis” column (max 40 chars)
• Many reports have style changes for consistency
• SS-6920: “Dues” vs “Special Dues” nomenclature should only apply if you collect dues. Otherwise just use “Fees”
• SS-6956: New option to select only all events that have already happened or are past their signup deadline
• Manage Signup's “revert to unknown” doesn't do anything if the member has already paid (and is implicitly signed up). Offer to change signup to NO rather than UNKNOWN
• Support for WB2 scouter training (just needs final database update)
• CLEANUP: Resolved HTML validation issues

• SS-6937: Events missing from embedded calendar
• SS-6937: Some long-established collaboration accounts were being displayed with an their original name at the time of collaboration, which could be different than the current name
• SS-6948: Failed login message was making reference to “MONIKER”, rather than your Section level (e.g., “Pack”)
• SS-6988: Filtering emails was choking on embedded images
• TRAINING: SS-6943: Topic hpocp799 wasn't being triggered
• SS-6956: New option to show all members in “Multi-event owing” report. Total row shows rollup of values in each column.
• Badly-encoded image in YLT requirements

• Better support/logging when invalid date formats are used
• Changing the preferred start of the week (Sunday or Monday) also impacts date pickers, immediately
• SS-7019: Signup & Fee options “Back” button was taking you back to the signup page, even when there wasn't a compelling reason to do so
• FROZEN: Better sizing of unfrozen tables
• FROZEN: Better print styling
• PAYMENT: Fixed some instances of text “Expense paid” that should be “Expense claim”
• PAYMENT: Offer a new “Convert to Fee Refund” if there were fee refunds that were inappropriately recorded as expense reimbursements
• ADMIN: tidyup lookupMember to put member# and status and displayname in the “other members” section
• SS-7033: When an Other Participant is converted to a Scouter, any signups/payments made for the Other Participant should be switch to the Scouter
• Historic events should show inactive members in Manage Attendance if they were active at the time of the event
• Upcoming events don't need to be included in “My Events” for inactive members, nor should “Show upcoming” toggle switch
• COMMITTEE: SS-7035: In a Committee/National account, limit “Access Granted by Logins” to *just* the Committee Members
• QUALS: SS-6637: Create min quals of 1xSFA and 1xWFA, and it turns out that a single person with WFA or higher will satisfy *both*. Now block this in the UI.

• HELLO, EMBED: SS-6995, SS-6996, SS-6999: Broke the display of servlet.js generated calendars
• SS-7003 (and others!): Pickable dates were always defaulting to today's date
• PAYMENT: SS-6694: Rounding errors meant that zero-balance wallets could be listed in the list of member wallets
• SS-7025: Changing the start of the week (Sunday or Monday) had no effect
• SS-7029: Setting “Show signup notes” to YES wasn't actually showing the notes
• SS-6998: After an initial Sync, viewing the Emergency List of a Master/Overview event was showing the details for all members, not just those that signed up
• PAYMENT: From “Manage Attendance”, edit an entry, and click “Delete”. Then the payment/expense history shows a $0 entry, rather than hiding it.

• Added a Total line to “Account” | “Member wallets”
• SS-7060: Attachments are now sorted by name, then insertion timestamp
• PAYMENT: Use members' real names (not troop nicknames) when determining what to call a shared wallet
• PAYMENT, RSVP: SS-7062: Rapid double-clicking on the RSVP landing page's Update button could record a second (over)payment
• QUALS: Better sorting of custom first aid quals in event's min safety quals picker
• EMAIL: SS-6690: Better display of fees when Scouters don't have to pay anything
• COMMITTEE: The calendar swatches of subscription events in other sections that have scouter-only visibility now show a lock icon
• Make #inventory-source-picker use “.selection.radio”
• Got rid of most “fsets”

• QUALS: Red-herring message box upon updating signups if user had WFA selected as their required first aid level
• QUALS: SS-6637: Further fine-tuning to handle historic situations where an event had two or more quals in the same category (e.g., SFA and WFA)
• PRINTING: “Home” | “The Pond Map” | “Print” is showing borders in the white-page
• PAYMENT: Pre-initialized value in member-event-payment was showing as “NaN” if no fees were defined
• PAYMENT: buildViewEvent wasn't always getting called when you add an entry from an event's wallet
• SS-7076: Toggling “Account” | “Program preferences” | “Only working on the Canadian Path” had no effect
• COMMITTEE, INVENTORY: SS-7076: Enabling “Share common badges” wasn't working
• Fixed an issue with loading previous scorecarding that was preventing the badge status display from changing