> 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/logika-biznesowa/scriptcode/formatery/tworzenie-i-podpiecie-formatera.md).
# Creating and attaching a formatter
## Adding a new formatter
To create a new or edit an existing formatter, go to the module **Library** and select the tab **Formatters.** A list of formatters will be displayed. From this view, you can create a new formatter, review the revision history, or edit an existing artifact.
Figure 1. Window with a list of formatters and the context menu of one of the artifacts
## Preview / Edit
After opening a specific formatter, its content will be displayed in the editor. From here, you can start editing the artifact and save its new version.
## Setting formatting for the component
### Components supporting formatting
Formatting is available for the following components:
* **Text field** (Text Field),
* **Text area** (Text Area),
* **Date** (Date picker).
### Setting a formatter for a component
The formatter can be set in the component properties view (the component must be selected first).
There are 2 properties available for the component that control the formatter's behavior (available in the section **Interactions**):
| | |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **FORMATTER** | In this field, select the appropriate formatter. |
| **Real-time formatting** | Determines whether formatting occurs after typing the next character (property enabled) or after leaving the field (property disabled). The property is disabled by default. |
Figure 3. Example of the attached formatter "duzeMaleLitery"
---
# 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/logika-biznesowa/scriptcode/formatery/tworzenie-i-podpiecie-formatera.md?ask=&goal=
```
`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.