Aspenware presents Aspenware Commerce 2.10. We’re excited to announce new waiver integration with 1Risk, enhancements to subscription payment processing, among several resolved issues.
...
Subscription Payment Grouping
Previously, if a subscription payment for multiple family members was grouped, but one of the grouped member’s payment date became out of sync with others, it would cause issues with properly charging upcoming payments. This could happen when one member was frozen and was later reactivated and their payment date was changed. This issue is now resolved
Missing Reservation Table Data
Previously, some customers were charged for orders with no data in the reservation table. Now, if an order shows as 'success' in the Order Queue (RecordQueues table), the order will be in the reservation table.
Subscription Retry Days - Square
Previously, subscription retry days were not retrying on schedule (weekly), but rather retrying every day. Now, the subscription schedule is working.
Changing Emails Creating Duplicate Customer Accounts
Previously, if a customer changed their email in my account, a duplicate customer account would be created; now the email change does not create duplicates.
Promotions/Discounts
Previously, when applying a discount to multiples of the same product within a cart, discount functionality only worked if product attributes selected on the cart items were identical. Now, customers can apply promotions to identical products with differing attributes.
Fonts
Previously, fonts (such as on the PDP short descriptions) were not being set properly in some locations; now, primary and secondary fonts (including bold, light, and regular fonts) are being set correctly.
Activity Start Date
Previously, under certain conditions, the wrong activity start date (ProductDate) was being sent to RTP. Now, unused attributes have been removed (that were incorrectly ending up on cart items), correcting activity start date issues.
Guests seeing unknown accounts - Siriusware
Previously, Siriusware customers were occasionally seeing information from accounts with similar guest numbers (guest_no). Now, guest information (and linked guest information) is only shown if there is an exact match.
Payment Plan Failures
Previously, some payment plan orders would fail with the error “Error parsing Infinity value”. Aspenware has resolved the issue by adding the ability to select multiple values for the conditional attribute of a dependent attributeThis issue is resolved.
Clear Cache
Cache is now being cleared automatically when updates are made in admin.
Payment Plan Modal
Previously, the payment plan modal was not showing the correct cents value (as shown in the cart); payment items in both cart and modal should be identical and include the proper cents value.
Generate Combinations
Previously, "Generate all possible combinations" and "Generate several combinations" buttons were not working when adding attribute combinations. Now, initial settings have been re-instated and generate buttons work properly.
Customer login for General Business accounts
Previously, if a customer has an Authentication Profile in RTP but is also setup to be a member of a General Business, they are unable to login.
Golf
Performance issues have been resolved including improved tee sheet load times and smart caching.
Previously, some golfers were getting reserved as “unknown”, now, Aspenware now passes in both first and last name regardless of whether profile has yet hydrated in EZLinks.
Previously, some golfers were not getting checked in despite completing an LS Retail transaction; now all golfers completing a transaction should be updated in the tee sheet.
Previously, some tee sheets were not displaying the public 18 hole rate as the default reservation price. Now, the 18-hole public rate (the prioritized configured in EZLinks) is the default booking rate for all new reservations made in LS Retail tee sheet.
Previously, administrators could not select multiple fees under a given fee type (e.g. an afternoon rate for the 18-hole public rate). Now, admins using Aspenware tee sheets can book at the time-specific rates for a single fee type.
Previously, when a line item was deleted from in LSRetail, the partial void call would successfully delete the item from the LSRetail POS, but cart items were never removed (resulting in false check-ins). Now, when a line item is voided, the cart item is removed (and, if checking in, only the paid-for transaction item is checked in).
Previously, an invalid customer error (resulting from guest account emails that matched registered user emails) caused occasional pending golf orders; this issue has been resolved.
...
In addition to Payeezy, and Braintree, Aspenware now supports Square as a payment processor for Aspenware Payment Plans. To set up payment plans, see the configuration guidelines.
Promotion Usage Details for Time-Date Specific Products (Golf)
...