Aspenware presents Aspenware Commerce 2.8. In this release, we’re happy to announce enhancements to Guest Checkout, security and search engine optimization improvements, enhancements to Unity, and numerous improvements to golf including new online check-in functionality. We’ve also addressed a number of high-priority issues.

Updates, Features, and Upgrades

Things to Look Forward to

1Risk Integration

Identity enhancements

Aspenware Payment Plans

Features

Guest Checkout Enhancements

We’ve enhanced Guest Checkout to add configurable language strings to the Guest Information form so resorts can customize buttons, labels, and helper text. We’ve also added a new setting that allows the administrator to choose which guest sign in form to show first, so it’s possible to either emphasize traditional login, or guest checkout, depending on whether the resort wishes to encourage one over the other. We’ve enhanced the customer duplicate prevention logic to identify guests who have a username which is different from their email address, to encourage those guests to login, if we find an existing account. As always, in the guest checkout flow, guests are encouraged to login with their existing account, but they are never forced to do so, they can still continue to checkout as a guest if they wish.

See the release guide for more information on Guest Checkout, including the names of all configurable language strings 2.7 - 2.8 Release Guides - Guest Checkoutarchived

Golf

Customer Pre-pay

With this release we are excited to announce online customer-facing check-in. Now, customers can pay for their tee times on the day of play through Aspenware Commerce. Additionally, we have made enhancements to Check-in/LS Retail and resolved several key issues. For more information see our release guide including configuration documentation.

Email confirmation includes check-in link
When booking on Aspenware Commerce sites, customers now receive emails including actionable buttons that auto-populate a customer check-in screen with their reservation confirmation details.

Customers may forward these emails to others on the reservation, allowing different players to select and pay for their individual slots.
Check-in link parameters have also been made available for outside email providers.

Online check-in/pre-pay on the day of play
On the day of play, customers may follow the link to check in for any number of slots in their reservation online. Additional functionality includes:

Customers can search for their reservation on the day of play by selecting their course, entering their confirmation number and the reserver’s last name.
Guest checkout is available for pre-pay customers.
Customers can see who from their party has checked in and whether any slots are pending (i.e. in the process of) checking in.
Customers are prohibited from checking in early, checking in late, checking in with a zero dollar reservation (if deactivated), and checking in with an incorrect reservation.

Configurable language strings for several informational messages
Aspenware has made language strings configurable for the following pre-pay check-in messaging

Reservation not found
Too early to check in messaging
Too late to check in messaging
Information on how to check in

Toggle for allowing zero dollar check-ins
Aspenware has added a toggle for allowing zero dollar check-ins. When activated, zero dollar check-in allows members (or any other zero dollar reservations) to check in without visiting the pro shop.

Enhancements

Narrowed customer search results
Administrator Check-in now narrows customer search results to exclude guest accounts, making finding the proper customer (retrieved from RTP) easier to find.

Update customer record in EZLinks
Whether checking in through the pro shop or online, payer names are now updated in the reservation slot on all check-in screens as well as in EZLinks.

Golf Issues Resolved

Pending orders are no longer created when customers receive 'tee time no longer available' errors.
Check-in/LS Retail now automatically selects newly created customers.
Header links now displaying properly in test and production golf sites.
Golf terminals can now be adjusted to different courses in Aspenware Commerce admin.
Various check-in issues across production sites.

Change to history mode for product urls (remove hash)

In order to improve SEO, which ignores everything to the right of a hash symbol, our page routing on the store now uses history mode rather than hash mode in the browser. The previous URL [store]/#/[category] is now [store]/s/category. This improvement will also make it easier to reference product category pages from outside sites. *Note: Current links from outside sites which use [store] /#/ will redirect to [store]/s/ automatically.

Order Processor Performance Enhancements

In this release, we’ve modified the Order Processor to handle processing orders in parallel. Previously, the Order Processor submitted orders one at a time to Unity, which were then submitted from Unity to the fulfillment systems, also one a time. This sometimes caused orders to ‘stack up’ and display as ‘Ready’ in the Order Queue for a long period of time, since each order had to wait for the next order to process before it could be submitted.

Now, the Order Processor submits a batch of orders on an interval. This improved Order Processor function submits 10 orders in parallel, every 60 seconds, rather than one at a time. This improvement offers faster and more efficient order processing, particularly when the store is under heavy load.

NOTE: As a result of this enhancement, the orderIDs created in the fulfillment system can be created in a different sequence. For example, previously, if the store created order IDs PK10752 and PK10753, the fulfillment system order IDs would be sequential, such as 100012 and 100013. Now, because orders are created in parallel, the fulfillment system’s orderIDs may not necessarily be in the same sequential order as the store’s order IDs. This does not affect the data, but it may affect guest service agents who are looking up multiple orders for the same customer, since their search results for those orders could be in a different sequence.

Update JQuery to 3.5 - Security Enhancement

Aspenware Commerce has been enhanced to support JQuery Version 3.5, which was released in April 2020. This new version of JQuery addresses a potential vulnerability in cross-site scripting (XSS) in certain cases.

Enhancement to display Unity version used by Aspenware Commerce

A useful new enhancement now displays the Unity version used by the Aspenware Commerce stores on the Dashboard in administration. This handy utility also displays Unity status, which allows for quicker troubleshooting in the event of a service interruption.

Issues Resolved

Order Amounts for GL Export

Previously, for some RTP|ONE customers using the GL Export, the Order total in the export did not match the amount the customer paid. The order totals in Aspenware Commerce and in RTP|ONE were correct, but the GL Export order total was incorrect. This issue has been resolved in this release.

Product/Recipient Vouchers Not Displayed in My Account

For RTP|ONE resorts using product/recipient vouchers (for Friends and Family benefits), this voucher type did not display in My Account, so the guest was not able to view these vouchers. We’ve added support for the Product/Recipient Voucher type, so guests can now view and print these vouchers from My Account.

Header links not displaying after update

There was an occasional problem for some customers where their header links did not properly display after an Aspenware Commerce update was deployed to the store. This issue has been addressed.

Unrelated members shown in My Account and checkout

There was an an issue for some Siriusware resorts where a few guests saw unrelated people in My Account and in member assignment on checkout. This problem is now resolved.

500 on Assign Media Step in Reload

For some RTP resorts, users were seeing a 500 error during checkout if the user had reloadable media. This issue has been addressed.

Navigating directly to a category page without a # or s in the URL allows the user to view all products (including hidden products)

Previously, if an external site linked into a product category in the store, if they had a typo in the address, it was possible in some cases for users to view hidden categories. This issue has been addressed.

Activities Times shown in 24-hour clock

For RTP resorts using activities in Aspenware Commerce, activities were shown in a 24-hour clock (for example, 15:00 was displayed rather than 3:00 p.m.). This issue is resolved and times are displayed in a 12-hour clock format.

Invalid Prompt Code creates order

For RTP|ONE resorts using Unity without RTP|Connect, an order was being created in RTP|ONE even when a prompt was not configured correctly with a valid RTP|ONE prompt code in Aspenware Commerce. Creating the order without a valid prompt code resulted in an enterprise framework error in RTP|ONE if a user tried to open the order. This issue has been addressed, and the order now fails with a meaningful error message, allowing the administrator to correct the configuration problem and reprocess the order.

Invalid RTP Authorization Type Code (Waiver) results in incomplete order in RTP

Similar to the issue above, previously, for RTP|ONE resorts using Unity without RTP|Connect, an order was created in an incomplete state if the product purchased in Aspenware Commerce was incorrectly configured with a waiver authorizationtypecode which did not exist. The resulting order could not be opened in RTP|ONE. This issue has been corrected, and the order now fails with a meaningful message, explaining that the Authorization Type Code is not configured, allowing the admin to correct the problem, and reprocess the order.

Aspenware Customer Hub

2.8 Commerce Release Notes