Published Feb. 4, 2022.

With great pleasure, Aspenware presents Aspenware Commerce 2.26. This minor release is compatible and must be deployed jointly with Aspenware Unity 3.21 and Identity 2.15.

New Features

Windcave Payment Integration

• Aspenware is excited to expand options for credit card processing to include Windcave Payment Gateway, a globally supported payment gateway that can also act as the acquiring bank in addition to the payment gateway. Windcave can serve customers operating in Australia, New Zealand, Canada, and the USA, and is fully integrated with Aspenware Commerce Payment Plans. For information on configuring this payment gateway, please see the Windcave Configuration Guide.

Enhancements

Performance Improvements in checkout

• With this, the initial release in our overall checkout refactor project, users should expect to see an improved performance during the checkout process, with a faster completion time.

Dynamic Pricing Calendar View restored - hover and background color

• On the large Dynamic Pricing calendar view, background color is now displaying when a customer hovers over a specific date. While the background colors respect the selected threshold in most cases, if inventory reaches below its threshold but has not yet reached the pricing count threshold, then inventory trumps the pricing count and the calendar background color will still change even if it has not yet hit the pricing count threshold.

Main Language (EN) of page is now declared within the HTML element.

• To achieve ADA compliance, the main language (EN) must be included in a language tag, so screen readers know how to pronounce the text on the page.

Resolved Issues

iPad users can add family members.

• Previously, iPad users running Safari v. 12.1.2.1 or earlier experienced an inability to add family members in the “Group Members” section, when completing the customer assignment, or in the My Account window. This has been resolved. Guests can successfully toggle between Affirm and Credit Card Payment, and can complete transactions using the Affirm Payment interface.

Affirm “500 errors” resolved.

• Some users of Aspenware Commerce v2.25 were experiencing a 500 error if they had selected Affirm as their payment method, and then changed their selection to Credit Card.

• Additionally, some users of Aspenware Commerce v. 2.22 or higher were experiencing a 500 error after completing the Affirm Payment flow, and were unable to complete their transactions. This error occurred if the customer had the Kount Plugin enabled, rather than the new Kount Command plugin. Uninstalling the Kount plugin resolved the error.

Known Issues

• Resorts that have implemented Aspenware Commerce 2.25, that use Payeezy or Authorize.net as their payment gateway, and have Resort Charge configured and active are sometimes seeing an unsupported feature (update credit card used for resort charge) become active. Customers can address the issue by setting the “customersettings.hideresortchargetab” to false.

• For resorts using the Arrive Parking integration and Authorize.net, if a customer has more than one credit card failure message while booking a parking product, the parking booking will succeed on the second confirm attempt rather than on order complete success, occasionally resulting in double parking bookings.

• For resorts using the Arrive Parking integration and Siriusware as a POS, orders with Arrive Parking products will show as failed in the order queue.

• Aspenware recommends using product cutoff days to automatically direct guests to the first month of the season on the pricing calendar, however, there is an issue where if the proper deep link was used, the correct default month will not load until the page is refreshed.

• On the calendar on the product detail page (PDP), dates that are not defined with inventory in the POS are shown as sold out rather than crossed out. This is resolved on the large calendar, but not for the small PDP calendar.

• Phone prefix is not being sent to RTP|One when the phone number is collected in checkout.

• When a phone number is updated in My Account, it is resulting in an invalid number being added to the beginning of the phone number in RTP|One.

• * Guests who do not have a birth date defined on their profile are not able to log in through Identity. This will be tracked in identity release notes going forward.

• * A customer is able to checkout with a product if the store cutoff time expires but the product is already in the cart. A similar issue was fixed in 2.15, however, this resolved issue was focused on the specification attribute for cutoff days, not time.

• If certain words are used in attribute descriptions, such as “days”, “date”, “day” that are not Start Date or Number of Days attributes, it can impact whether age rules work on the product. See this doc for common troubleshooting.  

• My Account- print vouchers will print the entire screen, not just the voucher.

• The query that runs to display vouchers for the My Account page is only checking if the vouchers were created from a transaction in RTP, not just from Voucher Tools.

• When using the Reimagined Dynamic Pricing modal to set prices for more than one season, ensure that you save the price for one season’s set of pricing, then open and close the modal to add prices for another season - otherwise initial pricing for the first season may be overwritten by the other season’s pricing.

• For several resorts themes, strong and bold HTML tags are no longer working for short and long descriptions.

• For resorts that use the SheerID integration, products that require SheerID validation must have either a waiver, child reg profile, rental profile, or prompt added to them in order to display the necessary SheerID checks. The fix for this would enable the personalization step to load and request the SheerID validation without anything else configured on the product that requires personalization.