> 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/flow-components/formatted-value.md).

# Formatted Value

The Avonni Formatted Value component displays a single value with automatic, type-specific formatting for consistently presenting Salesforce data.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-045cfde2092b39f787a79d7bb3fe9e3fb0de4049%2Fimage%20(63).avif?alt=media" alt="" width="375"><figcaption></figcaption></figure>

***

## Overview

The Formatted Value component renders a single value in a type-specific format — text, number, date/time, phone, email, URL, badge, rich text, or lookup. It handles the formatting automatically based on the **Type** you select, so phone numbers display with separators, emails become clickable links, and badges display with color styling. Use it to display calculated, fetched, or captured data in a consistent, readable way anywhere in a flow.

{% hint style="info" %}
When utilizing the 'Get Records' flow action, lookup values are not retrieved and, therefore, cannot be displayed using Avonni Formatted Value components. As a potential solution, consider creating a formula within the object to deliver the desired value.
{% endhint %}

## Configuration

To configure it, click the component on the Flow screen. The Edit Formatted Value Component panel opens on the right with two tabs: Properties and Style. The sections below mirror the Properties tab.

### Properties

**Label** — label for the component.

**Help Text** — help text for the component. Requires **Label**.

**Variant** — changes the position of the component and label: Standard, Label Hidden, Label Inline, Label Stacked, or Label Spread. Requires **Label**.

**Type** — the type of the formatted value. The type determines the formatting of the value and which value input is used:

| Type          | When to Use                                   |
| ------------- | --------------------------------------------- |
| **Text**      | Plain text display                            |
| **Rich Text** | HTML-formatted content                        |
| **Number**    | Numeric values with optional formatting       |
| **Date**      | Date fields                                   |
| **Date Time** | Date and time fields                          |
| **Time**      | Time-only values                              |
| **Badge**     | A colored pill/chip — great for status values |
| **Email**     | Email addresses rendered as a `mailto:` link  |
| **Phone**     | Phone numbers with formatting                 |
| **URL**       | Web addresses rendered as a clickable link    |
| **Lookup**    | Display a related record's name               |

**Value** — the value to format. The available value input adapts to the selected **Type**: a date picker for Date, a date/time picker for Date Time, a number input for Number, and a text input for Badge, Email, Lookup, Phone, Rich Text, Text, Time, and URL.

Under **Type** **Number**, **Value** also takes a query instead of a typed number. Switch the field to **Query** with the menu beside it, then configure:

* **Object** and **Field**: the object queried and the field aggregated.
* **Aggregate Function**: the calculation applied. A number, currency or percent field offers **Sum**, **Average**, **Count**, **Count Distinct**, **Maximum** and **Minimum**; every other field type offers the last four only.
* **Treat Blank Value as Zero**: counts records whose field is empty as `0` instead of leaving them out of the calculation.
* **Filters**: narrow the records the aggregate covers, with the same filter editor the data components use.
* **Query Refresh Emp Channel Name**: the API name of a platform event. The aggregate is recomputed whenever an event is published on that channel, so the figure follows the data without the end user reloading the screen.

**Type Attributes** — formatting and styling options that appear based on the selected **Type**:

* **Number** — Currency Code, Currency Display As (Symbol, Code, or Name), Format Style (Decimal, Currency, Percent, or Percent Fixed), and the Maximum/Minimum Fraction, Significant, and Integer Digits.
* **Date** and **Date Time** — Day, Weekday, Month, Year, and Era. Date Time adds Hour, Minute, Second, and Hour 12.
* **Badge** — Variant (Base, Brand, Inverse, Alt Inverse, Success, Info, Error, Warning, or Offline) and an optional Avatar (shape, initials, fallback icon, size, image, and position).
* **Email** — Label (link text) and Hide Icon.
* **URL** — Label (link text), Target (Self, Blank, Parent, or Top), and Tooltip.
* **Text** — Linkify, to auto-detect and link URLs in the text.
* **Rich Text** — Disable Linkify, to stop URLs from being auto-linked.

### Label Icon

Add an icon alongside the label text.

| Setting           | What It Controls                                          |
| ----------------- | --------------------------------------------------------- |
| **Icon Name**     | Lightning icon displayed next to the label                |
| **Icon Position** | Left or Right of the label text (requires **Icon Name**)  |
| **Icon Size**     | X-Small, Small, Medium, or Large (requires **Icon Name**) |

### Value Icon

Add an icon alongside the formatted value.

| Setting           | What It Controls                                          |
| ----------------- | --------------------------------------------------------- |
| **Icon Name**     | Lightning icon displayed next to the value                |
| **Icon Position** | Left or Right of the value (requires **Icon Name**)       |
| **Icon Size**     | X-Small, Small, Medium, or Large (requires **Icon Name**) |

## Styling

The **Style** tab gives you fine-grained control over the Formatted Value's appearance. Configure it from the **Style** tab of the Edit Formatted Value panel.

{% tabs %}
{% tab title="Margin" %}
Controls the *outer* spacing around the component, creating space between it and other elements on the screen.

* **Top / Right / Bottom / Left:** Adjust the space on each side of the component.
  {% endtab %}

{% tab title="Padding" %}
Controls the *inner* spacing between the component's content and its border.

* **Top / Right / Bottom / Left:** Adjust the inner spacing on each side.
  {% endtab %}

{% tab title="Border" %}
Customizes the border surrounding the component.

* **Color:** Set the border color.
* **Size:** Adjust the border thickness.
* **Style:** Choose a border style (e.g. solid, dashed, dotted).
* **Radius:** Control the roundness of the corners.
  {% endtab %}

{% tab title="Background" %}
Sets the component's background.

* **Color:** Set the background color.
  {% endtab %}

{% tab title="Label" %}
Styles the label text.

* **Color:** Set the label text color.
* **Font Size / Font Style / Font Weight:** Control the label typography.
  {% endtab %}

{% tab title="Value" %}
Styles the value text.

* **Color:** Set the value text color.
* **Font Size / Font Style / Font Weight:** Control the value typography.
  {% endtab %}
  {% endtabs %}


---

# 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/flow-components/formatted-value.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.
