Page Comparison

With great pleasure, Aspenware presents Aspenware Unity 3.21. This major release is compatible and must be deployed jointly with Aspenware Identity 2.15, Aspenware Commerce 2.27, and Arrival 1.65

Resolved Issues

Conflicting tax rates causing failed orders

Previously, when customers added two products to their carts with differing tax configurations - based on purchasing products with different tax rates would result in failed orders. Now when products with different rates are purchased simultaneously both tax rates can apply independently. This issue only applies to those resorts that allow both shippable and non-shippable products. In this rare case, resorts need to ensure that Aspenware Commerce and RTP tax zip codes and percentages match exactly. If your resort configures taxes by country/state/zip and therefore differing tax percentages - the order failed with a message that the tax collected differed from expected tax(rather than fixed) and you have any questions please reach out to your service representative.

Vouchers not referencing the RTP voucher template setup

Previously, vouchers produced from a product sale were based on hard-coded values in Aspenware Commerce, rather than referencing the RTP voucher template setup. This resulted in inconsistent voucher template values being recorded in the voucher template table (e.g. required, allow unknown recipient, and use recipient redemption customer). Now, voucher values are coming directly from RTP.