Note that BETA release notes are to be considered drafts of what will be included in the upcoming release. They are subject to change and may be altered due to findings during beta testing.
...
We have optimized the following areas of the commerce platform, in order to prepare for our upcoming commerce platform upgrade.
What should we include as the areas touched Leigh Bush ?
GA4 now includes events to capture account creation and login events, as well as fields to capture email address and phone number with the Purchase event.
In GA4, broken links that end up displaying an “Error 404” will now also trigger a virtual pageview event. This will allow resort customers to quickly identify pages with broken links.
...
GA4 - When a tag is triggered, the platform and version reporting with the event level data at the top of the tag displays as expected.
GA4 - The Update Item List ID and Item List Name in the F4 event parameters now use “category_page” and “Category Page” when product was accessed from the category page. This enables users to understand differences in customer add-to-cart, purchase and abandon-cart behavior when products are first viewed and accessed from the category page as compared to related products and cross sell lists.
Payment Plans - Payment plans balance as expected when the tax amount is not consistent. (Kevin says this is actually a Unity fix - not Commerce, but was categorized as Commerce)
Payment Plans (Siriusware) - When a customer has purchased multiple payment plan products in one order with one credit card, the installment payments are grouped and a single payment request is sent to the processor. (Currently blocked - leave in for BETA - 7390)
Payment Plans (Siriusware) - Hotlisting passes associated with a failed payment works as expected. (Currently Blocked - 7107 - Kevin says this is Unity, not Commerce, but was categorized as Commerce)
Payment Value Voucher - When a product is sold through Aspenware Commerce and a payment value voucher is created, the amount on the voucher is set to the price of the product. (Kevin says this is actually a Unity fix - not Commerce, but was categorized as Commerce)
Known Issues
Key Tag(s) | Summary | Known Version(s) Affected |
|---|---|---|
AW Payment Plan, TaxAmount | Payment plan payments are creating out of balance transactions in RTP if the TaxAmount on any payment is not consistent. | 2.31.2, 2.33 |
AW Payment Plan, Inclusive Tax | There is a issue with Inclusive taxes rounding correctly. | 2.30.2 |
Phone Number, RTP | Local Phone numbers do not display correctly in RTP> Order Processing> Customer Order Properties> Phone Profile. | |
Payment Plans, Siriusware | When there are multiple payment plan products in one order, they are not getting grouped correctly. This causes the card to be charged multiple times and get declined. All of the payments do eventually go through with the retries. | Commerce 2.29 |
Dynamic Pricing | When using the Reimagined Dynamic Pricing modal to set prices for more than one time period, ensure that you save the price for one time period’s set of pricing, then open and close the modal to add prices for another time period - otherwise initial pricing for the first season may be overwritten by the other time periods’ pricing. | Commerce 2.23 |
Arrive Parking, Siriusware | For resorts using the Arrive Parking integration and Siriusware as a POS, orders with Arrive Parking products will show as failed in the order queue. | Commerce 2.23 |
My Account, Vouchers | The query that runs to display vouchers for the My Account page is only checking if the vouchers were created from a transaction in RTP|One, not just from Voucher Tools. | Commerce 2.21 |
Mini Calendar | In the mini calendar on the product detail page (PDP), dates that are not defined with inventory in the POS are shown as sold out rather than crossed out. This is resolved on the large calendar, but not for the small PDP calendar. | |
Phone Number, Checkout | Phone prefix is not being sent to RTP|One when the phone number is collected in checkout. | |
Product Cutoff Time, Checkout | A customer is able to checkout with a product if the store cutoff time expires but the product is already in the cart. A similar issue was fixed in 2.15, however, this resolved issue focused on the specification attribute for cutoff days, not cutoff time. |