Limio Release Notes - Release 76.0
Summary
- New features: Brand new Webhooks view for Limio users and payment details clarity for customers. - Bug fixes: Customer-facing UI improvements, unique Journey IDs, and fixed entitlement webhook.
New Features and Improvements
Payment Table component enhancements: icons and names
Customers will now see the icons for the available credit card options next to the Credit Card radio button in the when editing their payment method. This ensures that the edit payment experience is consistent with the checkout experience.
Screenshot: Icons for available credit card options clearly visible when editing payment method.
Customers can also see the name of the payment method they are using in the Payment Table.
Screenshot: Example of payment name and icon clearly shown for credit card payment.
New change external payment order type
This new backend functionality allows for a new order type: 'change external payment'. This functions in the same way as the existing 'change payment' order, but should be used in cases where a payment provider besides Zuora is being used. This functionality allows all customers (both native and migrated) to update their card details in their MMA.
Contact Limio Support at if you are interested in using this feature.
New way to view webhooks
In order to help users better understand when webhooks are triggered by Limio, there is a new view under Subscriptions called Webhooks. Users can access this page by clicking on “Catalog” in the top left corner, switching to “Subscriptions”, and then clicking the “Webhooks” tab. This view will display all webhooks triggered, along with the corresponding endpoint, timestamp, and event type that triggered it. Clicking on the endpoint will bring users to a page with that displays the format and data sent. This can be helpful while designing endpoints to consume the data.
Screenshot: New webhooks table view.
Read more about using Limio web hooks here:
New prop on Switch Subscription component to preselect first offer in each group
There is a new property on the Switch Subscription component that allows users to toggle whether or not the first offer in each group should be preselected. This can be configured with the "Preselect first offer in each group" prop, as shown below. This change was made to make the experience more consistent with for the Grouped Offers component.
Screenshot: The first offer available in each group is preselected.
Screenshot: The new property for the Switch Subscription component as viewed in the Page Builder.
Read more about Switch Subscription here:
Use subscription name to sync with Zuora
Previously, the most recently added Zuora identity was used when syncing subscriptions with Zuora. However, this could sometimes cause issues with matching subscriptions and accounts. This has been improved so that the subscription name is used when syncing subscriptions to Zuora, as this is a more unique reference.
(Zendesk ticket #3136)
Bug Fixes
Unique ID's for duplicated journeys
When duplicating a journey, the cookies redirected to the Journey from which it was copied/duplicated. This bug is fixed in the release as each journey will have a random ID to avoid duplicates.
(Zendesk ticket #3125, 3165)
Label name in campaign tab displayed incorrectly
In the Label selection dropdown in Campaigns > Attached Offers, the labels were being displayed as the label value instead of the label name. This bug is now fixed and the name displays correctly.
(Zendesk ticket #3132)
Entitlements webhook was not being fired on cancelling a subscription entitlements
When a user cancelled a subscription and the entitlements order plugin was enabled with a URL to send the webhook to, no entitlements webhook was being sent. This is now fixed and working as expected.
Payment table doesn't display if the subscription doesn't have payment method
For migrated customers which had no payment method specified, the Payment Table component wouldn't load. A message has been added so the customer will now be notified to contact support in those cases.
Screenshot: Message to customers when payment details cannot be retrieved due to missing payment method.
Highlighted validation for country filed on Loqate form
In components using delivery address, when trying to change the delivery address fields, the Country field displayed a green highlight and tick, even though other fields did not display like this. This UI is fixed and Country field does not display a Green highlight and tick as per the other fields.
Customer Table phone number validation
There was an issue where the validation on the phone field appeared before the user started typing. This bug is fixed in this release and the validation appears only once the users adds to the phone field.
Last updated
Was this helpful?