> 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 1. View of the “Forms” tab in the “Library” module with the form creation button

*** 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 2. Dialog window for creating a new form

*** 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 3. Editor of the newly created form in the “Application” tab

*** 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/tworzenie-nowego-elementu.md?ask=&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.