Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With great pleasure, Aspenware presents Aspenware Commerce 2.38.
Release Date: February 1st, 2023

Linked Releases

Current Releases

(as of 2/1/23)

Commerce

Identity

Unity

Arrival

Resort Tools

2.38

2.2526

3.33

1.78

3.4

Enhancements

  • Fields were added in Admin to accommodate a JS tag and a CSS tag without code changes in support of integration with 3rd party cookie consent management tools that require those fields. If your resort is interested in integration with a 3rd party cookie consent management tool, contact your Aspenware Representative (support@aspenware.com) to discuss a project with our Professional Services team.

  • We have optimized the following areas of the commerce platform, in order to prepare for our upcoming commerce platform upgrade.

    • Customer Settings

    • Waiver Encryption

    • Legacy User Registration and Login

Resolved Issues

  • Payment Plan Payment Schedules in MiniCart - Payment Plan Payment Schedule accurately now reflects the correct total amount if the customer has more than one multiple quantities of the same product in their cart.

  • Payment Plans - Improvements were made to the grouping of payment plans when a mix of products is included in the payment plan and supports proper revenue recognition in RTP.

  • QR Code - Customers are now able to click ‘Escape’ easily return to the order confirmation page from the enlarged display of the selective selected QR Code.

  • $0 Order - The If using Windcave, Moneris, or Heartland payment gateways, the credit card input field is now masked , in certain flows, when the customer is checking out with a $0 order.

  • Renewal Product - Adding renewal products to the cart behaves as expected.

Known Issues

Key Tag(s)

Summary

Known Version(s) Affected

Apenware AW Payment Plan ModalPayment Plan modal during checkout shows the correct price (inclusive tax), yet in My Account, the Payment Plan Schedule modal shows the [depositDue] before tax, so they're not consistent.Aspenware Payment Plan, TaxAmount

Payment Plan plan payments are creating out - of - balance transactions in RTP |One if the TaxAmount on any payment is not consistent.

2.31.2, 2.33

Apenware AW Payment Plan, Inclusive Tax

There is an a issue with Inclusive Taxes taxes rounding correctly.

2.30.2

Phone Number, RTP|One

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 being getting grouped correctly. This causes the card to be charged multiple times and be 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 must save the price for one time period’s set of pricing, then open and close the modal to add prices for another time period . If it’s not done this way, the - otherwise initial pricing for the first time period season may be overwritten by the second other time period’s 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

On 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 mini 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.