For the complete documentation index, see llms.txt. This page is also available as Markdown.

Release 117

✨ Highlights

  • Introducing Limio Agents. A conversational AI assistant that runs inside your shop, answers questions about your products and offers, and can take a visitor all the way to a checkout.

  • A fresh look for the Limio app. A cleaner, more consistent design across every screen.

  • Embed video on your pages. Upload video straight to the Assets library, with no need to host it elsewhere first.

Breaking changes


New Features

Introducing Limio Agents

Limio Agents is a conversational AI assistant that runs inside your shop. Visitors ask a question about your products or offers, and the agent answers, recommends the right one, and can take them through to a checkout, all in the conversation. You set one up entirely in Limio, with no code.

  • Knowledge from your own content. Attach your own documents so the agent answers accurately and consistently with your material.

  • Know your catalogue. The agent works from your live offers, with their real names and prices, so every recommendation is one you actually sell.

  • Take the customer through to checkout. The agent can hand a visitor a ready-made checkout link for the offer they chose, and every order it brings in is tracked back to it.

  • Pick up where the agent left off. Decide what a conversation should achieve, such as capturing a lead or recognising a potential buyer, and see how each one ended, so your sales team knows who to follow up.

  • Put it where you want it. Add it as a floating chat widget, or as a panel on any page, styled with your own logo, wording and colours.

Read more in the Limio Agents documentation.

A fresh look for the Limio app

We have introduced an app-wide redesign, improving both how the Limio app looks and how it is to work in.

  • A cleaner, more consistent design. Buttons, labels, cards and tags look and behave the same wherever you are.

  • Simpler navigation. The side menu and the app switcher are now one consistent component.

  • Clearer lists and tables. Lists and tables are easier to read and quicker to work through.

  • Works on smaller screens. The layout scales correctly on a laptop or tablet.

This is an ongoing project, and more improvements will follow in later releases.

Embed video on your Limio pages

You can now upload video to the Assets library and place it on your pages, with no need to host it elsewhere first. Videos must be mp4 or webm and under 512MB.

Improvements

Self-service is now available for subscriptions synced from Zuora

Subscriptions brought into Limio directly from Zuora are now available in self-service, so a customer can view, update and cancel them just like a subscription bought through Limio. This journey now works end to end.

Faster processing for large orders

Order processing speed for large orders has been improved.

The Limio app is more resilient when something fails

If part of a page fails to load, the failure is now contained to that part. You keep your navigation and can carry on working elsewhere in the app.

Reorder items in a list prop

Where a component prop holds a list, feature rows for example, each item now has up and down arrows so you can change the order in place. Previously the only way to reorder was to delete an item and type it out again.

Strengthened platform security

Following further security testing, this release adds stronger protection against automated abuse, tightens the checks on who can change a subscription, and hardens how redirects are handled.

Improved platform monitoring

We have improved monitoring across the Limio platform, so we can identify and resolve issues faster.

Bug Fixes

Address errors name the right field

When a shopper left the state or city field empty at checkout, they saw a generic error rather than the name of the field. The message now uses the right word for the country, so it reads "State is required" in the United States and "Province is required" in Canada.

Refactors and cleanup

Legacy render and asset services removed

The renderShop, getAssets and odata services have been removed, along with the routes /page/shop, /assets, /assets/render, /page/render and /odata (and any path beneath it). These are legacy server-side rendering and asset endpoints from before the current shop, and have no modern equivalent — pages and assets are served through the shop itself.

Custom form endpoint removed

postCustomForm and the email and render chain behind it have been removed, along with the /custom-form route.

Page Builder V1 and V3 removed

Page Builder V2 is now the default and the only version. V1 and V3 have been removed. Page Builder V1 has been deprecated since Release 107.

Offers and Campaigns V1 removed

The V1 Offers and Campaigns screens have been removed. The current Offers and Campaigns screens should be used instead.

Developer keys are being retired

We are moving away from developer keys in favour of OAuth bearer tokens. The Developer Keys page has been removed from the navigation, and a developer key on its own no longer authorises changes to catalog records: a call to PUT /objects/{service}/{path_type}/{id} or POST /objects/{service}/{path_type}/{id}/related/{record_type} presented with only a key is refused.

Please remember to perform a hard refresh in your browser after upgrading your environment.

Last updated

Was this helpful?