Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

With great pleasure, Aspenware presents Aspenware Commerce 2.24. This minor release is compatible and must be deployed jointly with Aspenware Identity 2.13 and Aspenware Unity 3.19.

New Features

Enhanced Communications Preferences/My Account Functions

Aspenware has added a new feature to enhance options when setting communication preferences, which now includes the option to include a customizable button link to a third-party site for marketing preferences management. Details on configuring this can be found here: https://hub.aspenware.net/main/2.23-Release-Guide---My-Account-Communication-Preferences.2034466933.html.

Enhancements

Ikon Friends and Family

The Ikon Friends and Family plugin has been enhanced to now support multiple entitlement ID types within the currently existing text field boxes. This enhancement allows for comma-separated values that will allow resorts to add both the entitlement ID type that may be used by the passholder (and voucher owner), and those one-use voucher entitlement ID types that can be emailed out from the Ikon website. For more information see the updated Ikon Friends & Family Configuration Guide.

KountCommand Plugin

Kount is a popular third-party fraud prevention and detection tool that is now available for use as a standalone tool, in conjunction with your integrated payment gateway. Users can configure Kount to decline transactions to eliminate potential fraud, or focus extra scrutiny on approved transactions, declining them after the fact and whitelisting the media. An independent account and agreement with Kount must be established to use this plugin. See the 2.24 Kount Release Notes for more information 2.24 Release Guide - KountCommand

Resolved Issues

  • Some resorts with multiple inventory pools assigned to a product that also leveraged mulit-day consecutive date functionality found that these products would receive an “insufficient inventory” error during checkout because there were not enough matching pools. This issue has been resolved.

  • Resorts have reported failed orders after the 2.20 upgrade during high volume sales periods. This is likely related to a time-out error followed by duplicate “complete” calls. Aspenware has disabled this button when error scenarios happen, requiring any timeouts to require re-completion at checkout. In this case, the orders will have defined customers and order line items. Please reach out to Aspenware if failed orders with no line items or defined customers persist.

  • Previously, dates listed in the Print at Home Ticketing confirmation for Siriusware customers were all showing the first product date in the order rather than displaying the subsequent (and actual booked) dates. This issue has been resolved.

  • Previously, an unknown server error was being thrown for some resorts inputting hyphens in postal codes. This issue has been resolved by removing hyphens and special characters from input postal codes.

  • Previously, discount voucher savings were auto-applying on future transactions when the discount voucher was previously used. Now, once an order is complete, any vouchers tied to a guest are removed.

  • The save button is now consistent with all other My Account buttons.

  • The “My Account” dropdown shows an arrow rather than a cursor finger when hovered over rather than an arrow

Known Issues

  • 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.

  • No labels