# Clone Order Request Entity for Authorize

This section explains how to **clone an Order Request entity** and customize it for the **Authorize role**.\
Users with the Authorize role are responsible for **making approval decisions** when the total order amount **exceeds a configured maximum cap**.

The Authorize entity is created by cloning the **Back Office Order Request entity** and modifying decision rules and available actions to support authorization‑level approval only.

***

### Objective

By completing this section, you will learn how to:

* Clone an existing Back Office Order Request entity
* Configure decision options specific to the Authorize role
* Remove actions that are not applicable to authorization users
* Prepare a read‑only approval entity for high‑value requests

***

### 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 Entity

1. At **Select Existing Entity**, choose\
   `Doc Order Request - Back Office`.
2. At **Name of Clone Entity**, enter\
   `Doc Order Request - 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: Update Decision Configuration for Authorize Role

1. In the **Order Request** module, locate the **Decision** field.
2. Click the **pencil icon** to edit the field configuration.
3. Update **Condition Value** to:

   ```
   category_code = 'AUTHORIZE_DECISION'
   ```
4. Click **OK**.

This ensures that only **Authorize‑level decision options** are shown to users in this role.

***

### Step 5: Remove Unused Buttons

1. In the entity button section, remove the following buttons:
   * **ADD\_CHILD**
   * **SAVE**

These actions are not required for the Authorize role, as authorization users only review and decide on existing requests.

***

### Step 6: Save the Entity

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

The completed Authorize 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%252FJ2rG0nIyhtypkQ8AzyU6%252Fimage.png%3Falt%3Dmedia%26token%3Df794cee7-a32a-4252-85f5-02de510bf9c7&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=8a03ddff&#x26;sv=2" alt=""><figcaption></figcaption></figure>

***

### Summary

In this section, you have:

* Cloned the Back Office Order Request entity for the Authorize role
* Configured Authorize‑specific decision rules
* Restricted actions to approval‑only behavior
* Prepared an entity for handling high‑value order authorization

This entity completes the **authorization layer** of the **Order Management App (Web)**, ensuring that requests exceeding the maximum cap are reviewed and approved by the appropriate authority.


---

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