> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/release-notes/limio-commerce-release-notes/legacy-releases/releases-notes-winter-2021.md).

# Releases Notes - Winter 2021

## Releases Notes - Winter 2021

## Limio Subscription Commerce Platform

#### Platform

* **Segmented Switch:** Switch Campaigns compatible with Segmentation (Downgrade/Upgrade). See for more details.
* **Multi-shops:** Improvements to multi-shop, including better support of different meta configuration (e.g. favicons) and integrated providers (e.g. authentication). See
* **Layouts:** New layout options for a Campaign or Page (side-panel navigation). See
* **Journeys:** New Journey conditions, including Subscription Status, Device, Query String, JSON Web Token in request-handler. See .
* **Zuora:** Automatic sync of the Zuora Product Catalog in Limio Products and Offers. See
* **Zuora:** Expanded sync of the Zuora Subscriptions in Limio Subscriptions. See
* .
* **Authentication:** Improvements and simplification to authentication handling.

#### App

* **Filters:** Simplification to Active and Archive instead of Draft/Approved/Archive.
* **Sorting:** Easier sorting of offers via arrows

#### Components

* Checkout:
  * Support of new payment options with Zuora, including ACH and Invoice, in the Single-Page-Checkout
  * Support of Zuora Tax Preview in the Single-Page-Checkout component
  * Support of Zuora Order Preview in the Single-Page-Checkout component, including for complex pricing
  * Better mobile checkout experience, including spacing between product name and offer name and visible total price in the Single-Page-Checkout component
* Nav Header & Checkout:
  * Improvement to the basket, including better persistence across the Limio Shop, design improvements and better handling of quantity.
* SwitchSubscription:
  * Allow more granular control for Switch, including mid-term changes
  * Allow for Switch to be part of Campaigns and compatible with Journeys
* Edit Address:
  * Support editing of company name within the Edit-Address Component

#### Bugs

* Remove the dependence of the Builds on the Limio indexer. This is a fix for .
* Improvement to the 'Remove reference' workflow
* Better handling when several tags are present
* Preventing the ability to create Campaign with special characters (e.g. +, &) in the name
* Allow Bulk Edit to edit checkout\_\_limio attribute when editing Offers
* Improvements to data obfuscation

## Limio for Salesforce

#### Platform

* **Gifts:** Gifts can now be purchased in bulk in Limio for Salesforce. This allows an agent to place an order of multiple gift codes in one operation, which will generate 1 code with a redeemable quantity in Limio.
* **Order Processing Errors:** Update order processing to show error messaging if the Limio Event fails
* **Subscriptions Errors:** Display defect Subscriptions with error messaging
* **Delivery Address:** US & Canada delivery validation, including 9-digit ZIP codes
* **Refactoring:** Migration from Aura to Lightning Web Components (LWC)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/release-notes/limio-commerce-release-notes/legacy-releases/releases-notes-winter-2021.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.