Highlights
|
Please remember to perform a hard refresh in your browser after upgrading your environment.
New Features and Improvements
Billing frequency and term
A subscription can have a billing frequency (how often the customer is billed) that is different from a term (how long the customer is contractually obligated to the subscription). For example, you may want to have a customer pay monthly (billing frequency = every 1 month) but have their subscription for 1 year (term = 1 year).
Previously in Limio's Initial Price, the initial term was calculated from the billing frequency and the number of charges. For example, if the Initial Price was $10 per month recurring for 12 charges, this would have automatically given a term of 12 months. We have now decoupled these two concepts by introducing a new Initial Term attribute for Offers.
Screenshot: The new Initial Term attribute available on Offers.
Now, the pricing configured in the Price Editor will be used to set the billing frequency during the initial term, however the Initial Term field will determine the actual initial term.
For example, if you wanted to have a customer with an initial term of 1 year billed monthly, you would set the initial term to - Termed, external, 1 year - and you would configure the price in the price editor to be "every 1 year for 1 charge".
This feature is backwards compatible. If you do not populate the initial term field, then it will not change existing functionality (billing frequency and initial term will both be determined by the price editor). This new Initial Term will appear on your Offer templates after upgrading to this release however, so hide it it if you don't need it.
Read more about Offers and all corresponding attributes here: What are offers and how to configure them
Read more about configuring External Pricing here: How to configure Subscriptions in Limio Offers with External Price and Zuora Rate Plans
Read more about configuring Initial Pricing here: How to configure Subscriptions in Limio Offers with Initial Price and Zuora Rate Plans
Improvements to promo codes
We have made several improvements to our promo code feature. In order to align with standard practices, we have removed the ability to edit customer-facing codes, and have new validation to prevent customer-facing codes with spaces. Additionally, Limio Commerce users can navigate to the corresponding offer by clicking the Offer link.
Screenshot: Limio Commerce users can click the offer path to be redirected to the corresponding promo code offer.
New option for updating Zuora account details
Currently, when a customer updates their details in the customer table component, the Zuora billTo and soldTo attributes are updated with the customer's updated name. There is a new setting that allows Limio Commerce users to determine whether the Zuora account name should also be updated when a customer updates their details. This can be useful in B2C cases where your customer's name is the same as their account name. If you have mostly B2B cases, you will likely want to have this feature off.
This setting can be found as a toggle in Settings > Zuora > Zuora Account Name Update Settings.
If Zuora Account Name Update Settings is set to on:
- When a customer updates their details, billTo and soldTo are updated, and the Zuora account name is updated to match billTo.
If Zuora Account Name Update Settings is set to off:
- When a customer updates their details, billTo and soldTo are updated, and the Zuora account name is not modified (existing behaviour).
Screenshot: Limio Commerce users can see the new setting in Settings > General Settings > Zuora > Zuora Account Name Update Settings.
Receive notifications for webhook timeouts
Limio Commerce users can now receive email alerts when a webhook times out. To configure where to send the notification email, go to Settings > General Settings > Webhooks > Configure Webhooks, and enter email addresses in the Webhook Failure Notification section
The email will contain the webhook that has timed out, and the environment in which it is happening.
Screenshot: Webhook settings to configure failure notification email.
Read more about configuring webhooks here: Configuring Webhook timeouts
Removed 'Send report' button
The Modular Checkout previously displayed an error message on checkout failure with a button to report feedback, however this feedback wasn't tracked in a useful way. As we have Limio monitoring captured separately, this button was removed to reduce confusion.
Screenshot: The Report feedback button has been removed on checkout failure.
LTM attributes persist to Zuora regardless of order source
Limio offers an analytics solution that can be used to pass data from LTM (Limio Tracking Module) attributes in the offer to Zuora custom attributes. Previously, these LTM attributes would only persist to Zuora if the offer was posted from an online shop. We've extended this solution so that the LTM attributes will persist regardless of source, for example, if the order comes from LFS. This will remove the need to duplicate data on the client side.
Read more about our analytics solution here: How to configure Limio analytics for tracking and attribution
Access Users Settings directly
Limio Commerce users can now access the Users management tab directly, without needing to go through the Profile settings first. This makes it easier for users to find and manage user permissions.
Screenshot: Limio Commerce users can find the "Users" link when clicking their icon in the top right corner of any page.
Extend multibuy solution to support one-off charges
The Limio multibuy solution has been extended to support all quantity-based purchases for a one-off rate plan. Previously, one-off, multibuy purchases were not supported.
Enhance validation on Postal Code Subcomponent
If there is no regex specified in the "Validation regular express" prop on the Postal Code subcomponent, and the country does not have a post code rule in our metadata file, then the field will have new fallback validation to only allow letters, numbers, hyphens, and spaces.
Empty strings will only be allowed if the subcomponent is optional.
To see which countries have post code rules in our file, or read more about the Postal Code Field in general, please read here: Form subcomponent: Postal Code field
Show failed builds
Previously, if a page or campaign build failed, it would show as "Building" in the Builds view indefinitely. We have improved this view so that if a page or campaign is still building after 5 minutes, the "Building" status is replaced with a status returned from AWS. This will make the actual status of building pages and campaigns clearer.
Screenshot: An example of a Page that has a Failed build.
Include LTM and UTM attributes in Copy Live Link on Pages v2
If the Copy Live Link is clicked for a checkout in Pages v2, it now builds the URL including any LTM or UTM attributes on the Offer.
Screenshot: Copy Live Link button in Pages v2.
Show "n/a" in Payments Table for Renewal Price when subscription won't be renewed
If a subscription is a gift purchase, cancelled, or not auto-renew, the Payments Table component will now display "N/A" in the Renewal Price field.
Screenshot: Next billing date and Renewal price both display as N/A when the subscription is cancelled.
Read more about the Payments Table component here: Component: Payments Table
New prop to hide checkbox in Payments Table component
There is a new prop called "Hide agree to payment change checkbox" to hide the "I agree to save my details for future payments" checkbox in the Payments Table component. If the prop is set to false, the checkbox appears, and customers must check it before they are able to proceed (same behaviour as previously). If the prop is true, then the checkbox is hidden, and the user can still submit the change payment order.
Screenshot: There is a new prop in the Payments Table called "Hide agree to payment change checkbox".
To read more about the Payments Table component, see article: Component: Payments-Table
More control over date formatting
The date format can now be configured to show consistently across all components that show dates. Users can configure the date by navigating to Settings > Localisation > Default date format.
Dates are shown in the following components.
Read our guide for configuring this feature here: How to configure the date format in Limio Components
crm_id populated on Zuora account
When a Salesforce account is created via our Limio Salesforce v3 plugin, the crm_id will now be populated on the Zuora customer account.
Deactivate submit button immediately after press in Modular Checkout
Previously, it was possible for customers to click the Submit button in the Modular Checkout multiple times if they did so quickly. The Submit button now deactivates immediately when pressed, ensuring the customer can only submit the form once.
Invoice table to work regardless of the Zuora version
Older versions of Zuora return invoices in an array, however newer versions of Zuora return them as strings, meaning there were inconsistencies in the way the Invoice Table component displayed data. We have made the amendments that enable the Invoice Table to work consistently, regardless of what Zuora version is used.
Read more about the Invoice Table component here: Components: Invoices Table
Improve readability of downloaded invoices
When an invoice is downloaded from the Invoice Table component, the file name will now display as "INVxxx.pdf" where xxx is the invoice number from Zuora.
Read more about the Invoice Table component here: Component: Invoices Table
Support for Sass style sheets
Limio now supports the use of Sass style sheets in the design system.
Internal improvements of component functions
We've improved the functions used by some of our components (customer orders, orders change table, orders confirmation, orders table, subscription description, subscription info). This is to ensure consistency in terms and pricing.
Remove sync-events job
The sync-events job type has been removed from Operations > Jobs as its no longer in use.
Bug Fixes
Don't allow templates with duplicate attribute names or attribute option values
There is new logic to prevent Limio Commerce users from saving a Template if it has more than one attribute with the same name. There has also been logic added to restrict users from saving the Template if attribute options (eg picklist options) have the same value.
(ZD ticket #3567)
Remove billing address from Payment Details subcomponent when invoice is payment method
Previously, the Payment Details subcomponent in the modular checkout would display billing address fields to the customer when invoice was selected. Customers are no longer prompted to fill out address information when selecting invoice as a payment method. Instead, address information can be captured using the Address Fields subcomponent.
1 - n subs settings doesn't allow for different payment methods
Limio offers a configuration where new subscriptions for an existing Zuora account gets created under that Zuora account, instead of creating a new Zuora account. If you are interested in configuring this feature, please contact support@limio.com. Previously, when this setting was configured, the checkout would fail if the customer selected a different payment method than the original subscription. This has been fixed so that customers can use a different payment method to purchase additional subscriptions.
Errors when filters are applied in Process Events view
Previously, if a user navigated to Subscriptions > Events > Process Events and applied a filter, the page would break, saying "An error occurred". This has been fixed so users can now filter process events again. This bug only affected Release 91.
Rich text props do not persist in Page Builder v2
Rich text props on components would appear as blank through the Page Builder v2 view even though they were populated from the Shop view. This bug is now fixed.
Times and dates inconsistent across timezones
The date field was displaying inconsistently across Limio self service components, Zuora, and LFS due to timezone issues. This has been resolved.
Autofilled fields do not get added to order payload in Modular Checkout
If autofill (eg a service like Dashlane) is used in the Modular Checkout, those fields will not get added to the order payload, causing the order to fail. This issue has been resolved.
Comments
0 comments
Please sign in to leave a comment.