Limio Release Notes - Release 77.0

Summary

- New features: Published Offers API, enhanced Gift functionality, better Edit Address component, error configuration in the Page Builder and rich text upgrades. - Bug fixes: Mass publish stabilised, block to switch Offers enabled, Orders Table improved, Tag resolution and pricing corrections.

New Features and Improvements

Published Offers API

The Offers v2 API is being improved so that only published offers will be available via the API. This was done so that in-progress offers won't be returned by the API, which unifies the experience between what is available in a Limio Shop and other systems like Limio for Salesforce.

Key cases:

• New offer, not yet published - Won't appear in Limio Shop or via the API

• New offer, published - Appears in Limio Shop and API

• Existing offer, not yet republished - Latest published version appears in Limio Shop and via the API

• Existing offer, edits republished - New edits appear in Limio Shop and via the API

Read more about these changes here:

Edit Address component improvements

There were several improvements made to the Edit Address component:

1. Add a new property: "Hide Delivery Address".

2. "Edit Address" links are now buttons under the listed addresses.

3. Default component-id has been corrected from "redeem-checkout" to "edit-address".

Screenshot: A view of the improved Edit Address component in the Page Builder.

Read more about the Edit Address component here:

Gifting extended to work with multi-offer orders

The gifting functionality has been extended so its now possible to redeem multiple gift codes for one order containing multiple offers. Instead of mapping a gift code to redeem the entire order, the gift code will now redeem a specific offer in the order. Please note that the end-user experience for redeeming gift codes is not changing.

This is especially useful for B2B use cases where there are multiple offers associated with one order.

Improved customer experience during authentication errors

When there are errors with the authentication process, users will now be routed to a page at "/error" that Limio Commerce users can configure in the Page Builder. This allows users to configure consistent error pages and provides a better experience to the end customer.

Read more about setting up an error page here:

Rich text fields technical improvement

We've changed how rich text fields render in the Limio Shop to improve stability and increase consistency across the application. There are no visual changes to the rich text fields from an end customer or Limio Commerce user perspective.

Bug Fixes

Both buttons load when one is clicked in Change Billing Address section of Orders Table component

In the Orders Table component, when the customer edited their billing address, if the submit changes button was clicked, both the submit changes and cancel changes button would spin. This has been resolved, so only the button clicked will spin.

Mass publish fails if triggered too quickly after mass build

If the mass publish is triggered too soon after mass build finishes, then the publish can fail. This is resolved in this release.

"Block switch to offers with different products" toggle not working

If the "Block switch to offers with different products" toggle was turned on, customers were still able to switch to a different product. This is now resolved, and customers will not be able to switch to different products if the toggle is on.

(Zendesk ticket #3103)

Edit address button in Orders Table component missing for some customer subscriptions

The edit address button was missing on some customers' Manage My Account pages in the Orders Table component. This is now resolved, and the behaviour is:

• If a subscription’s end date is today or in the future, show the Edit Address button

• If a subscription is cancelled/lapsed (end date was before today), hide the Edit Address button

(Zendesk ticket #3150, #3204)

userDetails object not being sent during Cancel Order

The userDetails object needs to be sent during the cancel order. If this object is not sent, the customer details cannot be updated or passed on. This is now resolved in this release.

Error "Could not fetch Subscription" appears on Discount campaigns

Discount campaigns now need a term__limio attribute and not just discount__limio, otherwise the 'Could not fetch subscription' message appears in the cancel-save-offer component even when trying to apply a discount on a valid subscription.

There is now a condition to fall back to discount__limio term, and this issue is resolved.

(Zendesk ticket #3194)

Some schedules have incorrect prices

If there were multiple rate plan charges on a rate plan, the billing period on the Zuora rate plan charges was set to months, and the Limio price is different than the rate plan charge, then there was a bug where the schedules were created using the Limio price instead of the rate plan charge. This is now resolved, so that the charge amount of the initial term is set by the Limio price but the subsequent charge amounts are set by the Zuora rate plan charges.

Same tag can be added to different pages

If a user tried to add an existing, used tag to a different campaign or page, the tag was successfully added. This is now resolved, and a tag can only be added to one campaign or page at a time.

Price in pre-order doesn't match order price

There was a mismatch between the information displayed in the Single Page Checkout component. The pre-order information price always displayed as €1.00 if the order total was €0.00. This is now resolved, and the pre-order information price will match the order total.

Hotfix: Last rich text change not saved

If a customer made a change to a rich text field and clicked Save, the changes would not be saved. The workaround for this issue was to click into another rich text field before clicking Save. This is now fixed and changes to rich text fields can be saved straight away without clicking into another rich text field.

Please note this was retroactively deployed into Releases 77 and 78. After Release 79, this fix will be included in all releases without redeployment.

(Zendesk tickets #3256, #3266)