# Clone Leave Request Requester Entity

This section explains how to **clone the Leave Request entity** and customize it for the **Requester / Supervisor (PM) role**.\
The cloned entity is used by PM to **authorize leave requests** while restricting access to fields that are not relevant to their role.

***

### Objective

By completing this section, you will learn how to:

* Clone an existing Leave Request entity
* Customize field behavior for PM authorization
* Disable or set fields to read‑only based on role
* Prepare a role‑specific screen for Process Designer integration

***

### Step 1: Clone Leave Request Entity

1. From **ONEWEB App Designer**, go to\
   **Entities > Clone Entity**
2. In **Select Existing Entity**, choose

   ```
   Doc Leave Request
   ```
3. Set **Name of Clone Entity** to

   ```
   Doc Leave Request Requester
   ```
4. Click **Clone**
5. When the success message appears, click **Open Cloned Entity**
6. In the Search Entities popup, click the **Pencil icon** to edit the cloned entity

**Clone Entity Screen**

<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%252FySgfvL36yxiGbvP103ex%252Fimage.png%3Falt%3Dmedia%26token%3D7c3bdbd3-7156-4637-904f-d2f52e4b0e60&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=da6bb35f&#x26;sv=2" alt=""><figcaption></figcaption></figure>

**Open Cloned Entity**

<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%252FeX3HRNT91BbVnINY0ziZ%252Fimage.png%3Falt%3Dmedia%26token%3D8084b650-7835-4c68-9b3d-f0279bae25d5&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=74ddabce&#x26;sv=2" alt=""><figcaption></figcaption></figure>

***

### Step 2: Configure Supervisor / PM Decision Field

#### Field: **Supervisor / PM** (Dynamic List)

1. Go to module **Leave Request**
2. Locate Dynamic List **Supervisor/PM**
3. Click the **Pencil icon**

Configure:

* **Source tag**: `disabled`
* **onlyGuiFlag**: `Y`
* **viewFlag**: `Y`

1. Click **OK**

This allows PM users to view the field but prevents manual editing beyond the intended process action.

***

### Step 3: Configure Supervisor / PM Remark Field

#### Field: **Supervisor/PM Remark** (Text Box)

1. Click the **Pencil icon**
2. Set:
   * **Source tag**: `readonly`
3. Click **OK**

***

### Step 4: Configure One Down / Head Decision Field

#### Field: **One Down / Head** (Dynamic List)

1. Click the **Pencil icon**
2. Configure:
   * **Source tag**: `disabled`
   * **onlyGuiFlag**: `Y`
   * **viewFlag**: `Y`
3. Click **OK**

***

### Step 5: Configure One Down / Head Remark Field

#### Field: **One Down / Head Remark** (Text Box)

1. Click the **Pencil icon**
2. Set:
   * **Source tag**: `readonly`
3. Click **OK**

***

### Step 6: Configure HR Decision Field

#### Field: **HR** (Dynamic List)

1. Click the **Pencil icon**
2. Configure:
   * **Source tag**: `disabled`
   * **onlyGuiFlag**: `Y`
   * **viewFlag**: `Y`
3. Click **OK**

***

### Step 7: Configure HR Remark Field

#### Field: **HR Remark** (Text Box)

1. Click the **Pencil icon**
2. Set:
   * **Source tag**: `readonly`
3. Click **OK**

***

### Step 8: Configure Authorize Decision Field

#### Field: **Authorize** (Dynamic List)

1. Click the **Pencil icon**
2. Configure:
   * **Source tag**: `disabled`
   * **onlyGuiFlag**: `Y`
   * **viewFlag**: `Y`
3. Click **OK**

***

### Step 9: Configure Authorize Remark Field

#### Field: **Authorize Remark** (Text Box)

1. Click the **Pencil icon**
2. Set:
   * **Source tag**: `readonly`
3. Click **OK**

***

### Final Result

The completed **Doc Leave Request Requester** 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%252F5pVP5A5uou05d2OqcEpZ%252Fimage.png%3Falt%3Dmedia%26token%3D2bc6c08d-ac8c-4b75-a69a-e3af9114ebd1&#x26;width=768&#x26;dpr=1&#x26;quality=100&#x26;sign=38c568e6&#x26;sv=2" alt=""><figcaption></figcaption></figure>

***

### Summary

In this section, you have:

* Cloned the Leave Request entity successfully
* Customized the screen for PM authorization
* Disabled non‑relevant decision fields
* Set remark fields to read‑only
* Prepared the entity for workflow approval steps

This entity is now ready to be used as a **PM / Requester authorization screen** and can be linked directly to **Process Designer Human Activities** in the Leave Control workflow.


---

# 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/leave-control-app/app-designer/clone-leave-request-requester-entity.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.