> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-developer/object-editors/form-editor/form-editor-parts-tab.md).

# Parts

## Overview

<div align="left"><figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2Fgit-blob-f84e914bc36be883c5559ff72b6cc07286f3ba6d%2Fform-editor-parts-tab.jpg?alt=media" alt="Parts Tab"><figcaption><p>Form Editor - Parts Tab</p></figcaption></figure></div>

The **Parts** tab of the Form Editor allows you to manage the structural parts of a form.\
Parts define vertical sections in your form layout—such as headers, footers, and body sections—that help organize content logically and visually. By adding, removing, or reordering these parts, you control how the form is divided and displayed at runtime.

## Sections

### Available Parts Panel (Left Side)

Lists all standard parts that can be added to the form. Examples include:

* **Title Header**
* **Header**
* **Footer**

Hovering over these may display tooltips with more information.

### Used By Form Panel (Right Side)

Shows the parts that are currently added to this form in their display order.\
By default, a form always contains a **Body** part.

### Control Buttons

* **Between Panels**:
  * `>>`: Moves selected parts from **Available** to **Used by form** (adds the part to the form).
  * `<<`: Removes selected parts from the form and returns them to the Available list.
* **Right Side**:
  * `up`: Moves the selected part up in the list (displayed higher on the form).
  * `down`: Moves the selected part down in the list (displayed lower on the form).

## Using the Parts Tab

<div align="left"><figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2Fgit-blob-299a305f1283430e8b5362d3095977e708f66886%2Fform-editor-parts-tab.gif?alt=media" alt="Parts Tab demo"><figcaption><p>Managing form parts in the Parts Tab</p></figcaption></figure></div>

### Adding Parts:

1. Select a part from the **Available** panel on the left (e.g., `Title Header`).
2. Click the `>>` button to move it into the **Used by form** panel.
3. The selected part will now appear on the form at runtime.

### Removing Parts:

1. Select a part from the **Used by form** panel on the right.
2. Click the `<<` button to remove it.
   * The part will move back to the **Available** list and will no longer be rendered in the form.

### Reordering Parts:

1. Select a part in the **Used by form** panel.
2. Click the `up` or `down` buttons to change the display order.
   * This determines the vertical position of the part on the rendered form.


---

# 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.servoy.com/reference/servoy-developer/object-editors/form-editor/form-editor-parts-tab.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.
