# Process Apps: Business Process Only
**Process Apps** are applications that use ONEWEB primarily for **business process management**.\
In this design pattern, the core focus is on **workflow orchestration, task routing, and business rules**, while the user interface often serves as a supporting layer for executing and monitoring processes.
Process Apps are commonly used in scenarios where:
* Business workflows must be clearly defined and controlled
* Tasks need to be routed across users, roles, or departments
* Process visibility, auditability, and governance are critical
ONEWEB supports multiple **business process design patterns** that can be applied depending on workflow complexity and business requirements.
***
#### Design Pattern 1: Sequential Process
Use this pattern when:
* Tasks must be completed **in a strict order**
* Each task can start **only after the previous task is completed**
* The workflow follows a clear, linear progression
This is the most common and simplest process pattern, suitable for straightforward approval flows and step‑by‑step procedures.
***
#### Design Pattern 2: Parallel Process
Use this pattern when:
* Multiple activities need to run **at the same time**
* Different users or groups work on tasks **in parallel**
* The process can proceed once all (or a subset) of parallel tasks are completed
Parallel processes help reduce overall cycle time and are commonly used in review or validation workflows.
***
#### Design Pattern 3: Hybrid Process
Use this pattern when:
* The workflow requires a **combination of sequential and parallel steps**
* Some tasks must follow a strict order, while others can run concurrently
* Business logic is more complex and conditional
Hybrid processes are common in real‑world enterprise scenarios where workflows cannot be fully linear or fully parallel.
***
#### Design Pattern 4: Parent–Child Process
Use this pattern when:
* A main (parent) process must **spawn one or more sub‑processes**
* Sub‑processes can be executed independently but are still related to the parent
* Large processes need to be broken into **manageable units**
This pattern improves modularity and reusability of process definitions.
***
#### Design Pattern 5: Loop Process
Use this pattern when:
* The same activity needs to be **repeated multiple times**
* A process should continue **until a specific condition is met**
* Tasks require retry, rework, or iterative handling
Loops can be controlled by:
* Entry rules that delay the start of an activity, or
* Exit rules that determine when the process moves forward
This pattern is useful for exception handling, review cycles, or iterative approvals.
***
#### Design Guidance for Process Apps
As part of **App Design Fundamentals**, consider the following when designing Process Apps:
* Choose the **simplest pattern** that meets business requirements
* Avoid unnecessary complexity in early versions
* Combine patterns only when needed
* Design processes to be **clear, auditable, and maintainable**
ONEWEB allows process designs to evolve over time, so workflows can start simple and become more advanced as business needs grow.
---
# 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/building-apps/app-design-fundamentals/choose-your-oneweb-design-patterns/process-apps-business-process-only.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.