# Data Access from UX/UI

In the context of **Data & Content Management**, **Data Access from UX/UI** refers to how application users interact with and consume data through **user interface components**.

ONEWEB simplifies this interaction by providing built‑in mechanisms that allow **UX/UI components** to access, display, and manipulate data **without requiring direct database interaction**.

This section describes how data is accessed from the UI layer using **Smart Forms** and **Pages**.

***

#### **Purpose of UX/UI‑Level Data Access**

Accessing data through UX/UI components ensures that:

* Users interact with data in a **controlled and structured manner**
* Business rules and access policies are consistently enforced
* Data remains protected from direct or unintended modification
* UI behavior stays aligned with application logic and data design

Rather than exposing raw database access, ONEWEB enforces data access through **designed interfaces**.

***

#### **Data Access Using Smart Forms**

**Smart Forms** provide a structured way to access and manipulate data at the record level.

Key characteristics include:

* Automatic data binding between form fields and entity attributes
* Support for create, read, update, and delete (CRUD) operations
* Validation, calculation, and access logic applied at form level
* Role‑ and context‑aware data access

Smart Forms are commonly used when users need to **enter or maintain transactional or master data** in a guided workflow.

***

#### **Data Access Using Pages**

**Pages** provide a more flexible approach to accessing and presenting data, especially for **custom UI layouts or advanced interactions**.

Pages can access data by:

* Integrating with Microflows or backend services
* Binding dynamic data to UI components
* Displaying lists, charts, or aggregated content
* Supporting interactive or read‑only data views

This approach is suitable for dashboards, navigation screens, or data‑driven user experiences that go beyond standard forms.

***

#### **UX/UI Data Access and Governance**

In Data & Content Management, data access through UX/UI components is governed by:

* Application‑level access rules
* Role‑based permissions
* Entity and process configuration
* Business logic enforced via Microflows or validations

This ensures that **data access from the UI remains predictable, auditable, and consistent** across the application.

***

#### **Summary**

**Data Access from UX/UI** enables users to work with application data through well‑defined interfaces rather than direct database access.

By using **Smart Forms** and **Pages**, ONEWEB allows applications to:

* Present data in meaningful and controlled ways
* Enforce access and validation rules at the UI level
* Maintain data integrity and quality
* Align user interaction with data governance policies

This UI‑driven data access model is a core component of effective **Data & Content Management** in ONEWEB applications.


---

# 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/building-apps/data-and-content-management/database-access-management/data-access-from-ux-ui.md?ask=<question>
```

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.