Published Mar. 7, 2022.
With great pleasure, Aspenware presents Aspenware Commerce 2.27. This major release is compatible and must be deployed jointly with Aspenware Identity 2.16, Aspenware Unity 3.22, and Aspenware Arrival 1.7.
...
On some mobile devices, the error message “City is Required” was displayed improperly. The message has been repositioned in an easy-to-see location.
For some iPad users, mainly using IOS 12.1 or older, the ability to add Group members was grayed out. This feature is now available again for all iPad users.
The Kount Command Plugin was modified to pass (NULL) as the BIN, ratherthan the previous (000000) value.
Under “My Account” print vouchers will no longer print the entire screen. Instead, it will correctly print just the voucher.
Affirm Payment Plugin is now supporting a multi-store environment.
A minor adjustment was made to the position of the Voucher Banner so it no longer overlaps when using multiple HTML banners.
Some customers reported seeing an age range of 5-12 (Child) displayed in the mini cart as a Date (May 5). This has been resolved.
Payment Plan payments that ran successfully through the payment processor but failed when processed in RTP|One or Siriusware (due to network disruption, incorrect product id, etc.) did not have an efficient method to re-process. With this version, we have added a “Process - Don't Charge” status that allows for the data to be reprocessed by Siriusware or RTP|One but does not recharge the customer’s credit card. For more information see the Aspenware Customer Hub for Payment Plan Products Troubleshooting.
Tax Rates, triggered by shipping addresses, were sometimes being triggered incorrectly on items that were purchased online but consumed at the resort. We have modified the management of multiple tax rates to be applied at the product level, with a determination of the tax rate that depends upon whether shipping is applied to the specific product.
Resort guests using Payeezy as their credit card gateway were reporting that credit card profiles in RTP|One (primary and alternate) were getting created (rather than updated) each time a customer completed a transaction. This has been resolved.
...