> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/navigation/form-overviews.md).

# Form overview header

Navigate and search through forms by using default functions in (the header of) overviews

For more info about the configuration of the overview items enter the right side bar in the App Studio - Forms and select the **tabs Properties and Overviews**.

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2Fx4DOUQjxFWrgjA9KijRH%2FImage%20Overview%20forms.png?alt=media&amp;token=0dcb2332-38ea-4ec7-9ca8-f852e052d3d3" alt=""><figcaption></figcaption></figure>

**Configuration of an form overview**

* Select **Overview** in the toolbar. Double click on the appearing overview&#x20;
* or
* Select the tab Overview - Overview fields

Drag and drop **usable fields** in the overview configuration. Add **combined headers** if you would like to add more fields (vertically) in a column.

![](https://870194474-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M_kE41Rl4pOtwKfvvQq%2F-Mfxft9oZYeLVKJMQf0H%2F-MfxgSu_5Y921fxyykAe%2FImage%20overview%20actions.png?alt=media\&token=1d612280-ae27-46f9-b16b-df660d382444)

**Styling form overview fields**

Double click on each field for styling and specific functions&#x20;

**Specific functions form overview fields**

* Column weight
* Icon
* Styling
* Footer type
* Inline edit
* Scan

**Fillters and sorting options**.

Select the tab Overview - Filter fields - Default sorting and  configure the fields on which you would like to filter and sort.

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FkKQpsZT3b5oucYCmSHNC%2FImage%20Overview%20panels%20right.png?alt=media&amp;token=22d9a30b-cc23-411e-a82f-ac6b95de56fd" alt=""><figcaption></figcaption></figure>

#### Share (Excel)

Select the tab Advanced - Sharing and selected the items you would like to share.

#### Split screen

Select the tab Overview - Split screen for the configuration of **a split screen only available on desktop**.

#### Global filtering

Select the tab Overview - Global filtering for the configuration of the top search bar.

#### Header (overview)

Select the tab Overview - Header for the configuration of the top header.

#### Cells

Select the tab Overview - Cells for the configuration of the overview cells.

**Footer**

Select the tab Overview - Footer for the configuration of the bottom footer.

#### Load more row

Select the tab Overview - Load more row for the configuration of the load more row.


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/navigation/form-overviews.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.