> 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/wprowadzenie/architektura-platformy/moduly-wykonawcze/eximee-forms.md).

# Eximee Forms

**Eximee Forms** This is the module responsible for handling the user interface in Eximee applications.\
It enables the design, launching, and processing of low-code forms in various business and technological contexts – from public portals to the bank's internal systems.\
This module constitutes the platform's common presentation layer and provides a consistent environment for user interaction with Eximee processes.

## Module architecture

`Eximee Forms` It is a shared implementation of the forms component, used across all usage contexts.\
It provides a unified mechanism for rendering, validation, event handling, and communication with EximeeBPMS processes and with Eximee Data Model Runtime.

### **Usage contexts (module instances)**

Each **Eximee Forms usage context** — understood as **technology channel**, a way **of embedding in the relevant application** (e.g. portal, electronic banking, mobile app) or **making it available to a given group of users** (customers, employees, partners) – may constitute **an independent deployment instance** of the module.

Depending on the architecture and customer requirements, these instances may be:

* **separate** – for the purposes of environment separation, integration, security, or scalability,
* **shared** – when one Eximee Forms module serves multiple usage contexts within a single application or infrastructure.

Typical usage contexts include:

* **Eximee Forms for Portals**
* **Eximee Forms for Electronic Banking**
* **Eximee Forms for Mobile Banking**
* **Eximee Forms for FrontOffice**
* **Eximee Forms for BackOffice**
* **Eximee Forms for Partners**

Each of these contexts is based on a common core (Eximee Forms), using the same component libraries and form logic mechanisms.

## General description

`Eximee Forms` is the rendering and form logic engine of Eximee.\
It enables no-code running of dynamic forms designed in **Form Designer**, communicating with Eximee BPMS processes and with Eximee Data Model Runtime.

## **Functionality**

* Rendering forms based on low-code application metadata.
* Support for interactive components (library of simple and complex components).
* Field validation, visibility rules, dynamic dependencies.
* Collecting data and passing it to Eximee BPMS processes.
* Handling system actions: save, submit, signature, generating summaries.
* Support for modes:
  * creating a new case (start form),
  * handling a user task (form during the process),
  * data review (readonly mode).

## **Technical features**

* Based on Web Components architecture.
* Integration with BPMS via events and component parameters.
* Two-way communication with the parent application (postMessage, JS API).
* WCAG 2.1 compliance.
* Support for multiple languages and RWD modes.
* Ability to extend with custom components.

## **Security**

* Masking of sensitive data.
* Client-side and server-side data validation.
* Antivirus scanning of attachments.
* Isolation of session and authorization contexts.

## Common functionalities

| Area                           | Description                                                                   |
| ------------------------------ | ----------------------------------------------------------------------------- |
| **Low-code forms**             | Launching forms designed in Eximee Form Designer.                             |
| **Integration with processes** | Forms are the user interface for BPMN processes (user task, start form).      |
| **RWD and UX/UI**              | Fully responsive forms, compliant with the client's Design Style Guide.       |
| **WCAG**                       | Full compliance with WCAG 2.1.                                                |
| **Business monitoring**        | Collecting data on form usage, conversion metrics, and drop-offs.             |
| **Draft copies**               | A mechanism for local or remote saving of partially completed forms.          |
| **Design Style Guide**         | Support for multiple visual themes and UI styles depending on the deployment. |
|                                |                                                                               |

## Common features and deployment parameters

* **Deployment flexibility:** each context can be a separate instance or share the environment with others.
* **Scalability:** microservices architecture, with the ability to scale instances independently.
* **Reusability:** common component and form logic libraries.
* **Security:** compliance with KNF and WCAG requirements, access control, and event auditing.
* **Customization:** ability to adapt the style and behavior to a specific customer deployment.


---

# 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/wprowadzenie/architektura-platformy/moduly-wykonawcze/eximee-forms.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.