...

...

By default, a horizontal button group will be displayed. However, the display format will switch to a vertical group under the following conditions:

• If there are 3 or fewer values in the group and at least one attribute value exceeds the maximum width of 7 ~7 characters.

• If any attribute value in the group has an associated add-on price.

• If any attribute value in the group contains a pipe character “|”.

...

For resorts using a full-page cart (unlocked when Commerce Site Nav is enabled), a link allowing users to Continue Shopping, linking back to the default category, is visible under the checkout button. This link uses resort’s body font and can be set to force caps or not.

...

• Improved error messaging for declined transactions processed by Windcave; customers will now receive a more specific message: "Payment error: Payment declined. Please verify your details and try again. Contact your bank if the issue persists," aiding in clarity and resolution for guests and resorts.

• Fixed issue where some customers using the Windcave payment gateway who received the 3DS challenge, could select the cancel button and still proceed through checkout without completing 3DS. Now, all guests attempting to cancel the 3DS challenge must re-enter their credit card information and complete the challenge before completing checkout.

• Addressed rare issue where customers of resorts using the Windcave payment gateway would not be prompted not to retry their payment information until after the checkout complete step when a validation failure occurred. Now, when a failure to validate payment information occurs, the customer is prompted to re-enter within the payment step rather than the complete step. Note: Aspenware recommends resorts using the Windcave payment gateway test this feature using production credentials and live credit cards when upgrading to this release.

Credit Card Entry Field Loading with Square

...

Enhancements

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 Removed

For information on all order statuses see Order Statuses on the Customer HubNote: A previous version of this page erroneously included a new order status for enhanced troubleshooting for orders. This enhancement can now be found in the Release Notes for Unity 3.46.

Resolved Issues

Enhanced Unity Compatibility

...