# Switching to New Offers Table Design

## Overview

Limio’s new offer catalog design can be toggled by setting a `use_new_offers_table` flag. The exact setup depends on whether you are using the **latest version of the flows** or older versions created before this flag was introduced.

This article provides clear, step-by-step instructions for both scenarios.

***

## For New Flow Copies (Flows Already Support the Feature)

If you've just installed the Limio for Salesforce package, you are going to create your first copy of the flwo with customisations, the `use_new_offers_table` constant is already present in the parent flow and automatically passed to the subflows.

### ✅ Steps

1. Open the `Limio_Manage_Subscriptions` flow in **Salesforce Flow Builder**.
2. In the **Manager tab**, locate the existing **Boolean constant** named `use_new_offers_table`.
3. Set its value to:
   * `True` → Enables the new catalog design
   * `False` → Keeps the old design
4. Click **Save** and then **Activate** the flow.

✅ That’s it! The updated value will be used automatically by all subflows:

* Limio Cancel Order
* Limio Renew Order
* Limio Switch Order
* Limio Refund Order

***

## For Existing Flow Copies (Manual Setup Required)

If your flows were created before the `use_new_offers_table` flag existed, you’ll need to set it up manually. We recommend configuring it in a way that gives you centralized control from the parent flow.

### **Recommended Setup** (Control from Parent Flow)

#### 1. Configure Each of the 4 Subflows

Open each of the following flows in **Flow Builder**:

* `Limio_Cancel_Order`
* `Limio_Renew_Order`
* `Limio_Switch_Order`
* `Limio_Refund_Order`

For each subflow:

* Create a new **Boolean variable**:
  * **Name:** `use_new_offers_table`
  * **Available for Input:** ✅ (check this box)
* Locate the **Screen element** that contains the **offer catalog LWC**.
* In the LWC's input configuration:
  * **Map** the `use_new_offers_table` **variable** to the appropriate input property.

    <figure><img src="https://3950144701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxTpA9AeeNYx1ml6UpHj%2Fuploads%2F29YLed2lvJkBoB3wgUA8%2Fimage.png?alt=media&#x26;token=602ea27b-cd65-404c-a936-b39c10f694d4" alt=""><figcaption></figcaption></figure>
* Click **Save** and then **Activate** the subflow.

#### 2. Configure the Parent Flow

* Open the `Limio_Manage_Subscriptions` flow in Flow Builder.
* In the **Manager tab**, create a new **Boolean constant**:
  * **Name:** `use_new_offers_table`
  * **Value:** `True` (to enable the new catalog design)
* In each of the 4 subflow elements:
  * Pass the constant `use_new_offers_table` into the matching input variable you just created in each subflow.

    <figure><img src="https://3950144701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxTpA9AeeNYx1ml6UpHj%2Fuploads%2FTsyz5SJyWCONrxARJAI7%2Fimage.png?alt=media&#x26;token=dbfce452-17bd-4a9a-aac8-140f0f368ef2" alt=""><figcaption></figcaption></figure>
* Click **Save** and then **Activate** the parent flow.

✅ You now have centralized control: change the constant once in the parent flow to affect all subflows.

### **Alternative Option**: Configure Each Subflow Directly

If you prefer not to set up variable mapping:

* Open each of the 4 subflows listed above.
* Find the **Screen element** with the Offers Table LWC.
* In the LWC input configuration:
  * Set Use new offers table? directly to `True` or `False`.

⚠️ **Warning:** This works but lacks central control. You'll need to update all four flows individually if the value changes in the future.

***

## Summary

| Scenario                                 | Setup Steps Summary                                        | Pros                             | Cons                               |
| ---------------------------------------- | ---------------------------------------------------------- | -------------------------------- | ---------------------------------- |
| **New flow setup**                       | Set value in existing constant in parent flow              | Fastest setup, consistent        | None                               |
| **Existing flows (recommended)**         | Add variable to subflows, map from constant in parent flow | Central control, scalable        | Requires one-time setup            |
| **Direct in subflows (not recommended)** | Hardcode value in each LWC                                 | Quick to test, granular roll out | Harder to maintain across subflows |

## Need Help?

If you're unsure which setup you have or encounter issues while configuring flows, contact your Salesforce dev team or <support@limio.com>.