> 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/setting-up/add-ons-config/add-ons-display-types.md).

# Display Types

**LFS version:** requires Limio for Salesforce v12.20 or later

### Overview

Before a user can select an add-on, they are required to choose a type of add-on from a dropdown menu. In certain cases, only certain types of add-ons are relevant for specific journeys. Additionally, if a user always wants to select an add-on of one specific type, they should have the option to skip the selection step altogether. This new feature enables users to easily and efficiently define the desired add-on types in the flow builder to enhance their Limio for Salesforce experience.

This change applies to all flows where the add-ons selection is available (i.e. Limio Acquisition Flow and Credit Memo subflow of the Limio Manage Subscriptions Flow).

### Limio Acquisition Flow

In the **Selected Offers Screen**, click on the **Limio Selected Offers Table**, and find a new property **Input: Comma-separated list of add-on types to display.**<br>

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

### Credit Memo Subflow

In the **Credit Memo Screen**, click on the **Limio Order - Credit Memo** component and find the same new property **Input:** **Comma-separated list of add-on types to display.**<br>

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

This input property allows you to specify the types of add-ons that the agent will see in the dropdown when they open the modal to select an add-on:

* If left blank, all existing types will be loaded and displayed in the dropdown.
* If populated with only **1** type, the dropdown will be skipped and the user will immediately see the list of add-ons of that specific type.
* If populated with 2 or more add-on types, the user will see a dropdown with only those types to choose from.

### Format

Comma-separated list of type values:<br>

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


---

# 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/setting-up/add-ons-config/add-ons-display-types.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.