| Estimated Release Date |
4th September 2024 |
| Estimated Release Time |
Day release |
| Expected Downtime |
No expected downtime |
Summary
During this development cycle, the teams have continued the work to progress Activities V2 (Templates & Schedules), along with a correction to staff access relating to activity schedules, release of a new improved Direct Debit Collection Datasource and several small improvements.
Key Defect - Already Released
Staff Access Correction for Activities Module
Reported case where staff who don't have access to Activity Templates but should have access to Activity Schedules as part of their Flow account, were still able to access Activity Templates and make amendments. This has now been resolved and staff users should now have the correct access for the main Activities module as set out in their allocated access role.
Future Start Date Memberships & Activity Discounts
A further improvement has been made concerning the booking behaviour for memberships with a future start date. There were continued reported cases for some customers that whilst their membership had a future start date, they were not receiving the relevant discounts eligible as part of their membership for activities booked for a date on/after the membership was due to be active. We believe to have identified the cause of these cases as being related to pricing adjustments that had a home centre override applied.
Worth noting from the internal testing of this improvement, that there is a backend pricing option cache process that can take up to 15 minutes to run and as a result, there can be cases of a short delay in created/updated pricing to appear correctly. Whilst in most cases the process takes less than 15 minutes, it is worth factoring this in when testing/triaging any pricing option set-up or queries.
Customer Searching - Email Addresses
A fix has been released for an issue that was occurring when searching for a customer account with an email address that contained an underscore.
Enhancement - Already Released
New Direct Debit Collection Datasource - Recurring Membership Collections
Following feedback on the behaviour of the current DirectDebitCollection datasource and our own internal review, we have now released a new version titled Recurring Membership Collections. The previous datasource had behaviour that was causing clients difficulty with the reconciliation of DD income and also when doing any yearly reconciliation/reviewing data for financial audits. This included:
- When a DD mandate was cancelled, any previously successful DD collections for a member were removed from the Datasource.
- When a DD collection had been paid/part with credit this value was not represented correctly in the datasource and showed the normal DD collection fee regardless of the amount actually collected.
- When one DD mandate was paying for more than one membership DD collection, the full total value of memberships was attributed to multiple entries in the data. For example Member A has a DD mandate paying for their membership at £30 and also paying for Member B's membership at £25. Both Member A & B would each have an entry in the report for their months DD collection as £55, making it appear the total value collected for that mandate was £110. The correct behaviour should be Member A is represented with £30 in one entry for their collection and Member B is represented with in one entry for their collection at £25, making the total for that mandate the correct £55.
- In the case where there was a recovery/reconciliation fee involved with a DD collection (for example a customer coming off a freeze part way through their DD payment period), the value for the collection would not always take into account the recovery/reconciliation fee value and would display an incorrect value for the collection.
The new Recurring Membership Collections datasource now addresses the previous behaviours mentioned and now maintains any records of the collected DD's regardless of the current status of the mandates, handles credit and recovery/reconciliation fees and splits out the collection fees for when one mandate pays for multiple memberships.
We will next be working on a Recurring Membership Rejections datasource so that any reconciliation can be done to handle DD rejections. We decided to split these out into separate datasources due to the complex nature of the query that supplies the new datasource to ensure the appropriate refresh rates.
Enhancement to Membership Cancellations
During the work for cancelling a membership in any status & cancelling a membership immediately (released in 1.59), the team had a follow-up change to complete as part of this project for when a membership cancellation is processed and there is an active or pending freeze involved. The change we have released will now:
- Apply a freeze rejection reason of Membership Cancelled
- Suppress the freeze rejected notification to a customer
- Cancel any freeze related fees
Please note this change will apply to any type of membership cancellation, be it immediately or in the future.