Release Date: Mar. 7, 2022.
With great pleasure, Aspenware presents Aspenware Commerce 2.27. This major release is compatible and must be deployed jointly with Aspenware Identity 2.16, Aspenware Unity 3.22, and Aspenware Arrival 1.7.
New Features
...
Theme Designer
...
Checkout Enhancements
Aspenware has taken a deep dive into our code, assessing what changes and enhancements could make the biggest difference in performance. Beginning with the 2.26 Release, resorts may see up to a 500% improvement in checkout complete call speed! In addition to vastly improving the checkout complete call time, we’ve also introduced a CDN (content delivery network or content distribution network). This optional feature helps your pages load faster and reduces latency across your site. For more information and pricing please reach out to your Aspenware service representative and check back often for Aspenware’s formal introduction to the benefits of CDN and initial speed test results.
Enhancements
On some mobile devices, the error massage message “City is Required” was displaying displayed improperly. The message has been repositioned in an easy-to-see location.
For some iPad users, mainly using IOS 12.1 or older, the ability to add Group members was grayed out. This feature is now available again for all iPad users.
The Kount Command Plugin was modified to pass (NULL) as the BIN, and to update the Kount dashboard if a transaction has been approved by Kount, but subsequently denied by the credit card gatewayrather than the previous (000000) value.
Under “My Account” print vouchers will no longer print the entire screen. Instead, it will correctly print just the voucher.
Affirm Payment Plugin is now supporting a multi-store environment.
A minor adjustment was made to the position of the Voucher Banner so it no longer overlaps when using multiple HTML banners.
Some customers reported seeing an age range of 5-12 (Child) displayed in the minicart mini cart as a Date (May 5). This has been resolved.
Payment Plan payments that ran successfully through the payment processor but failed when processed in RTP|One or Siriusware (due to a network disruption, incorrect product id, etc.) did not have an efficient method to re-process. With this version, we have added a “Process - Don't Charge” status that allows for the data to be reprocessed by Siriusware/ or RTP|One but does not recharge the customer’s credit card. For more information see the Aspenware Customer Hub for Payment Plan Products Troubleshooting.
Tax Rates, triggered by shipping addresses, were sometimes being triggered incorrcetly incorrectly on items that were purchased online but consumed at the resort. We have modified the management of multiple tax rates to be applied at the product level, with a determination of the tax rate dependent that depends upon whether shipping is applied to the specific product.
Resort guests using Payeezy as their credit card gateway were reporting that credit card profiles in RTP|One (primary and alternate) were getting created (rather than updated) each time a customer completed a transaction. This has been resolved.
Known Issues
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.
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|One, 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.
...