Limio Release Notes - Release 91

Highlights

- New features: - B2C/B2B Commerce: New add-ons concept - Faster time to market: improved UX of journeys, enhancements to offer labels - Omnichannel: Agents can initiate in Limio for Salesforce a purchase and allow the customer to complete the checkout online with controls - Seamless synchronisation: Improvements to Limio Salesforce order plugin, improvements to external integrations framework, SDK and webhooks improvements - Frictionless checkout: Improved Fields in checkout

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

New Features and Improvements

New Feature: Add-Ons

Limio has introduced a new concept called ‘Add-Ons’ which allows much more flexibility to marketers when configuring offers.

The concept of Add-ons is to give users the ability to add additional charges to an existing offer. Want to add a recurring delivery fee to a print offer? How about a lifetime discount so that a user gets 10% off a product for every charge? You can even add perks such as premium access or family plans. For B2B business, you can sell add-on on top of a base plan, for example an AI bot on top of your Silver plan. Add-ons supports co-terming, i.e. adding new product and pricing within an existing subscription.

Here’s an example of how Add-ons might look for you:

Add-ons leverages the same Zuora Catalog Product and Rate Plans, allowing for seamless integration with Limio’s Shop and Self-Service. In this release, Custom Components can now access add-ons data via the Limio SDK. This feature is also available in Limio for Salesforce as of version 12.09. Further functionality for add-ons in Limio Commerce will become available in new releases.

Read more at

Improvements to Limio Salesforce order plugin

We've upgraded the Limio Salesforce plugin for seamless integration with unauthenticated purchase processes. This ensures consistent data across Limio, Zuora, and Salesforce. Now, Limio Commerce can effortlessly locate or create Salesforce Accounts and Contacts (or Person Accounts) during order provisioning, maintaining data accuracy in your Salesforce data. This does not rely on Salesforce Identifier being in the JWT token. You can then use to enhance your Salesforce data, such as filling out Opportunity records.

Please contact if you are interested in using this feature.

Allow multi-select for all condition types in Journeys

We know that users want to create the least number of conditions possible for a journey, since that means faster velocity to complete tasks and faster time-to-market. This new feature allows users to select multiple values for all condition types in Limio Journeys, drastically reducing the volume of journeys, especially for our users with more complex journeys. Some example use cases that would benefit from this feature include:

• Creating a journey using multiple regions that will route customers to a special cancellation page for customers from states that require online subscription cancellation

• Creating a journey that routes customers to certain switch pages based on segment

Improved offer label selection

We have made some changes that improve the experience for selecting offer labels throughout the Limio Commerce application. Offer labels are now alphabetised and searchable in the Offers tab, Campaigns tab (Attached Offers), and throughout Pages v2 views.

Screenshot: One of the places this new functionality was added is in the Offer Creation wizard.

Set basket session length via API

As part of our effort towards supporting more omnichannel experiences, we have introduced functionality to add a session expiry to baskets in Limio for Salesforce. This will allow users to determine how long they want the basket session to be active for before it expires. The default is 2 weeks after the session was requested.

This functionality also interfaces with Limio for Salesforce, which you can read more about here:

Read the API documentation here:

New initiate_source attribute

As part of our ongoing work to build out better omnichannel experiences, we've added a new attribute called initiated_source to new and renew orders.

This field is used to determine where the basket was initiated. It can be used along with the source attribute to better track omnichannel orders. For example:

1. If a basket is initiated in Limio for Salesforce and the order is completed in Limio for Salesforce:

   • initiated_source: salesforce

   • source: salesforce

2. If a basket is initiated in Limio for Salesforce but a payment link is sent to the customer and the order is completed through the Limio Shop:

   • initiated_source: salesforce

   • source: shop

3. If a basket is initiated online through the Limio Shop and the order is completed in the Limio shop checkout:

   • initiated_source: shop

   • source: shop

4. If a basket is initiated online through the Limio Shop and the order is completed in Limio for Salesforce using the Abandoned Basket functionality:

   • initiated_source: shop

   • source: salesforce

Read about how to generate a payment link for a customer via Limio for Salesforce:

Read about the Limio for Salesforce Abandoned Basket functionality:

Configure minimum selectable day in the Date type Field subcomponent

When a Field subcomponent is configured to have a Date input type, users can now set a ‘minimum days in future’ value for the date picker. To the end customer, this becomes the minimum date that they can select in the date picker, based on the number of days from today. This can be used to set subscription start date logic, or delivery logic.

For example, if min days is set to 5, then the customer can only pick a date from 5 days after today. This gives Limio Commerce users full flexibility for when the date can be set, as there is already functionality to . The table below shows the different use cases in more detail.

Example if today is August 1st.

Min	Max	Outcome
Blank	Blank	Customer can select any date, past or future.
0	Blank	Customer can select from August 1 to any date in the future.
5	Blank	Customer can select from August 6 to any date in the future.
Blank	0	Customer can select any date until today (inclusive of today).
0	0	Customer can only select today.
Blank	5	Customer can select any day in the past until August 6 (inclusive).
0	5	Customer can select from August 1 to August 6
5	5	Customer can select August 6 only.

To read more about the date picker functionality, read here:

Improve user interface for managing external integrations

We have improved the user interface for configuring and managing external integrations. The user experience is much more intuitive now, with clearer buttons and directions for what to do. Limio commerce users can see this new interface when adding any external integration to their shop by navigating to Developer > Integrations > Add integrations or Developer > Authentication Providers > Add integrations.

Screenshot: For example, the Add and Delete buttons in Developers > Integrations > Add integrations > Datatrans have been updated to be more intuitive.

Integrate with HUP to fetch edition and deliverability

Limio has added an integration with HUP, an API provider specialising in Swiss addresses, to enrich the metadata we can capture for Swiss-specific addresses. Thanks to our integration with HUP we can feed in a Swiss address through one of the Limio checkouts and return fields such as deliverability and edition. Please contact if you are interested in using this feature.

Limio SDK Improvements

We have made some amendments to the Limio SDK to reduce complexity. The specific changes made are:

• Removed useLimio. This is replaced with useLimioContext which returns the build time pageContext and isInPageBuilder.

• Added useLimioPageContext. This is the build context returned as pageContext.

• Added useCampaign. Returns the campaign (name), tag, offers and groupValues

• Moved useOfferGroups, useOfferInfo into @limio/sdk.

• Change signature of addToBasket to be consistent.

These changes could affect your custom components. Please check if your custom components are using useLimio, and reach out to if you have any questions.

Webhook timeout configuration

Limio Commerce users can now define a webhook timeout in milliseconds on the webhooks settings page (Settings > General Settings > Webhooks). If nothing is defined, it defaults to 2000 milliseconds.

Screenshot: A view of the new webhook timeout setting.

Filter cancelled schedules out of the Subscription view

Previously, the the schedules table in a subscription showed all schedules, even cancelled ones. In order to improve the user experience and make things clearer to users, cancelled schedules will no longer be displayed.

Screenshot: Subscription view with the schedules table only showing non-cancelled schedules.

Bug Fixes

US and Canada gift orders fail if no address 1 is collected in modular checkout

Previously, if a gift was purchased in a modular checkout that didn't collect address line 1 and the country was US or Canada, the order would fail. This has been fixed so that address line 1 is not a requirement to purchase a gift. This issue affects Release 88, 89, and 90.

Incorrectly sized loading spinner

We've adjusted design elements to maintain a consistent appearance using a relative height of "1em" and relocated our configuration source for improved code consistency across the application. This issue affects Release 89 and 90.

Cannot perform switch on a renew to evergreen sub in Limio for Salesforce

Improved subscription preview process by calling the appropriate Zuora Order Action "RenewSubscription" for renewing to evergreen subscriptions, enhancing accuracy and consistency in such scenarios while ensuring it is only added in specific switch occurrences.

Fix debit memo custom field sync

The problem of custom fields not syncing correctly in Zuora debit memos has been resolved by refactoring the code to define field types only once, making order irrelevant, and adding both types and tests for improved functionality.

Country input doesn't use the required/optional label defined in form props

Previously, the "Required" label on the country field in the Address Fields subcomponent was using a hardcoded label instead of the configurable Required/Optional labels. This has been fixed so that the Country field also uses the configurable label.

Implement paging in syncS3Files (#****)

Introducing a file filtering feature in files.js allows the exclusion of files with ".limio-asset-dist" in their names during the copying process, reducing clutter and maintaining a cleaner workspace.

Preview failing in Limio for Salesforce when 'price' attribute is not well defined (****)

We will eliminate the 'total' field in the Zuora plugin and instead obtain the total price information from the offer.

Order total validation should only happen for new orders

Refund orders, which is introduced by Limio for Salesforce users and not from the offer, will be resolved by limiting the recalculation to only new and renew orders.

Timeline fails for change address event when type is billing

We removed the "type" detail from the "changeAddressEvent" in enhanced testing with new mock data and revised the delivery address logic to improve functionality.

Prevent customers with a submitted order from resubmitting the same basket ()

Some customers were able to buy the same order twice because the first order submit looked like it failed when it was actually successful. This has been fixed so customers are not able to purchase the same basket if that basked has been marked as purchased.

Some customers unable to update payment method in Payments Table component ()

There was an issue where some customers weren't able to update their payment method in the Payments Table component depending on how their state or province was populated. If the state or province was recorded as a name instead of a 2 letter code, the update would fail. This has been resolved, and we've greatly enhanced the component to validate and display missing fields to the customer more clearly.

Screenshot: The Payments Table component has been enhanced to show customers when their details need to be updated.

Standard checkout configuration not redirecting to /checkout

If an offer originally was configured with the external configuration and then the checkout was updated to the standard configuration, customers would not be routed to /checkout. This bug affected R90 and has now been fixed.

Security improvements

We've worked on improving order processing security of Limio orders.