With great pleasure, Aspenware presents Aspenware Commerce 2.37.
Release Date: January 4th, 2023
Enhancements/
In Payment Plans Admin > Product Assignment, the Payment Product ID field is now a dropdown so that administrators can select a valid Payment Product ID. The dropdown is populated with products that have a price of $0 and do not have attributes.
In Payment Plans Admin > Product Assignment, the Failed Payment Retry Days field now defaults to 1 and is enhanced with error messaging when fields are not populated when Apply Changes is selected.
Windcave is now integrated with RTP|One, and is capable of passing a token via Aspenware Commerce, for storage in the primary and alternate credit card profile in a customer record in RTP|One. Tokens can be used to process refunds, support COF purchases and resort charge purchases.
Resolved Issues
Multifactor Authentication - The Continue button is now activated after an administrator user scans the QR Code when setting up an Authenticator app.
GA4 - When a tag is triggered, we will now see the platform and version reporting with the event-level data at the top of the tag.
PDPs with Available Start Date - When a change is made to an available start date, the change is automatically reflected in the store.
Payment Plans - Customers who purchase payment plan products now see a consistent and correct display of their transactions, regardless of whether the items purchased were subject to sales tax.
reCaptcha - reCaptcha box no longer displays off-screen if reCaptcha is not enabled.
Resort Charge - Order no longer fails when a customer pays for a product fully with Points, Vouchers, or Gift Cards and then selects the Enroll in Resort Charge checkbox in the checkout flow.
Payment Plan Payment Schedules in MiniCart - The Payment Plan Payment Schedule has been updated to accurately reflect the total amount if the customer has more than one of the same product in their cart.
Known Issues
Key Tag(s) | Summary | Known Version(s) Affected |
|---|---|---|
Aw Payment Plan Modal | Payment Plan modal during checkout shows the correct price (inclusive tax), yet in my account, the payment plan schedule modal shows the [depositDue] has before tax, so they're not consistent. | |
AW Payment Plan, TaxAmount | Payment plan payments are creating out of balance transactions in RTP if the TaxAmount on any payment is not consistent. | 2.31.2, 2.33 |
AW Payment Plan, Inclusive Tax | There is a issue with Inclusive taxes rounding correctly. | 2.30.2 |
Phone Number, RTP | Local Phone numbers do not display correctly in RTP> Order Processing> Customer Order Properties> Phone Profile. | |
Payment Plans, Siriusware | When there are multiple payment plan products in one order, they are not getting grouped correctly. This causes the card to be charged multiple times and get declined. All of the payments do eventually go through with the retries. | Commerce 2.29 |
Dynamic Pricing | When using the Reimagined Dynamic Pricing modal to set prices for more than one time period, ensure that you save the price for one time period’s set of pricing, then open and close the modal to add prices for another time period - otherwise initial pricing for the first season may be overwritten by the other time periods’ pricing. | Commerce 2.23 |
Arrive Parking, Siriusware | 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. | Commerce 2.23 |
My Account, Vouchers | 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. | Commerce 2.21 |
Mini Calendar | In the mini 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 Number, Checkout | Phone prefix is not being sent to RTP|One when the phone number is collected in checkout. | |
Product Cutoff Time, Checkout | 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 focused on the specification attribute for cutoff days, not cutoff time. |