With great pleasure, Aspenware presents Aspenware Commerce 2.25. This major release is compatible and must be deployed jointly with Aspenware Identity 2.14 and Aspenware Unity 3.20.
New Features
Windcave Payment Integration
Details coming soon
Enhancements
Improved Edit Cart Capabilities
Details coming soon
Resolved Issues (Issues expected to be resolved in 2.25)
Auth.net expiration date issue- https://aspenware.atlassian.net/browse/TCW-3141
Previously add-ons were not autofulfilling if the core product that they were sold through was not also set to autofulfill. Add-on products should be able to have independent autofulfill rules from the core product they are attached to, so this is now fixed so that there are no dependencies on autofulfill setup.
When entering a media id on a Fast Flow product, when selecting enter key instead of clicking validate, Enter key refreshes the page.
For resorts using Unity and Rental Locations, the products are booked to the correct rental sales location, however, the description on the order in RTP was showing as a general commerce order rather than displaying the rental sales location, which was confusing to frontline staff fulfilling and finding these orders.
For resorts using Unity and Retail functionality, a shipping fee product should be sold into RTP when an order-level shipping charge is added to an order. Presently, this additional shipping fee product is not included in the order when it gets to RTP|One.
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.
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
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.