# Data Access from Process

In **Data & Content Management**, **Data Access from Process** refers to how application processes interact with databases in a **controlled, structured, and governed manner**.

ONEWEB provides built‑in **Database Nodes** within its **Process components (Microflows)**, allowing business logic to access and manipulate data without exposing databases directly to the user interface or external clients.

***

#### **Role of Process‑Level Data Access**

Accessing data through Processes ensures that:

* Business rules are enforced consistently
* Data access logic is centralized and reusable
* UI components remain decoupled from database operations
* Data integrity and transaction control are maintained

Processes act as an **intermediate layer** between the UI and the database.

***

#### **Database Node in Process**

Within a Microflow, ONEWEB provides a **Database Node** that can be configured to perform database operations.

The Database Node supports common database commands, such as:

* `SELECT` – retrieve data
* `INSERT` – create new records
* `UPDATE` – modify existing records
* `DELETE` – remove records

Each node can be configured with:

* Connection type
* SQL command or query
* Input parameters
* Output mapping

This enables precise control over how and when data is accessed during process execution.

***

#### **Typical Data Access Flow**

A common data access flow using Process components is:

1. A Page or Smart Form triggers a Process (Microflow)
2. The Process executes business logic
3. The **Database Node** performs the required data operation
4. The result is returned to the Process
5. The Process passes data back to the UI or to another system

This flow ensures that all database interactions pass through **defined business logic pathways**.

***

#### **Data Governance via Process Layer**

From a **Data & Content Management** perspective, using Processes for data access provides several governance benefits:

* Prevents direct database access from the UI
* Centralizes data access rules and validations
* Simplifies auditing and monitoring of data operations
* Supports transactional consistency across multiple operations

Processes help ensure that data is accessed **intentionally and predictably**.

***

#### **When to Use Data Access from Process**

Use Process‑level data access when:

* Business logic must be enforced before or after data access
* Multiple UI components share the same data logic
* Data operations involve complex rules or workflows
* Integration with external systems is required
* Transaction management and reliability are critical

This approach scales well for enterprise‑grade applications.

***

#### **Summary**

**Data Access from Process** is a core mechanism in ONEWEB for managing how data is accessed and controlled within applications.

By using **Database Nodes inside Processes**, ONEWEB enables applications to:

* Centralize data access logic
* Enforce business and governance rules
* Protect databases from direct UI access
* Maintain clean separation between data, logic, and presentation

This process‑driven approach supports robust, scalable, and well‑governed **Data & Content Management**.


---

# 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-process.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.