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.

Updates, Features, and Upgrades

Subscription Support for Payeezy Payment Systems

1Risk Waiver Integration

Aspenware Commerce Consolidated Waivers

Square for Payment Plans

Promotion Usage Details for Time-Date Specific Products (Golf)

Login Help Setting

New Validated Prompt Setting

New Sign Waiver During Personalization Setting

Resolved Issues

• Subscription Payment Grouping

  • Previously, if a subscription payment was grouped, but one of the grouped members had their payment date get 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 seeing orders getting created and customers getting charged 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, discount functionality only worked if product attributes were identical. Now, customers can apply promotes 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.

• Rare Payment Plan Failures

  • Previously, select 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 attribute.

• 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, is a customer has an Authentication Profile in RTP but is also setup to be a member of a General Business, they are unable to logi

• Golf

  • Performance issues have been 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.

User Interface Updates

Hero images, logos, headers, and footers have been updated according to customer requests.

Things to Look Forward to

Aspenware Arrival

Improved Performance for Flash Sales and Limited Inventory

Capacity Limits

Queuing Integration

1Risk Support for Siriusware

Features

Subscription Support for Payeezy Payments

Resorts using the Aspenware Subscriptions plug-in can now utilize Payeezy as a payment provider. Previously, only Square payments could be used for subscriptions credit payments, for either the original purchase of the subscription enrollment, or for subsequent monthly payment amounts for the subscriber. Now, resorts can offer subscriptions using Payeezy as well. As with all subscription functionality, this new feature is available to RTP|ONE resorts using Aspenware Commerce.

1Risk Waiver Integration for RTP Customers

Aspenware now integrates with 1Risk Management Software for RTP. As with Aspenware Waivers, customers can sign 1Risk waivers during the personalization step in checkout. Signed waivers are updated and stored in 1Risk and verification is input/updated in RTP. 1Risk waiver capability is configurable and allows resorts to use both 1Risk and Aspenware waivers simultaneously. For more information see the 1Risk Release Guide. Note: 1Risk Waivers do not work with Aspenware Consolidated Waivers.

Square for Payment Plans

In addition to Payeezy, Auth.net, 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)

Aspenware has enhanced the usage details for time and date specific products. Now, when a customer has applied a promotion to any (or multiple) item(s) in the cart, they usage table will reflect how many orders have claimed the promotion.

Settings

Login Help Setting

Resorts can now use a setting (true/false) to display or hide the "login help" link underneath the username on the sign-in page. This link is designed to show images of tickets/passes/media, helping users log in using their pass number. The default value is false (not hidden).

New Validated Prompt Setting

Previously, if a product prompt was configured so that it did not validate at assignment, it became a required validation prompt. Once a value for that prompt had been used (validated), that value could not be used again. Now, administrators can use the settings panel to mark whether prompts can be used multiple times.

Sign Waiver During Personalization Step at Checkout Setting

Now Aspenware Commerce allows waivers to be signed in RTP during the personalization setp and prior to completing checkout. This allows for immediate waiver capture. To enable this setting (WaiverSettings.SignWaiverDuringCheckOut) see the configuration guidelines.

Validate Signature Setting

Aspenware Commerce also now allows customers to skip signing waivers that have already been sigend and are already valid. This setting can be turned off and on in Aspenware Commerce Waivers administration panel by setting the “ValidateSignature” to true/false for a given waiver. For more information see the the configuration guidelines.