...

...

• 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

...

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

...

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

Validation on Reservation Products

...

Prompt Error Messaging

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

...

• 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

...