Limio Release Notes - Release 78.0
Summary
- New features: Side panel layout improvements and B2B price configuration. - Bug fixes: Gift refunds enabled in LFS, Customer Table fixes and Zuora preview issue resolved in LFS.
New Features and Improvements
Multiple components in side panel layouts
Layouts that use side panels now allow for multiple components to be included in those side panels. This allows for greater flexibility in how you configure your Campaigns and Pages.
Screenshot: Two image components have been included in the right side panel to illustrate multiple components in a single side panel.
Right side panel layout in mobile and tablet view
Components included in the right side panel are now handled in mobile and tablet view. Components included in the side panel will appear above the components configured in the main body of the page and below components in the header when viewed on mobile and tablet.
Screenshot: Desktop view of the Shop shows the Single Product Basket component and Promo Code component in the right side panel next to the main body of the page.
Screenshot: Mobile view of the Shop shows that the Single Product Basket and Promo Code components previously displayed on the right side panel are now displayed near the top of the screen.
Read more about changing the how your components look here:
Overwrite Limio Price when Unit Price is specified in the B2B Flow for LFS
As part of , a new Salesforce Flow was introduced to extend the Limio gift code solution to B2B selling cases. In that Flow, users can set a Unit Price that can be different than the price configured in Limio on the specified offer.
Limio Commerce has been updated in Release 78 so that if the order has a unit price specified, that is the price used in Zuora and Limio Commerce (as long as external pricing is not used). If there is no unit price specified, there are no changes to application behaviour. Please note that this B2B solution only works with new orders, not switches or renewals.
Screenshot: If the Unit Price is updated in the B2B LFS Flow, then Limio Commerce and Zuora will use that updated price for creating order information.
Read more about the LFS B2B Flow here:
Bug Fixes
Unable to process gift refunds in LFS Manage Subscriptions
When LFS users tried to process gift refunds using Manage Subscriptions, an error message was thrown and the gift refund failed. This issue is resolved in this release, by correcting the offer type in the Zuora-Limio order processing plugin.
(Zendesk ticket #2952)
Change name not working in Customer Table component
If a customer tried to change their name in the Customer Table component and saved the change, the change was not reflected instantly. The customer would need to refresh the page in order to see the changes. This bug is fixed in this release.
Unable to update customer details in Customer Table component when no delivery address is specified
If a customer tried to update their address in the Customer Table component, and they only had a billing address previously specified (like if they only had a digital subscription), then an error would occur. This is now is fixed in this release, and customers can update their customer details regardless of whether they have a delivery address specified or not.
Zuora Preview Issues in LFS Manage Subscriptions
The Zuora Preview functionality is throwing a few types of errors in various scenarios that are causing issues in LFS Manage Subscription. We've addressed the root cause of the following errors in this release, and will be addressing more in future releases:
Cannot read properties of undefined (reading 'map') in previewSwitchOffer and previewAddOffe
Request failed: https://rest.eu.zuora.com/v1/orders/preview [undefined] Operation failed due to a lock competition, please retry later.
(Zendesk ticket #3144)
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)
Last updated
Was this helpful?