Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 2.12 Identity Release notes (LINK COMING SOON).Notes

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.

  • For resorts using the Heartland Payment Gateway, the “Sandbox mode” messaging persists when production credentials were added. This can be temporarily fixed in 2.22 versions using an HTML Widget. Talk to your Aspenware representative if this is desired.

  • For resorts using Aspenware Payment Plans, 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.

  • Some Admin roles could not see Release Version information from within the Aspenware Commerce Administration Dashboard, this has been resolved.

  • For products that are set up to use Radio-button date functionality (such as camps, events, seasonal programs, etc.) cutoff windows were not being properly enforced. This issue is resolved.

  • For resorts using the Arrive Parking integration, when a customer navigates to a future month in the date selector for Arrive products, no inventory is available. If they navigate forward, then back to the future month that did not display dates, dates will become available.

  • For resorts using the Arrive Parking integration and Authorize.net, if a customer had a credit card failure message while booking a parking product, the parking booking would succeed on initial confirm attempt rather than on order complete success, occasionally resulting in double parking bookings. Now, if a credit card charge failure occurs on the confirm step, the attempted booking is canceled (though the customer will be emailed that it’s canceled) and the parking booking will only persist if an order is successfully completed.

  • Retail Product Detail Page Images were not displayed on desktop for some themes.

  • 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. This has been fixed for a number of resorts in 2.23.

...