Release Date: TBD6/6/24

...

Cloud UI Enhancements

Product, Discount, and Product/Discount Vouchers

• Cloud UI now supports enhanced flows for Product Vouchers, Discount Vouchers, and combined Product/Discount Vouchers.

• Enhancements for Cloud UI include new redemption flows on Product Voucher PDPs and Large Pricing Calendars, new modals, new language strings, and new alert prompts.

  Modal

  Note that iconography

  colors

  can be

  configured through ThemeDesigner

  customized by Aspenware Customer Success.

...

Payment Plans

• Foundational work has been completed to support Payment Plans in CloudUI Cloud UI in an upcoming release.

Assignment on the PDP

• Admins can now configure products to allow guests to assign products to group members on Cloud UI PDPs. When enabled, guests can also create group members on Cloud UI PDPs.

...

Related Products Design

• The Related Products design has been enhanced on the Cloud UI PDP to optimize spacing for images and text.

• When hovering, arrows will indicate that the guest can scroll left or right to access additional products.

• Additionally, the furthest product card is displayed to clearly signal there are more products to scroll through.

Item Summary “You Saved $__” Text

• The Item Summary text for “You Save $__” has been repositioned to enable a more fluid flow for guest viewing and to stay consistent with the cart page.

Cloud Header

We’ve added a couple of enhancements to our Cloud Header. These are available through Theme Designer, so talk with your Aspenware Service Agent if you are interested in these options.

• The Parent Category in the header can be configured to display a customizable underline beneath the category name for active, hover, and focus states. The side navigation can be also configured to display a customizable vertical bar next to the category name. The color, weight, and spatial positioning from category text for the underline and vertical bar can be configured

• The Cloud Header’s font weight can now be adjusted.

Resolved Issues

Cart Quantity with Back Button

• After removing product(s) from the new cart page, clicking the browsers back button would incorrectly display the previous quantity in the cart icon. This has been fixed.

Button Groups

• An issue where Button Groups were not being always being displayed vertically has been fixed.

Related Product Cards

• Related product cards on Cloud UI had a small area that was un-clickable and has been fixed to be fully clickable.

Unavailable Variants with Radio-button Dates

• Switching to an unavailable variant for a radio button date-configured product after selecting an available date was enabling "add to cart" to be clickable when it shouldn't. This has been fixed.

AUS-Specific Resolved Issues

• We fixed the AUS settings for store-wide product cutoff times that were not always respected when the product was purchased outside of the local timezone.We addressed an issue specific to AUS resorts, where a small number of guests from timezones far from the resort's local time could not add the first date of the season to their cart.

Edit Cart with Quantity Greater Than One

• We addressed an issue where editing a cart with an existing product quantity greater than 1 did not always default the edit page to display the existing product quantity.

...

Enhancements

Aspenware Admin Order Queue

...

We’ve made some exciting enhancements to the Aspenware Admin Order Queue. Now, when admins go to Order Queue > Record Queue Admin, they will see the following new options and an updated UI:

New Order Queue Features

• Improvements have been made to the order retry logic by adding more retry attempts to the Order Processor and by maintaining records of reasons for the retry. You may also reach out to your representative concerning configuration options to prevent retry attempts for specific error cases.
  

• A Set Manually Resolved button is now available for orders resolved by Admins or Customer Success Specialists so that orders that have been resolved don’t continue to show as failed and cause confustion. Once the button has been selected, the order status will change to ‘Success,’ and the Manually Resolved column will change to ‘True.’ These orders will now show both when using the dropdown search bar to search for “Success” and “Manually Resolved”. Logs will show the Admin user and a time-date stamp for when this action was taken. See images below for an example using Aspenware Order ID 15001072.
  

  

• The Manually Resolved column shows whether an order has been manually resolved by showing a status of “True” once an admin has made and approved the change by selecting the “set manually resolved” button. When searching statuses, the dropdown “manually resolved” will show all orders that have a Manually Resolved status of True (these orders will also now be shown as success in the order queue).
  

  

Order Queue Changes

• The previous “Object ID” is now named “AW Order ID” and ID refers to the order number (and Store prefix) that appears on the order complete page and in the order confirmation email.

• Order ID is now also a hyperlink. By clicking the Order ID, Admins are taken to the Order page where they can view order details. See image below.

• The previous “Master Order ID” is now named “POS Order ID” and now displays the RTP POS Order ID and may continue to be used for auditing purposes. See image below.

• Set as Ready: Previously, both successful and incomplete orders could be Set as Ready.Now, because incomplete orders are automatically retried (and require manual intervention) and successful orders should not be retried, only failed orders can be Set as Ready.
  

  

• Previously, error logs could be inconsistent when reporting issues. Now, all order processing errors show errors that occur while attempting to process an order, including syncing that order with RTP should show more detail in the logs and include a more user-friendly interface.
  

  

Removed from Order Queue

• Master Status has been removed from the Order Queue Admin view

Future Reservations Enhancements

• We implemented diagnostic structured logging to support Aspenware’s future reservation service. This organized format enhances Aspenware's ability to compare, analyze, and troubleshoot errors.

Order Processor

• We have enhanced the order processor function. Now, when processing a batch of orders all records are set to “PROCESSING“ status before starting processing rather than when record processing begins. This will prevent case when two instances will try process same set of records.

• The durable function support for the Azure Order Processor was removed. This work will improve stability and simplify the Azure Order Processor function as well as save on storage cost.

Resolved Issues

Payment Plans

• An issue that required a temporary widget has been fixed in code and the “Voucher/nav overlapping payment plans style fix“ widget should now be removed. Previously, the Payment Plan modal would appear behind certain page elements.

• An issue in which the checkbox for updating multiple payment plans was only selecting the top payment plan has been fixed. Now the update all checkbox will automatically select all payment plans and allow the user to update all cards at once.

Subcategory Display

• Subcategories that were defined as hidden within a parent category that wasn't hidden were still being shown. Now, subcategories within a hidden category are not visible.

Renewal Page Loading

• An issue where the Renewal Page would not load and displayed and error page has been fixed.

Cloud Header

• The store footer now displays on the Full-page Cart page.

Widget Zone

• Previously, a widget zone was not visible in the admin drop-down menu, but now it is displayed and can be selected.

Voucher Date Formatting

• We have fixed an issue where date formats for non-US dates were formatted incorrectly on vouchers.

Head of Household Error

• We have corrected an issue where if two users in the same account, a dependent and ‘Head of Household, sign in, they would ‘flip flop’ with the ‘Head of Household’ status, which allowed the guest to checkout, but the order would fail during the processing of the order. This is corrected in both Identity v2 and v3.

Prompt Error Messaging

Validation on Reservation Products

• Aspenware has fixed an issue reported by one resort that showed an occasional lack of validation for reservation products. Now, when a customer cannot be validated, an error is shown and the reservation can not be madeOne resort found that when product prompts faced issues loading, no meaningful error message was displayed. Validation has been put in place such that if an error occurs and the prompt cannot be saved, a meaningful error message will be shown and the user may try again.

Site Performance

• We removed instances of unused CSS and jQuery to improve site performance.

Dynamic Pricing Display Updated Pricing

• We fixed a display issue in the Dynamic Pricing v2 tool that made it appear like pricing wasn't updating when an admin navigated back to a previous “Time Period” during a single entry session.

Windcave Credit Card Digits

• We fixed an issue in which resorts using the Windcave payment gateway were seeing the incorrect last 4 digits of the credit card in My Account > Payment Plans (this was an encrypted version of the last 4). Now, the unencrypted last 4 digits display in My Account > Payment Plans.

...

Enhancements

Currently, when a new guest registers, RTP defaults the country to USA. This creates a discrepancy for Resorts resorts if trying to report on where there guests are coming from. To solve this, there is a new Unity rtp-config.json configuration entry called “AllowPlaceholderAddress,' which, if set to 'false’ will NOT default the country to USA. Reach out to customer success to help configure this setting if interested.

• AllowPlaceholderAddress: true - default value if setting is omitted and current functionality will remain. The default country will be saved as “USA” along with '.' for every other address field (address line 1, city, state, zip)

• AllowPlaceholderAddress: false - the address profile in RTP won’t populate any data if a full address isn’t saved.

Transaction ID for Financial Reporting

• We have added ‘transaction ID’ to the unity API so clients can utilize for financial reporting purposes, if needed.

New Order Status for Enhanced Troubleshooting

Aspenware introduces a new status in the order queue admin view to better understand and address order issues. Orders that do not successfully process are marked as Failed and allow for the admin to set the order to “ready” status and have the order processor attempt to try to re-process the order. On rare occasions, a failed order set to the “ready” status returns as a “success” despite not having fully processed into RTP. This could lead to guest arrival with an incomplete order and result in confusion for both admins and Aspenware Customer Service trying to address the issue.

Now, if failed orders are retried and and the order does not fully populate in RTP during reprocessing the order will return with a status of “Incomplete” and an error log is included that helps indicate the source of the processing issue. Because these issues usually result in partial orders that must be remediated in RTP, the order no longer gives a false positive and cannot be reprocessed. This should cut down on admin confusion and help with troubleshooting. Report any orders that are in this state to Aspenware so that we can help resolve them.
Note that this setting is available in Commerce 3.4 or later.

Image Added

For information on all order statuses see Order Statuses on the Customer Hub.

Resolved Issues

Multiple Type Codes in RTP

• Previously, in rare cases, sign-in issues occurred when a customer record in RTP had multiple Alternative IDs associated with a single type code. Now, customers can have multiple Alternate IDs associated with 1 type code and will not experience any sign-in issues.

Voucher Creation for Non-Autofulfilled Products

• Previously, only one (1) voucher was being created when multiple vouchers were defined to be created for products not auto-fulfilled into RTP. This has been fixed. For resorts using vouchers that are not autofulfilled, please verify that the number of vouchers created is now correctAs a precaution, when performing UAT testing, Aspenware recommends that resorts review that the correct number of vouchers are created for voucher products that are not autofulfilled.

Resort Tools

• When a customer selects to add the Damage Waiver/Insurance in Aspenware Resort Tools, the RentalForm created in RTP will now have the ‘InsuranceInd’ parameter set to ‘Yes.’ Previously, this was not being updated when the guest opted-in for insurance.

• The number of days the customer booked online for a rental product now display when fulfilling the order in RTP after using Resort Tools. Previously, this was defaulting to 1 day even if someone bought the rental for multiple days.

...