With great pleasure, Aspenware presents Aspenware Commerce 2.25. This major release is compatible and must be deployed jointly with Aspenware Identity 2.14, Aspenware Unity 3.20, and Aspenware Arrival 1.5.
| Table of Contents |
|---|
Enhancements
Improved Edit Cart Capabilities
Previously, it was difficult for guests to make adjustments to their cart items including adding on additional tickets with identical attributes or removing quantity from configured cart items without having to delete the item entirely. For example, if a guest wants to purchase multiple tickets for a family, Aspenware now has added two links to both the cart and the products on the assignment step.
Link 1 - Edit options link: Link including attributes that draws from the cart item ID and directs the guest to a product detail page in “edit mode” with the ability to update the current cart item. If quantity is included on the product detail page then quantity may be adjusted as well.
Link 2 - The product title is linked: This url is a direct link to the product detail page - this link does not put the product in “edit mode,” and represents a faster way for a user to add more of a product already in cart.
Display “Parking Location Description” instead of “Entrance Notes” on the Product Detail Page for Arrive Products -
Descriptive copy that has been populated into the Parkwhiz/Arrive Parking field “location description” now passes to the “Lot Notes” section of the Arrive Parking PDP.
Update Date Formats to shorter, abbreviated versions and keep them consistent throughout checkout
Dates that are displayed on chips in checkout have been styled so they present consistently, in standard abbreviations. Format is ddd, mmm, DD (Sat, Aug 1).
Resolved Issues
Kount Command no longer blocks order placement of guests who do not have a billing address stored in RTP and are not required to provide one in checkout.
Previously, for some resorts using Authorize.net, no primary credit card was created upon order complete when resort charge was added. This issue was likely related to an expiration date setting in Authorize.net configuration (one that was not present for all resorts on Authorize.net). Aspenware now handles the setting differently and primary credit card is be created upon order complete.
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.
Aspenware has updated the Fast Flow module such that when the “enter” key is selected after entering a media idea, the module will validate rather than trigger a page refresh.
For resorts using Unity and Rental Locations, the products are booked to the correct rental sales location. In the description of the order in RTP, it now displays the rental sales location, rather than the previous display of “general commerce order”.
Previously, for standard Aspenware authentication create account, when specific phone number formats were entered, a guest-facing error prevented create account. This error is especially present when a customer enters a country code in the phone field. Now, any number can be submited, even if invalid, however all valid numbers should be automatically reformatted properly.
Now, customers who are not logged in cannot access the My Account page, or the Resort Charge page.
Configuring a cutoff window now results in product no longer being available for purchase once the cutoff date has been reached.
Dynamic Pricing Calendar is once again changing color when a guest hovers over a date.
Known Issues
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.
...