> 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/integrations/setting-up-limio-for-salesforce/new-component-design/migration-guide.md).
# Using Limio Offers Table and Cart Items: Migration Guide
This guide walks you through upgrading your Salesforce Flow (`Limio_Acquisition_Journey`) by replacing the legacy components *Limio Offers Catalog* and *Limio Selected Offers* with Limio’s redesigned Lightning Web Components: **Limio Offers Table** and **Limio Cart Items**. This new architecture supports multi-offer selection, streamlined cart handling, and a faster, cleaner user experience.
## Why Upgrade?
Limio’s legacy components supported only single-offer logic or required separate screens in the flow for managing selection and cart data. The new architecture simplifies everything with a modular, responsive pair of components.
## Place Both Components on the Same Screen
> ✅ **Limio Offers Table** and **Limio Cart Items** are designed to react to one another in real-time. When a user selects or changes offers, cart outputs like currency or delivery status update instantly.
Benefits of this setup:
* Fewer clicks and screens for agents
* Faster, real-time feedback in the UI
* Easier flow design and debugging
🛠 *If needed*, you may place the components on separate screens—but this is not recommended unless driven by UX constraints.
> You can find more details about each of the components in the articles linked below:\
> 1\. [Limio Offers Table Component](/integrations/setting-up-limio-for-salesforce/new-component-design/offers-table-component.md)
## Migration Steps
1. Add a new screen above the Selected offers screen in the Acquisition flow
* Add new **Limio Offers Table** and **Limio Cart Items** to the screen
* Expand *Advanced* settings on both components and set the *Revisited Screen Values* to the second option - "Refresh inputs to incorporate changes elsewhere in the flow"
*
```
```
2. Add a new Assignment element after the new screen and populate flow properties with the outputs of the new components.
3. Remove references to the old components and replace them with the new components outputs.
* `selectedOffer` property is not relevant in the new flow context, since it supports multiple offers selection, so we recommend removing assignment of the `selectedOffer` from the screens as well.
4. Remove the old Assignment Elements and Screens.
5. Save, Debug, Activate the new flow version.
{% embed url="" %}
Need support? Reach out .
---
# 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/integrations/setting-up-limio-for-salesforce/new-component-design/migration-guide.md?ask=&goal=
```
`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.
.png)