1.67 Release Notes

Summary

The primary focus for this development cycle has been working on Activities V2 for any key defects identified during the rollout of Activities V2 for our first client, along with the next round of enhancements and an improvement to our Off-Peak Membership functionality.

We have also released enhancements to our datasource offering, an improvement to the membership cancellation reason function and the next phase of our Multi Membership project, which is the ability to associate customer accounts together in a group.

Key Defects & Enhancements (Activities V2) - Already Released

We have officially gone live with our first client for Activities V2 and during the testing and preparation for this, a number of key improvements & defects were identified and resolved, which include:

- Enhancement to the schedule search functionality, searched words now look at the template name, category & venue name (along with the schedule reference). 

- When making any significant changes to a published schedule (i.e. shortening the schedule dates) then any bookings will be cancelled and the customer notified. 

- Added the functionality for when auto-attendance is enabled (used for venues with no access control) for bookings and block booking schedules. 

- Updated the minimum Age Restriction feature to allow '0' to accommodate any age restricted activities for under 1 year old. 

- Included the functionality for extras as past of Ticketed schedules.

- Wrote a query that will allow Block Bookings in Activities V1 to be identified to support clients with transitioning existing Block Bookings over to Activities V2. We will be able to re-use this query for all client rollouts. 

- Resolved a defect identified to ensure that the booking availability setting is working correctly (i.e. where an activity should be bookable online/FOH/both)

- Released two key datasources to support Activities V2 bookings. These are the Bookings & Income datasources. 

- Resolved a key defect to ensure class waitlists work as intended.

- Ensured customers can browse by location online

- Implemented performance improvements to schedules, which corrected the behaviour for editing schedules and publishing complex schedules.

- Ensured packages could be redeemed as intended. 

- For ad-hoc activities (resource), reported that when selecting an activity to the book the default resource/location was not what a customer selects. This was caused by two different templates belonging to the same activity category and sharing same start and end times. Corrected behaviour is that each template has its own grouping. Customers will still be able to change from the default location if needed. Please note this impacted both Activities modules and has been changed in both .

Over the coming weeks, the team will continue to review any reported key defects and make progress on the remaining functionality due for the next phase of Activities V2. 

Key Defect - Already Released

Opening Times for Resources

Resolved reported cases of being unable to change the opening times for resources.

Enhancements - With the Release

Credit Datasource Improvements

Updates will be implemented to our existing Credit Datasource to support clients with identifying if a credit has been spent or expired more intuitively. These columns are:

- Credit type column (general & membership credit)

- A spent credit total against the line items

- A expired credit total against the line items

Account Linking (Groups)

This feature introduces new customer types in Flow, allowing a 'primary' customer—typically a paren, to create a 'dependent' customer associated to their account, usually a child. This functionality enhances our system's ability to manage family-based relationships, bookings, and memberships and unlocks the next phase to support management of accounts on customers behalf (e.g bookings on behalf a child account). The initial release will be via FOH/Customers module, with the next phases allowing customers to create their own group.

We are developing this feature in the form of groups. The reason for this approach is that, in the future, if a scenario arises where a person needs to be part of multiple groups (such as a nanny or carer), we will have the capability to accommodate that. Initially, our design will only allow customers accounts to be associated in one group.

Here are the definitions of the roles:

• Dependent: Child
• Admin: Parent or Nanny
• Owner: Group Owner

Note - This is an OP only admin setting that would need be enabled on a client per client basis. Please contact your Client Success Manager to enable this functionality.

Please find a demo below on this initial phase and how to:

• How to create a group
• How to link accounts

Note - The first profile will always default to group owner in the example of the demo this is Andrew

• How to view the linked accounts
• How to manage the groups
• How to delete a linked account

In addition to this feature we have built a new datasource (Customer Groups) to support the management of linked accounts/groups. As part of notifying your Client Success Manager to use this feature, this datasource will also be enabled to the available list to report from. Please see example report preview below:

Enhancement - Already Released

Membership Cancellation Reasons Improvement

We have made the reasons for membership cancellation configurable so clients can choose which ones they see.

We have also added the following additional reasons:

• Downgrade to Individual membership
• Upgrade to couple membership
• Converting to Pay as you Go
• No longer using
• Poor Service

The first two reasons were added to support the recent Multi-Use/Joint Membership functionality and the Multi Membership (purchase on behalf of another customer), and provide specific cancellation reasons where clients may want to identify these types of member movements where membership change is unavailable. 

Note - The hard-coded are defaulted and clients can go in and add the new ones above and delete any of the hard-coded ones they no longer want.

Off-Peak Memberships Enhancement

We have also made an improvement to our Off Peak/Membership Restriction functionality whereby, membership types can be configured so that they can only view and book activities for a permitted times aligned with an assigned timeband. For example, if an activity can only be booked by members (no pay as you go option), you may have a Peak and Off Peak membership, whereby the Off Peak membership can only book activities scheduled to start between the hours of 10:00 & 15:00, whilst allowing a Peak membership to book any activity for this schedule. The configuration for this happens at the booking pricing option level, which means you do not need to have separate schedules to attempt to achieve this.

Note: Currently this functionality is only available for Classes and Resources (Ad-hoc) activities at the moment, it does not work currently for Fast Tickets activities, which will be coming soon. Please speak to your Client Success Manager if you are interesting in learning more and understanding how this can be utilised in your business.