> 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/changelog/whats-new-at-avonni.md).

# What's New At Avonni

Stay up to date with the latest features, improvements, and fixes across all Avonni component suites for Salesforce.

**Release Date: October 31, 2026**

{% columns %}
{% column %}

#### [Installation & Update Links](#installation-and-update)

{% endcolumn %}

{% column %}

<p align="right"><a href="https://dashboard.mailerlite.com/forms/808392/134910842135119740/share" class="button primary" data-icon="bell">Subscribe for Updates</a></p>
{% endcolumn %}
{% endcolumns %}

***

## New Components

### Chart: Choropleth Map

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

A new Choropleth Map chart type shades geographic regions by a measure, so a sales manager sees at a glance which provinces carry the most shipments. Built-in world, continent and country maps can be split down to countries or states and provinces, or you can point to your own GeoJSON or TopoJSON map by URL or by a file stored in Salesforce. Records are placed by a region name field or by latitude and longitude, with a gradient legend, tooltips, a total and optional zoom.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FrEfWKJT6oC8KxThds6ZR%2Fnovember-2026-choropleth-map-inline.png?alt=media" alt="Chart component drawn as a choropleth map of Canada, each province shaded by its number of shipments, with a gradient legend and a total."><figcaption><p>Shipments by destination province, each province shaded by its count, with a gradient legend and a total.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Chart: Word Cloud

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

A new Word Cloud chart type sizes each word by a measure, for example lead sources sized by the amount behind them. Words come from one or more fields and run horizontally or horizontally and vertically. You set the smallest and largest font size, or turn on Fit All Words so every word fits. The font family is set in the chart styles.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FKxsQvji3Zn035PtKYsBz%2Fnovember-2026-word-cloud-inline.png?alt=media" alt="Chart component drawn as a word cloud of shipping destinations, each word sized by the number of shipments behind it."><figcaption><p>Shipping destinations, each word sized by the number of shipments behind it.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Data Driven Tree Grid

<mark style="background-color:green;">**`LWC Components`**</mark>

A new data-driven Tree Grid for LWC developers shows related records as nested rows, such as accounts with their contacts, from a parent query and child queries. It can also take rows directly, each carrying its children. It supports column widths, sorting, column header actions, a total record count and a per-row count of children.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2F6Ro3FcSsJxIGGNhRxTsd%2Fnovember-2026-data-driven-tree-grid-inline.png?alt=media" alt="Tree Grid listing accounts with their opportunities nested underneath, a total number of items above the grid and the number of children printed beside each account."><figcaption><p>Accounts and their opportunities in one grid, with the total number of items and each account's number of children.</p></figcaption></figure>

***

## Improvements

### Chart: Grouped Queries

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

A chart bound to a query now lets Salesforce do the grouping and the measures, so it reads one row per group instead of every record behind it. Pages with several charts on the same data load faster. Measures Salesforce cannot compute in a query, a median for instance, still read the records. Each measure also gains a Treat Blank Value As Zero setting.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2F44uGsh4HaVN8wdN4P4ke%2Fnovember-2026-chart-blank-as-zero-inline.png?alt=media" alt="Chart measure editor in the Builder with the Treat Blank Value As Zero setting turned on." width="480"><figcaption><p>In the Builder, a chart measure with the new Treat Blank Value As Zero setting turned on: records with an empty value count as zero in the measure.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Experience Sites: Phone Layouts

<mark style="background-color:orange;">**`Experience Sites Components`**</mark>

The Application Shell theme layout has a phone mode: on a phone or tablet the left panel hides and opens as a drawer from a header toggle. The Navigation component gains Display Actions In Mobile Menu, which moves the actions slot into the open mobile menu, and its mobile menu now follows the device form factor rather than the window width.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2F7wo6RvCUffbDpCkZ21GP%2Fnovember-2026-experience-phone-layouts-inline.png?alt=media" alt="A partner portal in Experience Builder&#x27;s phone preview with the navigation menu open and the account avatar shown inside the menu."><figcaption><p>A partner portal in Experience Builder's phone preview: the account avatar leaves the header and appears inside the navigation menu.</p></figcaption></figure>

**Documentation:** [Navigation for Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-navigation)

### File Upload: Guest Uploads on Public Experience Cloud Pages

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

File Upload can now be used by guest visitors on a public Experience Cloud page. Two new properties, Guest File Field Name and Guest File Field Value, tag the uploaded file through a field instead of the record Id, which is the route Salesforce supports for guests. The documentation gives the org-side setup.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FMqHFMRP6gCkL9DxPlPOg%2Fnovember-2026-file-upload-guest-uploads-inline.png?alt=media" alt="File Upload in the Builder with the Guest File Field Name and Guest File Field Value properties set in the Properties panel."><figcaption><p>In the Builder, Guest File Field Name and Guest File Field Value tag each guest upload so a flow can link it to the right record.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/file-upload)

### Tree, Tree Grid and Relationship Graph: Record Counts

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

A Show Total Number of Items option displays how many records the hierarchy holds, every level included, counted on the server. The Tree Grid also gains Show Number of Children, which prints each row's child count beside its label.

**Documentation:** [LWC Components](https://docs.avonnicomponents.com/lwc-components/data-driven-components/tree) · [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/tree-grid) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/tree-grid) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-tree-grid)

### Refresh Query: Stay on the Current Page

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

The Refresh Query and Refresh All Queries interactions gain an Override Refresh Behavior option, with Stay on Current Page and Preserve Selected Items. Turn them on and a Data Table, List or Timeline keeps its page and its selected rows after a refresh instead of going back to page one. They are off by default, so existing components behave as before.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FDYKSdprH0I40k7gQyxHQ%2Fnovember-2026-refresh-query-stay-on-page-inline.png?alt=media" alt="Refresh Query interaction in the Builder with Override Refresh Behavior, Preserve Selected Items and Stay on Current Page turned on."><figcaption><p>A Refresh Query interaction with Override Refresh Behavior, Preserve Selected Items and Stay on Current Page turned on. All three are off by default.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/component-builder/interactions/refresh-query) · [Flow Components](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/refresh-query)

### Chart: Legend Order and Donut Labels

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

A new Item Order setting lists the legend's category labels in the order they should read; labels you leave out follow in their usual order, and Reverse Item Order is ignored when Item Order is set. Donut segments can now print their category name next to the value and percentage. Donut and funnel segments are now always drawn largest first, and Reverse Item Order reverses the legend only.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2Fut84O3J4BOkn4xtBNVqG%2Fnovember-2026-chart-legend-order-donut-labels-inline.png?alt=media" alt="Donut chart of pipeline by lead source with a legend in a set order, and each segment showing its category name and percentage."><figcaption><p>Pipeline by lead source. The legend follows the order set in Item Order, while the segments stay largest first and each one shows its category name and percentage.</p></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Record Detail and Expandable Section: Help Text

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

A section in a Record Detail custom layout can carry help text beside its label, the way Salesforce's own dialogs do. The Expandable Section takes help text too, and so does the Accordion Section in Dynamic Components.

**Documentation:** Expandable Section for [LWC Components](https://docs.avonnicomponents.com/lwc-components/core-components/expandable-section) · Record Detail for [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/record-detail) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/record-detail) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-record-detail)

### Record Detail: Undo and Redo in the Custom Layout Dialog

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

The Custom Layout dialog of the Record Detail now has undo and redo, from its toolbar or with Ctrl or Cmd+Z and Ctrl or Cmd+Shift+Z, so a layout can be rearranged without the risk of losing work.

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/record-detail) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-record-detail)

### Menus and Popovers: Placement That Follows the Screen

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

Button menus, button popovers, the filter menu, the combobox and the color picker treat their alignment as a preferred side and flip to the other side when there is not enough room. The pointer follows the side the menu opened on and is centered under icon buttons. One default changed: the Button Icon Popover now opens to the right.

### Open Quick Action: Global Actions and a Clearer Setup

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

An action name with no object prefix now resolves to a global action when no Source Entity is set. The picker separates object and global actions, shows each action's API name and no longer lists Chatter actions. Prefilled values are now labeled for Send Email, the only action that accepts them, and the Record Id requirement is spelled out.

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/component-builder/interactions/open-quick-action) · [Flow Components](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/open-quick-action)

### Scheduler and Calendar: Dates in the User's Locale

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

Dates and times in the Scheduler and Calendar headers, popovers, agenda ranges and toolbars now follow the running user's locale for order and punctuation instead of a fixed US format. A custom header pattern you write is kept exactly as written.

**Documentation:** Scheduler for [LWC Components](https://docs.avonnicomponents.com/lwc-components/data-driven-components/scheduler) · Calendar for [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/calendar) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/calendar) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-calendar)

### Pills: Error State

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

A pill can now be marked as in error with a new Has Error option, matching the standard Salesforce pill, so an invalid entry stands out.

**Documentation:** [LWC Components](https://docs.avonnicomponents.com/lwc-components/core-components/pill-container) · [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/pill-container) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/pill-container)

### Queries: The Running User's Permissions

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

Component queries now run with the viewing user's own object, field and sharing access; a request from the browser can no longer ask for system mode. Flow screen components keep their Query System Mode setting, which still works as configured. No query can read a custom setting, including the package's own protected settings.

### Dynamic Components: A Lighter First Load

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

When several formulas read fields of the page record, the component now describes that object once and shares it, instead of sending the same request once per formula before the first answer arrives.

### Component Builder: Preview While Saving and Clearer Pickers

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

Preview stays available while a component saves. The fields where a resource makes no sense, the time periods of a calendar heatmap and the words of a word cloud, no longer offer the resources submenu. And the builder now warns that a Repeater's current record cannot be used in a query filter.

**Documentation:** Repeater for [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/repeater)

### LWC Components: Upgrade From 1.11.x

<mark style="background-color:green;">**`LWC Components`**</mark>

An org on LWC Components 1.11.x or earlier can now upgrade straight to 1.14.0. The install of 1.12.0 and 1.13.0 over 1.11.x was refused because of a removed Data Table property; that property is restored. Fresh installs were never affected.

***

## Bug Fixes

### Charts

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

* **Dark mode**: charts take their text, axis and legend colors from the theme.
* **Tooltips**: on small charts the tooltip opens on the side that has room.
* **Funnel**: a funnel measured by a count of records draws its bands again.
* **Measures**: the builders offer First and Last only on number fields.

### Data Table

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

* **Excel export**: export works again when a column has an empty or missing label.
* **Export dialog**: the Export dialog on Experience Cloud sites follows Avonni theming.
* **Totals**: Summarize By totals and group subtotals refresh after an inline save or a Refresh Query (Dynamic Components).
* **Default filters**: default filters name their field by its label.
* **Slider column**: a slider column can hide its min and max labels.
* **Color picker column**: a color picker column with an invalid label no longer errors in the builder.
* **Large tables**: tables with avatar or progress bar columns appear far faster, because the per-cell checks that made a thousand-row table take seconds to show its first row are gone.

### Scheduler

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

* **Missing resources**: a real resource is no longer mistaken for the unassigned placeholder and replaced by an Empty row with its events.
* **All-day events**: in the timeline, an all-day event on the first visible day is drawn when the time frames start after midnight.

### Filter Menu, List, Map, Combobox, Pills and Pagination

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:orange;">**`Experience Sites Components`**</mark>

* **Filter Menu**: panel and popover layouts keep earlier selections when you search.
* **List**: dragging several Ctrl or Cmd selected items keeps their order.
* **Map**: a Leaflet map with no options renders.
* **Combobox**: a combobox preset to a record Id shows the record's label.
* **Pagination**: paging through queries with large fields no longer fails.
* **Pills**: pill avatars are round and placed as in SLDS 2.

### Color Picker

<mark style="background-color:green;">**`LWC Components`**</mark> | <mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

* **Disabled and read-only**: a disabled or read-only color picker no longer shows its clear button, so its value cannot be deleted.

### Component Builder

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

* **Visibility rules**: the editor no longer loads forever on a global variable relationship field, groups its resources again, no longer offers queries and keeps a selected resource visible.
* **Data Mapping**: global and record variables can be mapped.
* **Folders**: a component keeps its folder after saving.
* **Names ending in digits**: names such as Map11 are no longer split in property editors.

### Dynamic Components

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

* **Hidden buttons**: buttons hidden by a formula no longer flash into view while it loads.
* **Choice Set**: a default from a variable or merge field filters queries on load.
* **Record Detail**: a Record Detail bound to a clicked Data Table row shows the saved values after Edit Selected Records.
* **Panel filters**: panel filters stay visible when their query returns nothing.
* **Repeater**: a Repeater uses its container column count on first render in an Experience site.

### AX Data Table

<mark style="background-color:orange;">**`Experience Sites Components`**</mark>

* **Badge colors**: a badge column whose background color is mapped to a field now takes that color on the canvas and on the site.

### CSV Parser

<mark style="background-color:violet;">**`Flow Components`**</mark>

* **Parsing**: Delimiters To Guess and New Line are applied again, headers with spaces map to their field automatically, and the row count reads correctly.

### Tree

<mark style="background-color:violet;">**`Flow Components`**</mark>

* **No Results Message**: in the Flow Tree editor, the section no longer appears under every nested Child Items level.

***

## Installation & Update

{% hint style="danger" %}
**Important**

Because each release can introduce important architectural or behavioral changes, **we strongly recommend first installing it in a sandbox environment to validate** the updates and confirm that all your existing processes still work as expected before deploying to production
{% endhint %}

#### **⭐ Avonni Experience Components (recommended)**

The full bundle is available on AppExchange. Use this if you're installing Avonni for the first time or want all components in a single package.

<table><thead><tr><th width="213.56597900390625">Detail</th><th>Value</th></tr></thead><tbody><tr><td><strong>Includes</strong></td><td>Dynamic Components, Experience Sites Components, App Builder Components</td></tr><tr><td><strong>Namespace</strong></td><td><code>avxp</code></td></tr><tr><td><strong>Version</strong></td><td><strong>v1.30</strong></td></tr><tr><td><strong>Install in Sandbox</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1LpYAK"><strong>Install →</strong></a></td></tr><tr><td><strong>Install in Production</strong></td><td><a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1LpYAK"><strong>Install →</strong></a></td></tr></tbody></table>

***

#### **Flow Screen Components**

Standalone package for Salesforce Flow Builder. Install this if you build screen flows and want Avonni's flow-specific components.

| Detail                    | Value                                                                                              |
| ------------------------- | -------------------------------------------------------------------------------------------------- |
| **Includes**              | Flow Screen Components                                                                             |
| **Version**               | **v6.35**                                                                                          |
| **Install in Sandbox**    | [**Install →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000rN89AAE)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000rN89AAE) |

***

#### **LWC Components**

Standalone package with the Avonni base component library for developers building custom Lightning Web Components.

| Detail                    | Value                                                                                              |
| ------------------------- | -------------------------------------------------------------------------------------------------- |
| **Includes**              | LWC Components                                                                                     |
| **Version**               | **v1.14**                                                                                          |
| **Install in Sandbox**    | [**Install →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1IbYAK)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1IbYAK) |

***

#### **Legacy Packages**

For existing customers using one of the older standalone packages. **Not available on AppExchange.** If you're starting fresh, install Avonni Components (the bundle above) instead.

<table><thead><tr><th>Package</th><th width="142.77691650390625">Namespace</th><th>Version</th><th>Install</th></tr></thead><tbody><tr><td>Dynamic Components (standalone)</td><td><code>avdynamic</code></td><td><strong>v1.57</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1KDYA0"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000I1KDYA0"><strong>Production</strong></a></td></tr><tr><td>Experience Sites Components (standalone)</td><td><code>avcmpbuilder</code></td><td>n/a</td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000UhFdAAK&#x26;isdtp=p1"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000UhFdAAK&#x26;isdtp=p1"><strong>Production</strong></a></td></tr></tbody></table>


---

# 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/changelog/whats-new-at-avonni.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.