# Clone Order Request Entity for Admin PO

This section explains how to **clone an Order Request entity** and customize it for the **Admin PO role**.\
Users in the Admin PO role are responsible for **reviewing approved order requests** and **performing purchase order (PO) processing**.

The Admin PO entity is created by cloning the **Authorize Order Request entity** and removing decision‑related fields and actions, since all approval steps have already been completed before this stage.

***

### Objective

By completing this section, you will learn how to:

* Clone an existing Authorize Order Request entity
* Remove decision‑related fields not required for Admin PO users
* Restrict save actions to prevent modification of approved data
* Prepare a read‑only order view for purchase order processing

***

### Step 1: Open Clone Entity

1. From the **ONEWEB App Designer** screen, click\
   **Entities > Clone Entity**.
2. The **Clone Entity** dialog opens.

***

### Step 2: Clone the Authorize Entity

1. At **Select Existing Entity**, choose\
   `Doc Order Request - Authorize`.
2. At **Name of Clone Entity**, enter\
   `Doc Order Request - Admin PO`.
3. Click **Clone**.
4. Wait until the message\
   \&#xNAN;**“Entity has been imported successfully”** appears and the\
   **Open Cloned Entity** button is displayed.

***

### Step 3: Open the Cloned Entity

1. Click **Open Cloned Entity**.
2. The cloned entity opens in edit mode.

***

### Step 4: Remove Decision Fields

1. In the **Order Request** module, locate the following fields:
   * **Decision**
   * **Decision Remark**
2. Delete both fields from the module.

These fields are no longer required, as Admin PO users only work with fully approved requests.

***

### Step 5: Remove Save Buttons

1. In the **entity button** section, delete **both SAVE buttons**.

Admin PO users should not modify request data at this stage; they only review information and proceed with purchase processing.

***

### Step 6: Save the Entity

1. Click **Save this Entity** to complete the configuration.

The completed Admin PO entity appears as shown below:

<figure><img src="https://docs.oneweb.tech/oneweb/~gitbook/image?url=https%3A%2F%2F2015371994-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FMpDjHWFRUtZ5nJcSfVXd%252Fuploads%252FS99KV3jiZpG2lQE9gcAj%252Fimage.png%3Falt%3Dmedia%26token%3Dcff8dc4f-6254-46dd-bfe8-3567615ddb94&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=8598379b&#x26;sv=2" alt=""><figcaption></figcaption></figure>

***

### Summary

In this section, you have:

* Cloned the Authorize Order Request entity for Admin PO usage
* Removed approval decision fields
* Disabled all save actions
* Prepared a read‑only order request screen for purchase order processing

This entity represents the **final stage of the Order Management App (Web)** workflow, where approved requests are reviewed and processed into purchase orders by the Admin PO role.


---

# 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/app-designer/clone-order-request-entity-for-admin-po.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.