> 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/guides/develop/application-design/forms/layout-management/abstract-form.md).

# Abstract Form

## Overview

When creating a form, one must always select a layout type. An **Abstract** (No UI) layout can be used to create a base form, from which other forms can inherit. The benefit of having a base form be Abstract, is to allow child forms to implement any UI, while still inheriting the properties and event bindings, as well as logic from the Abstract parent.

## Quick Start

When creating a form, select the form type option **Abstract** (No UI) in the [New Form Wizard](/reference/servoy-developer/object-editors/new-form-wizard.md). Then you may set form properties and event handlers, as well as implement logic to be inherited as you please.

{% hint style="info" %}
For more information on creating an Abstract Base Form see the guide on [**Form Inheritance**](/guides/develop/application-design/forms/form-inheritance.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.servoy.com/guides/develop/application-design/forms/layout-management/abstract-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.