# Clone Order Request Item Entity for Authorize

This section explains how to **clone the Order Request Item entity** and customize it for the **Authorize role**.\
The Authorize role is responsible for **reviewing supplier information and related details** in order to make the **final approval decision** for high‑value order requests.

The Authorize entity is derived from the **Back Office Order Request Item entity**, with adjustments to field visibility and available actions so that users can review data without modifying it.

***

### Objective

By completing this section, you will learn how to:

* Clone the Back Office Order Request Item entity for Authorize usage
* Remove fields not required for authorization decisions
* Set supplier‑related fields to read‑only mode
* Remove save actions to prevent data modification
* Prepare a read‑only item review screen for final authorization

***

### 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 Back Office Order Request Item Entity

1. At **Select Existing Entity**, choose\
   `Doc Order Request Item - Back Office`.
2. At **Name of Clone Entity**, enter\
   `Doc Order Request Item - Authorize`.
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 Unused Supplier Field

1. In module **Supplier**, remove the field **Remain Order Unit**.

This field is not required for final authorization decisions.

***

### Step 5–6: Enable View Mode for Supplier Fields

1. In module **Supplier**, edit **Order Unit**:
   * Click the **pencil icon**
   * Set `viewFlag` = `Y`
   * Click **OK**
2. In module **Supplier**, edit **Back Office Remark**:
   * Click the **pencil icon**
   * Set `viewFlag` = `Y`
   * Click **OK**

These fields are displayed in read‑only mode for Authorize users.

***

### Step 7–8: Remove Save Actions

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

Authorize users should only review information and make decisions, not save or modify item data.

***

### Step 9: Save the Entity

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

The completed Authorize Order Request Item 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%252Fy3UlC6DrrzffDmLGiocV%252Fimage.png%3Falt%3Dmedia%26token%3D95a8ce43-a3c0-4f1e-918f-8eb7f4d4da5b&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=e0edeb94&#x26;sv=2" alt=""><figcaption></figcaption></figure>

***

### Summary

In this section, you have:

* Cloned the Back Office Order Request Item entity for Authorize usage
* Removed fields not needed for authorization review
* Set supplier and remark fields to read‑only mode
* Disabled all save actions
* Created a dedicated item review screen for final authorization

This entity completes the **item‑level review layer for the Authorize role** in the **Order Management App (Web)**, ensuring that authorization decisions are made based on accurate and immutable data.


---

# 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-item-entity-for-authorize.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.