> 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/model-danych.md).
# Data model
### What is a data model?
**Data model** in the Eximee platform is a central element that describes **the business data structure** used in the low-code application. The model serves two functions:
* a documentation function, providing unambiguous information about the source of each field's value,
* a technical function, performing the operations necessary to retrieve the value.
The data model enables modeling the data structure in a tree structure. Each tree node represents a business domain object of the application, e.g. applicant, loan, or correspondence address. Each leaf of the tree denotes one field storing a specific value.
Each model field has a defined way of obtaining its value (the so-called *"data source"*). Sources can calculate data **locally**, based on fixed default values, algorithms implemented in ScriptCode (e.g. PageService, ServiceTask, ...) and data entered manually by users (e.g. in loan application fields or in a credit analyst task). Values can also be obtained **remotely** from services via REST API.
The data described in the model is stored in many places, not necessarily in Eximee platform components. The task of the data model is to retrieve the value for each field from the indicated place at the appropriate time. It is therefore a component **coordinating data retrieval**, not just storing them.
Each low-code application has its own data model definition. There is no need to create a single, shared *"mega-model"* covering all areas of the institution. The data model exists only in **the context of the running application** and is not global for the entire platform. This means that a separate instance of the data model is created for each running application (see [Storing data in the model](/documentation/documentation-en/budowanie-aplikacji/model-danych/przechowywanie-danych-w-modelu.md))
{% hint style="info" %}
A good data model can significantly facilitate application maintenance and development. The ability to quickly verify the source of a given value is crucial when analyzing problems and when planning application enhancements. Remember to use clear names for objects and fields, specific documentation in descriptions, and to keep the model definition up to date!
{% 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych.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.