# Entity
An **Entity** in the ONEWEB platform represents a **collection of business data and transactions** related to a specific business concept.\
Entities are the **core data models** used throughout ONEWEB for Smart Forms, process flows, and application logic.
Common examples of Entities include:
* Customer
* Order
* Product
* Tax Invoice
Each Entity groups together all relevant business attributes and behaviors into a **single logical unit**.
***
### Purpose of Entity
Entities are used to:
* Define business data structures in a standardized way
* Act as the foundation for **Smart Forms**
* Support data exchange across processes and workflows
* Ensure consistency across the application
On the ONEWEB platform, **creating and defining Entities is the first step** in building any Smart Form.
***
{% hint style="info" %}
**Important**\
Before starting Smart Form configuration, you must carefully analyze and define the **scope of each business Entity**.
Poorly defined entities can lead to:
* Complex or redundant forms
* Difficult process integration
* Increased maintenance effort
In most cases, an Entity in ONEWEB maps directly to business concepts defined in **use case diagrams** or **ER diagrams**.
{% endhint %}
***
### Entities and Smart Forms
A **Smart Form** in ONEWEB can consist of:
* A **single Entity** (for simple forms), or
* **Multiple related Entities** (for complex business scenarios)
Entities can be linked together to represent real‑world relationships such as:
* One‑to‑many
* Master‑detail
* Reference relationships
This flexibility allows Smart Forms to scale with business complexity.
***
### App Designer and Entity Management
**App Designer** is the Smart Form and Entity builder in ONEWEB.\
It is available under the **DEV ZONE**, located on the top‑left corner of the **ONEWEB menu bar**.
Using App Designer, users can:
* Create new Entities
* Define business attributes
* Manage relationships between Entities
* Maintain data definitions centrally
***
### Searching for Existing Entities
App Designer also supports searching for existing Entities.
1. Open **App Designer**
2. Click the **Search** icon 
3. Enter the Entity name or keyword
This allows users to:
* Quickly locate existing Entities
* Reuse Entities across multiple Smart Forms
* Avoid duplicate data definitions
***
### Role of Entity in ONEWEB Ecosystem
Entities defined in App Designer are tightly integrated with other ONEWEB designers:
* **Page Designer** – Uses Entities as data sources for UI components
* **Process Designer** – Uses Entities to carry and manipulate process data
* **Microflow Designer** – Uses Entities for logic and integrations
This shared model ensures seamless data flow across the entire application lifecycle.
***
### Summary
The **Entity** is the foundational building block of applications in ONEWEB.
Key points:
* Represents a real‑world business concept
* Groups related business data and transactions
* Mandatory starting point for Smart Form creation
* Can be reused across forms, processes, and logic
* Managed centrally through App Designer
Well‑designed Entities lead to **cleaner Smart Forms, simpler workflows, and more maintainable applications** in ONEWEB.
---
# Agent Instructions: 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:
```
GET https://docs.onewebstack.com/oneweb-platform-th/designer-reference/app-designer/entity.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
