> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/tworzenie-nowego-elementu.md).

# Creating a new item

### Creating a new application element (using a form as an example)

To create a new **form** — one of the basic elements of the application — go to the module **Library**, and then to the tab **Forms**. In the upper-right corner of the screen there is a button **Add form**, which initiates the creation process.

<figure><img src="/files/b5d97bca21fab921b220def722653d6603baef86" alt=""><figcaption><p align="center"><em><strong>Figure 1.</strong> View of the “Forms” tab in the “Library” module with the form creation button</em></p></figcaption></figure>

***

After clicking the button, a window will open where you need to fill in the basic data:

* **Form name** — in line with the naming convention (more in: [*Application item naming conventions*](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/konwencje-nazewnicze-elementow-aplikacji.md)),
* **Repository location** — the place where the form will be saved,
* **Number of columns** — set by default to 16; you can change it (more in: [Page editing](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/edycja-stron.md)),
* **Description** — an optional field, helpful for documenting the form's function.

<figure><img src="/files/23d93f8abafc610b2ca3097d70635f4130203c5f" alt=""><figcaption><p align="center"><em><strong>Figure 2.</strong> Dialog window for creating a new form</em></p></figcaption></figure>

***

After confirming (button **Add form**) the editor will open with an empty form template in the tab **Steps**. **Request** (1), and saving the form to the repository — by clicking the button **Save** (2).

<figure><img src="/files/73dae944a3e74aae4c3c5adeb428baee719c9fc8" alt=""><figcaption><p align="center"><em><strong>Figure 3.</strong> Editor of the newly created form in the “Application” tab</em></p></figcaption></figure>

***

The process of creating the remaining application elements (such as composite components, scripts, or validators) is similar:

1. Go to the appropriate tab in the module **Library**,
2. Click the button **Add**,
3. Fill in the configuration data,
4. Confirm and proceed to editing the new element.


---

# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/tworzenie-nowego-elementu.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.
