> 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/salesforce/agent-assisted-ordering/acquisition-flow/new-selected-offers-ui.md).

# Selected Offers UI

The Limio Acquisition Journey supports a tabular format for the selected offer, also supporting inline editing.

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-2e1ba6d96e6cba160cc0970c6a74f73ba3ef7c9b%2Fimage%20(227).png?alt=media" alt=""><figcaption></figcaption></figure>

To enable this view, in the acquisitionflow, add a new **Selected Offers Table** screen right after the **Offers Screen**, and place a **Limio Selected Offers Table** there.

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-86798c0201af59752e6671ed45ffbfa159bf0bd2%2Fimage%20(228).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-213ed3366055e4f7fccbbbd113084370542ecf96%2Fimage%20(229).png?alt=media" alt=""><figcaption></figcaption></figure>

Once added, open the **Assign offers screen properties,** map:

1. `is_deliverable` => **Limio Selected Offers Table** `includes_deliverable`
2. `orderItems` => **Limio Selected Offers Table** `orderItems`\
   Create a new variable `allowedCountries`, map
3. `allowedCountries` => **Limio Selected Offers Table** `allowedCountriesList`

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-791e240fb17df28f2beef9d2ea71468f19343a92%2Fimage%20(230).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-144ca87bf3f3b9e511c5afd9ae8b11a1dcdfbd2a%2Fimage%20(231).png?alt=media" alt=""><figcaption></figcaption></figure>

Additionally, if removing the previously added flow component Order Items, perform the following steps

* Remove the **Assign orderItems** element.
* In the **Delivery Address Screen**, map `Input: Allowed Countries` => `allowedCountries`
* In the **Payment Selection Screen**, in the **Limio Order Total** component map `Input: Order Items` to the local variable `orderItems`
* In the **Zuora Payment Screen**, map
  * `Input: Allowed Countries`=> `allowedCountries`
  * `Input: Currency Code` => `offers.currencyCode`
* In the **Summary Screen**, map `Input: Order Items` to the local variable `orderItems`
* Remove the **Order Items Screen**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/salesforce/agent-assisted-ordering/acquisition-flow/new-selected-offers-ui.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.