With great pleasure, Aspenware presents Aspenware Commerce 2.27. This major release is compatible and must be deployed jointly with Aspenware Identity 2.1516, Aspenware Unity 3.21 22 and Aspenware Arrival 1.67.
New Features
Windcave Payment Integration
...
Theme Designer
As part of improving and streamlining our theming process, Aspenware has created a new tool to make implementation of new themes and upgrading existing themes easier than ever. Our new theme designer tool provides resorts with recommended templates and offers our most popular customizations for easy and quick selection and implementation.
...
The most exciting part of this feature work is under the hood, where we’ve packaged up our theming files and folders into resort-specific modules and moved our theme building process outside of the larger commerce build.
...
Future theme adjustments will be faster and easier to deploy with more reliable results. Resorts can also look forward to our upcoming theme plugin, which will allow theme changes without the release!
Checkout Enhancements
Aspenware has taken a deep dive into our code this release to discover , assessing what changes and enhancements could make the biggest difference in our customers’ lives. While resorts may not see any changes to the checkout interface, we are confident you’ll notice a difference in checkout flow timesperformance. 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.
(Requires release guide and eventual documentation update)
Enhancements
Resolved Issues (Issues expected to be resolved in 2.26)
(May be 2.25) Previously, for resorts using Unity for order processing, add-on products were not autofulfilling if the core product that they were sold through was not also set to autofulfill. This is resolved so that add-ons and core products do not have dependencies on autofulfill setup, i.e. add-on products can have independent autofulfill rules from the core product they are attached to.
On the Large Dynamic Pricing Calendar view, UI interactions that highlight the date being hovered over are no longer interactive. - This may be the result of missing configuration - (May require documentation update - talk to Danny G and Marty)
On Product Cards that Display in the Category View, if the price of the product contains cents it is being rounded to the nearest dollar amount - > Not complete or 100% confirmed to make it
...
Enhancements
On some mobile devices, the error massage “City is Required” was displaying 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 gateway.
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.
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. * Though a requested field for the rental profile, shoe size is not required and can be
* 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.
...