With great pleasure, Aspenware presents Aspenware Commerce 2.23. This release is compatible and must be deployed jointly with Aspenware Identity version 2.12 and Aspenware Unity version 3.18.
We have a few fun features coming your way including an enhanced dynamic pricing calendar. Below you will find release notes and their attached configuration guides. See Unity and Identity release notes for more information.
Features
Enhanced Dynamic Pricing Calendar
The dynamic pricing calendar now comes with more configuration options than ever, allowing resorts to choose how they would like to inform their guests of ticket inventory. Now, resorts can choose color backgrounds based on either dynamic pricing levels or their inventory levels. A legend informs users of color codes, pulling in the threshold value set in settings. While this enhancement still requires dynamic pricing to be included on a product, resorts without multiple pricing levels can now take advantage of the color indicators based purely on inventory. For more information about this feature and configuration guidance see the 2.23 Configuration Guide for the Enhanced Pricing Calendar.
Aspenware Payment Plan Support for Heartland Portico Payment Gateway
Aspenware Commerce’s Proprietary Payment Plan feature is now integrated for use with Heartland’s Portico Gateway. Guest can self-manage their credit card and admins can take advantage of our easy to configure payment schedules. For more information on Aspenware Proprietary Payment Plans, please click here.
Aspenware Payment Plan Support for Moneris
Canadian resort customers now have the ability to adopt Aspenware Commerce’s Proprietary Payment Plan feature, newly integrated for use with the Moneris Gateway. Guest can self-manage their credit card and admins can take advantage of our easy to configure payment schedules. For more information on Aspenware Proprietary Payment Plans, please click here.
Improvements to My Account Header, New Tab for Communications Preferences in My Account
The MY ACCOUNT display has been improved for ease of use. The original MY ACCOUNT heading is now a configurable language string, which spawns a dropdown list when hovered over. The MY ACCOUNT button that appears will take you directly to the MY ACCOUNt display when clicked.
Under the My Account Tab, a new page (Communications Preferences) is available, specifically for reviewing and updating guest’s marketing preferences. Resorts can control what is displayed, customize the page with unique copy and/or include a URL link to an external page for those who work with a third party CRM.
Additional Customization options to the IKON Pass Friends and Family
Resorts leveraging the IKON Pass Friends and Family discount functionality can now customize the title and subtitle displayed in the discount modal banner that appears on the PDP- in accordance with IKON Pass guidance. Previously there was a single look and feel for all customers using this banner, however, now this banner can be customized to include the resort name.
For Resorts that Use Identity with Commerce, a number of Identity enhancements roll out with this release, including:
Identity Account creation is now customizable and can include links to external pages for terms and conditions
Can trigger actions, like Opt in/out of marketing communications when creating an account through Identity
GTM/GA tracking enabled in Identity
For full details, see Identity Release notes (LINK COMING SOON).
Resolved Issues
For customers using Payeezy as a gateway, if configured for AVS and CVV, this failure/pass message is now being sent with the pre-auth as well as the tokenized call.
Some failures to send orders to the POS occurred during very high volume periods when a timeout occurred on the order complete page and a customer clicked Confirm a second time after the initial time out.
Retail Product Detail Page Images were not displayed on Desktop for some sites.
For resorts using Heartland as a payment provider, if an order total was $0, due to a free product or customer using alternate payment methods to pay off the balance of their order, and the order had a resort charge product, the primary credit card profile was not getting properly stored in RTP|One.
On very few payment plan payments when a certain error is returned, the customer is successfully charged more than once but shows as failed payment in Aspenware Commerce.
The RemoveDeletedInventory function was optimized. NEED TO ADD MORE DETAIL ABOUT WHAT THIS MEANS FOR RESORTS.
Some Admin roles could not see Release Version information from within the Aspenware Commerce Administration Dashboard, this has been resolved.
For products that are setup to use Radio-button date functionality (such as camps, events, seasonal programs, etc.) Cuttoff windows were not being properly enforced. This issue is resolved.
For customers using Heartland Payment Gateway, and RTP’s Resort Charge, credit cards can now be updated in the Resort Charge tab under My Account.
Aspenware recommends using product cutoff days to automatically direct guests to the first month of the season on the pricing calendar, however, there was an issue where if the proper deep link was used, the correct default month would not load until the page was refreshed. This product cutoff days implementation will now load the correct month.
Added support for IKON Friends and Family discount redemption for resorts with multi-storefronts, using single Aspenware Commerce Admin instance.
Known Issues
For parking
When entering a media id on a Fast Flow product, when selecting enter key instead of clicking validate, Enter key refreshes the page.
Guests who do not have a birth date defined on their profile are not able to log in through Identity.
Some resorts have reported that the order history page “bleeds off the page” and this appears to be theme specific and will be handled case by case. If you notice your site experiencing this, contact support@aspenware.com.
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.
Upgrades
Axess SmartLink Upgrade
Previously, resorts using Axess SmartLink gate were restricted to validating against one access product at a time at the gate. Now guests with two different access products can be validated against in one gate. For more information about this enhancement and to read about configuration, see the Axess SmartLink Configuration Guide.
Update 1
What has been updated. How has it been changed. What are the positive outcomes of the change. Any other necessary information for installation (e.g. automatically installed plugin or manual, new settings or new language strings).