> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/build-visual-picker-items.md).

# Build Visual Picker items by hand

Build Visual Picker cards by hand in a screen flow, with a title, a description, an icon, a "Most popular" tag and a plan that can't be picked.

A support rep sets up a new customer and has to pick a support plan: Basic, Plus or Premier. A dropdown hides what each plan includes. Three cards side by side show it, flag the plan most customers take, and keep Premier visible but out of reach until a contract is signed.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FNf03Toji8WCBiMoUu6WW%2Fvisual-picker-build-visual-picker-items-result.png?alt=media" alt="Visual Picker with three support plan cards, Basic, Plus tagged Most popular and selected, and Premier greyed out"><figcaption><p>Three plans as cards: Plus is tagged and selected, Premier is locked.</p></figcaption></figure>

## Before you start

* The [Avonni Flow Screen Components](https://docs.avonnicomponents.com/flow/getting-started/installation-and-licenses-management.md) package is installed and you have its permission set.
* You have a screen flow open in Flow Builder.
* The items here are typed in by hand (the **Manual** data source). If your choices already live in Salesforce records, see [Show records as Visual Picker cards](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/show-records-as-visual-picker-cards.md) instead.

## Steps

{% stepper %}
{% step %}

### Add a Visual Picker to a screen

Open a **Screen** element and drag the Avonni **Visual Picker** onto it. Give it an API Name such as `Support_Plan_Picker`: you will use it to read the pick later.

The **Edit Visual Picker Component** panel opens with three tabs: **Properties**, **Interactions** and **Style**.
{% endstep %}

{% step %}

### Set the label and the selection type

In the **Properties** tab:

* **Label**: `Support plan`.
* **Type**: keep **Radio**. A customer has one support plan, so one pick.
* **Size**: **Large**, so each card has room for its description.
  {% endstep %}

{% step %}

### Add the three plans

Set **Data Source** to **Manual**, then add three entries to **Items**. For each one, fill in:

| Setting                | Basic                             | Plus                                       | Premier                                    |
| ---------------------- | --------------------------------- | ------------------------------------------ | ------------------------------------------ |
| **Figure Title**       | `Basic`                           | `Plus`                                     | `Premier`                                  |
| **Value**              | `basic`                           | `plus`                                     | `premier`                                  |
| **Figure Description** | `Email support on business days.` | `Phone and email support, business hours.` | `24/7 phone support and a named engineer.` |

**Figure Title** and **Figure Description** print inside the card. **Title** and **Description** print under it: leave them empty here.

**Value** is what the flow receives when the rep picks the card, not the title. Keep it short and stable: you can rename the card later without breaking a Decision that tests `plus`.
{% endstep %}

{% step %}

### Give each card an icon

Still inside each item, under **Avatar**, set **Icon Name**: `standard:entitlement` for Basic, `standard:service_contract` for Plus, `standard:reward` for Premier.

To show a picture instead of an icon, put its URL in **Image Source** and describe it in **Image Alternative Text**. When an item has both, the image wins.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FxUJE96xBVODi9t7vVEbG%2Fvisual-picker-build-visual-picker-items-item-editor.png?alt=media" alt="Visual Picker item editor for the Plus plan showing Figure Title, Value, Figure Description, Avatar icon, a Most popular tag and a Response time field" width="320"><figcaption><p>Every card setting lives in its item: title, value, icon, tags and fields.</p></figcaption></figure>
{% endstep %}

{% step %}

### Tag the plan most customers take

Open the Plus item. Under **Tags**, add one tag with **Label** `Most popular` and **Variant** **Brand**.

The tag only labels the card. It does not pre-select Plus.
{% endstep %}

{% step %}

### Keep Premier visible but locked

Open the Premier item and turn on **Disabled**. The card stays on screen, grayed out, and the rep can't pick it.

**Disabled** accepts a flow resource, so the lock can depend on data: map it to a Boolean formula resource such as `{!Get_Account.NumberOfEmployees} < 100` to open Premier only to larger accounts.
{% endstep %}

{% step %}

### Use the pick later in the flow

After the screen, the picked value is in the component's **Value** output: `{!Support_Plan_Picker.value}` holds `basic` or `plus`.

Test it in a **Decision** element (outcome **Plus** when `{!Support_Plan_Picker.value}` **Equals** `plus`), or write it to a field with **Update Records**.
{% endstep %}

{% step %}

### Save and test

Save the flow and click **Debug**. The screen shows three cards in a row: Plus carries a `Most popular` tag, Premier is grayed out. Click Plus: a check mark appears on it. Click Basic: the check mark moves. Clicking Premier does nothing.

Click **Next** and open the debug details: the Visual Picker's value is `plus` or `basic`, the **Value** you typed, not the card's title.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>The cards show an icon but no text</summary>

**Size** is **Xx-Small** or **X-Small**. At those two sizes the Visual Picker draws only the avatar and hides the titles and descriptions. **Small** is the smallest size that keeps the text.

</details>

<details>

<summary>The text sits under the cards instead of inside them</summary>

The text went into **Title** and **Description**. Move it to **Figure Title** and **Figure Description**, which print inside the card.

</details>

<details>

<summary>Every card is grayed out</summary>

**Disabled** is on in the **Properties** tab, which locks the whole picker. Turn it off there and turn on **Disabled** inside the Premier item only.

</details>

## Related tutorials

* [Show records as Visual Picker cards](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/show-records-as-visual-picker-cards.md): build the cards from Salesforce records instead of typing them.
* [Limit and pre-select Visual Picker choices](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/limit-and-preselect-visual-picker-choices.md): let the user pick several cards, within a minimum and a maximum.
* [Visual Picker](https://docs.avonnicomponents.com/flow/flow-components/visual-picker.md): every item setting, sizes, image positions and output variables.


---

# 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.avonnicomponents.com/flow/tutorials/components/visual-picker/build-visual-picker-items.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.
