2.21 is in beta and these release notes are unfinalized. If you are beta testing this version and would like to know what features and fixes are introduced in this release, use this guide as we will be updating it frequently.
With great pleasure, Aspenware presents Aspenware Commerce 2.21. This release is compatible and must be deployed jointly with Aspenware Identity version 2.11 and Aspenware Unity version 3.16.
| Table of Contents |
|---|
Updates, Features, and Upgrades
...
Details coming soon
Resolved Issues
Memory fixes - Aspenware Commerce will now run in 64-bit mode, which resolves a memory-related issue some sites were experiencing. This fix requires a web config setting change. If you receive an “out of memory” error when navigating the Aspenware Commerce admin or if Azure indicates a memory issue and you are on version 2.21 or later, check with your Aspenware Representative to ensure your store is running in 64-bit mode.
For Fast Flow products, scanning of a QR code to populate media ID does not work on Chrome, which impacts Android users. Note that this fix requires a webconfig web config setting change. If experiencing this issue on a any version 2.21 or later, contact your Aspenware representative about updating the web config for the “Feature Policy” section to set the “camera mode” to ‘self.'
On the large pricing calendar, dates that are not defined with inventory in the POS are showing as sold out rather than crossed out. The following logic now applies to the large pricing calendar. Note that the small calendar that appears on the product detail page does not follow this exact same logic and some dates that are not priced and do not have defined inventory will still say continue to display as sold out when hovered over (see known issues below). To determine which message/treatment is given to give dates on the large pricing calendar, the following logic is used:
If dynamic pricing is not configured for a date, the date shown crossed out, no sold-out messaging will appear on the large even if inventory comes back 0 for that date.
If dynamic pricing is configured and inventory is configured on a date and if inventory is sold out or not present for a date, then the date will show as sold out messaging.
If dynamic pricing is configured and inventory is configured on a date and inventory is available on that date, show price.
When using the new Fast Flow with Reservations functionality, reserving two different people for the same day is incorrectly assigning both reservations to the first person.
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.
Better error messaging for guests who do not have a birth date defined on their profile but try to login through identity. NOTES ON HOW TO UPDATE ERROR MESSAGING IN IDENTITY FOR THIS VALUE COMING SOON.
When using Payeezy as the gateway and resort charge is enabled, guests are allowed to define a credit card that is not the card being used for the order for resort charge. This capability is now disabled, so only the card used to pay for the transaction can be stored as the primary (resort charge) credit card profile and this primary card will be stored as a tokenized value.
For orders that have multiple vouchers assigned to the same recipient, only the first voucher is getting assigned to this recipient.
...
Cannot create new subscription types in Aspenware admin (expected to be resolved in 2.21).
If a resort uses Aspenware Identity for authentication and if click tracking was turned on in SendGrid, for some email clients (namely Outlook 365), the URL for password reset links exceeded the URL length parameters for that email client and would get truncated, returning invalid. (Also see Identity 2.11 release notes).
For resorts that use a combination of Aspenware Identity and the Loyalty feature in Commerce, when guests are asked to enroll in the Loyalty Program from Identity, the content next to the enrollment checkbox now supports some HTML. See documentation for additional details on supported HTML.
...
Known Issues
Guests who do not have a birth date defined on their profile are not able to log in through Identity.(Expected to be resolved in 2.23)
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 2.21)
On the calendar on the product detail page (PDP), dates that are not defined with inventory in the POS are showing as sold out rather than crossed out. This is resolved on the large calendar, but not for the small PDP calendar.
Capture of Additional Customer Data feature when capturing zip code only data always sends back USA as the country in the RTP address profile regardless of the resort’s location.
Phone prefix is not being sent to RTP when phone number is collected in checkout.
When a phone number is updated in my account, it is resulting in an invalid number getting added to the beginning of the phone number in RTP|One.
...