š ļø What We Fixed
Program Registration Pages
Fixed an issue that could cause a server error when opening a program registration page after moving a member.
Member Association Fields
Fixed an issue where Association Fields were not saving correctly when adding or editing a member through the new membership workflow.
Units on Invoice Report
Resolved an issue where the Units on Invoice report could display units with no associated information.
āØ What We Improved
Updated Membership Workflow
ā Updated the new membership workflow so staff now begin by selecting the Branch and Membership Type before adding unit members.
This more closely aligns the experience with the previous workflow and allows membership type-specific fields to be displayed when member information is entered.
š What's New
ā Waiver Expiration Settings
Added new expiration options for waivers, giving associations greater control over how long a signed waiver remains valid.
A waiver will now remain signed until one of the following occurs:
The waiver reaches its configured expiration date.
The signed waiver is removed.
A new version of the waiver is created.
For membership renewals, a waiver will only be considered signed if it is still valid. During program registration, members will not be prompted to sign the same waiver again until their previous signature expires.
Available expiration options include:
Never: The waiver does not expire.
Daily: Expires at the end of the day it is signed.
Monthly: Expires one month after it is signed.
90 Days: Expires 90 days after it is signed.
6 Months: Expires six months after it is signed.
Yearly: Expires one year after it is signed.
Start of Calendar Year: Expires January 1 of the year following the date it was signed.
Only on Version Change
Note: The waiver check function is version specific; If the waiver is updated to a new version, members will be prompted to sign the new version regardless of the expiration setting.
Daxko Payments EMV Devices by Branch
Added support for Daxko Payments EMV devices across multiple branch locations.
When processing an in-person payment, users will now automatically see the appropriate EMV device options based on the branch they are working in, making it easier to manage payment devices across multi-branch associations.