> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing.md).

# Data processing

Get to know building blocks for application logic and other data processing features.

There are almost no limits for apps built with Heisenware. This is an overview of the most important building blocks for your application logic: 

* [Functions](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/functions.md):  To create the application logic, instead of programming, you configure functions and establish links between them. Each function is designed to perform a specific action using input arguments and provides an output result for further processing. Functions can be triggered by events. 
* [Function extensions](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/function-extensions.md) are useful tools to modify, filter or record output on the fly. You can use JSONata or plain JavaScript to express your custom modifications or filters.
* [Objects](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/objects-and-instances.md) are like smart containers that combine information (*data*) and actions (*functions*) together. They are useful if many instances of a same template (*class*) must be managed, where each instance needs to keep an isolated context (*state*).
* [Utilities](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/utilities.md): Pre-built, specific functions and objects aiding to build complex data processing logic.


---

# 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.heisenware.com/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing.md?ask=<question>&goal=<user_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.