# Order Management App (Web)

The **Order Management App (Web)** is a sample ONEWEB application designed to demonstrate how an organization can manage **order requests for electronic equipment** through an automated, end‑to‑end process.

This application showcases how ONEWEB can be used to orchestrate **request submission, approval workflows, supplier processing, and purchase execution**, all within a single web‑based solution.

By automating the entire lifecycle of an order request, the application reduces manual effort, minimizes errors, and ensures consistency in the order management process.

***

### Purpose of the Tutorial

The Order Management App tutorial is intended to help users understand how to:

* Build a **web‑based enterprise application** using ONEWEB
* Design **end‑to‑end business workflows** with approval and decision logic
* Integrate backend logic with user‑driven actions
* Combine **human activities** and **automated tasks** in a single process
* Manage order data through structured forms and search interfaces

This example represents a **real‑world enterprise scenario** commonly found in internal procurement or IT request systems.

***

### Application Workflow Overview

In the Order Management App:

1. A user submits a request for electronic equipment
2. The request enters an approval workflow
3. Approvers review and approve or reject the request
4. Approved requests proceed to supplier processing
5. The system completes the purchase process

Most steps are handled automatically by the platform, with human interaction only where required.

***

### ONEWEB Features Demonstrated

The Order Management App tutorial uses key capabilities from both **Process Designer** and **App Designer**.

***

#### Process Designer

The following Process Designer elements are used to model the workflow:

* **Start / End Events**
* **Database Activity** – for data persistence and retrieval
* **Java Activity** – for custom backend logic
* **Human Activity** – for approval and decision points
* **Exclusive Gateway** – for conditional routing (approve / reject paths)

These components demonstrate how complex business processes can be modeled visually and executed reliably.

***

#### App Designer

The App Designer is used to build the web UI and data interaction layers, including:

* **Normal Input Fields** – for capturing order details
* **Dynamic List Fields** – for dropdowns and selectable values
* **SQL Work Queue** – for task and request handling
* **Search with “Like” functionality** – for efficient data lookup
* **Customization options** – for adapting forms and screens to business needs

Together, these features show how data entry, search, and task handling can be seamlessly integrated with backend workflows.

***

### What You Will Learn

By following this tutorial, you will gain practical experience in:

* Creating a process‑driven web application
* Designing user‑friendly input and search forms
* Implementing approval workflows with decision logic
* Connecting UI actions to backend process execution
* Managing enterprise order lifecycles using ONEWEB

***

### Summary

The **Order Management App (Web)** tutorial demonstrates how ONEWEB can be used to build a **robust, automated, and scalable order management system**.

It highlights:

* End‑to‑end process automation
* Integration of UI, data, and workflow
* Practical usage of Process Designer and App Designer
* A realistic enterprise use case suitable for production environments

This tutorial serves as an excellent reference for users looking to build **process‑centric web applications** on the ONEWEB platform.


---

# 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/tutorials-examples/order-management-app-web.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.