Aspenware Commerce 2.24.1 is a hotfix release that is compatible and must be deployed jointly with Aspenware Identity 2.13 and Aspenware Unity 3.19.
Enhancements
Fraudulent IP Blocking
Aspenware has added a new feature to enable auto-blocking of IP addresses that exhibit fraudulent volume behavior. If an IP address fails on payment complete more than the configured threshold within an hour, the IP will be blocked prior to sending to the payment provider once they surpass the threshold and will be presented with an error message. This includes two new settings, one to enable this functionality, and a second to define the threshold that blocking behavior will be triggered by.
order.ipblocking.enabled- “true” enables this settingorder.ipblocking.threshold- “5” would block someone after 5 failed attempts in an hour. This number is configurable.
Resolved Issues
This version removes the ability to update the credit card used for resort charge stored in RTP in my account altogether. The resort charge in my account feature is normally available to only resorts that use Authorize.net and Heartland for payment gateways but will not work in this hotfix version. 2.25 will re-instate resort charge functionality in a more secure manner.
Known Issues
For resorts using Unity, if an add-on product is set up to autofulfill but is sold as an add-on of a core product that is not set to autofulfill, the add-on product is not autofulfilling.
When entering a media id on a Fast Flow product, when selecting enter key instead of clicking validate, Enter key refreshes the page. This is expected to be fixed in 2.25 (early-Jan major release)
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. This is expected to be fixed in 2.25 (early-Jan major release)
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. This is expected to be fixed in 2.25 (early-Jan major release)
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. This is expected to be fixed in 2.25 (early-Jan major release)
On the Large Dynamic Pricing Calendar view, UI interactions that highlight the date being hovered over are no longer interactive.
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.
Aspenware Identity doesn’t automatically redirect the guest back to the PDP they were on prior to selecting to sign in unless they explicitly use a redirect URL where sign-in is required. This is a feature enhancement to Identity.
Guests who do not have a birth date defined on their profile are not able to log in through Identity.
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.
KountCommand is currently only supported for Heartland. All other payment gateways are expected to be supported in 2.25.