3.16 Unity Release Notes

Owned by Jenni Buonanni
Last updated: Mar 24, 2023 by Sarah Holst
2 min read

With great pleasure, Aspenware presents Aspenware Unity 3.16. This release is compatible and must be deployed jointly with Aspenware Identity version 2.11 and Aspenware Commerce version 2.21.

Updates, Features, and Upgrades

Pass additional customer information from RTP|One to Happy Cog’s Middleware

Previously the export API passed basic pass information. This export API now passes more rich customer information. The export API passes name, email, phone, DOB, RFID, Status, Rules Name, and Change Date. For Ikon Passholders: we are now passing only one record with the Pass Media #. For employees, this is now returning an Alternate ID instead of the RFID number. This API is currently only licensed to and available for specific Powdr resorts.

Resolved Issues

  • When a product uses multiple inventory locations and is set to autofulfill, if a customer orders multiple inventoried products across locations, the locations are getting incorrectly assigned to the first location upon autofulfil. A workaround is to turn off autofulfill on these products.

  • If using RTP Connect and products that are set up as non-consecutive date selection with add ons, the wrong price for these add ons is passed into RTP|One on order complete. A workaround is to turn off non-consecutive date selection or switch to Unity for order placement.

  • For Aspenware Payment Plans, payment plan payments with tax configured are experiencing a tax rounding discrepancy between what is sent to RTP|One and what the customer paid for certain payment amounts.

  • For orders that have multiple vouchers assigned to the same recipient, only the first voucher is getting assigned to this recipient.

  • The RemoveDeletedInventoryPools function was running even when it wasn’t required. this has been resolved.

Known Issues

  • On very few payment plan payments when a certain error is returned, the customer is successfully charged more than once but shows as failed payment in Aspenware Commerce. (expected to be resolved in 3.18 - the next major release)

  • Phone prefix is not being sent to RTP|One when the phone number is collected in checkout.

  • When a phone number is updated in My Account, it is resulting in an invalid number being added to the beginning of the phone number in RTP|One.