Published Jan. 10, 2022.
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
Aspenware is excited to expand options for credit card processing to include Windcave Payment Gateway, a globally supported payment gateway that can also act as the acquiring bank in addition to the payment gateway. Our robust integration will eventually support tokenization in conjunction with a futureRTP|One version but this integration is dependent on Active network development.
(Requires release guide and eventual documentation update)
Enhancements
...
, 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.
...
Enhanced Retail Tax Capabilities on Shipping Fees - Not complete or 100% confirmed to make it - HIGH RISK of not making it due to estimate being ~5 days of work
Retail for Aspenware Commerce has always included the ability to charge order-level shipping fees for retail products specifically, however, tax support on these shipping fees has not historically been supported. With Aspenware 2.25 both inclusive and exclusive tax is able to be charged on the retail order-level shipping fee. (Requires documentation update)
...
Display “Parking Location Description” instead of “Entrance Notes” on the Product Detail Page for Arrive Products -
...
Resorts using the integration into Arrive Parking want to stop using the “Entrance Notes” field in Arrive admin and switch to using “Parking location description” for input that displays under the More Info section of the Parking Lot detail. (Requires documentation update)
Resolved Issues (Issues expected to be resolved in 2.25) - All in progress, none 100% complete or confirmed for 2.25, but they are in somewhat priority order
...
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 being created when an order is completed primary credit card was created upon order complete when resort charge is was added. This is issue was likely related to an expiration date setting in Authorize.net configuration that is now being handled differently and is (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.
* When entering a media id on a Fast Flow product, when selecting enter key instead of clicking validate, Enter key refreshes the pageAspenware 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, however, . In the description on of the order in RTP is showing as a general commerce order rather than displaying the rental sales location, which was confusing to frontline staff fulfilling and finding these orders. , 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. *
For certain resorts with specific inventory pool configurations, the inventory sync is occasionally timing out and requires Azure intervention to restart the sync.
For standard Aspenware authentication create account, when specific phone number formats are entered, it is resulting in a guest-facing error preventing create account. This error is especially present when a customer enters a country code in the phone field.
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 - (May require documentation update - talk to Danny G and Marty)
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 Requested field for the rental profile, shoe size, is not required and configuration can only be * managed through Azure (forthcoming enhancements include allowing shoe size to be required and moving configuration out to Nop).
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.
...