# Create Leave Request Entity This section explains how to create the **Leave Request Entity** using **App Designer**.\ This entity is used by requesters to submit and manage leave requests. *** ### Step 1: Create New Entity 1. From the **App Space** screen, click **Form** 2. Enter a value in **Component Name** 3. Click **Start Design** *** ### Step 2: Configure Entity Properties 1. Click the **Pencil icon** to open **Entity Configuration**

2. Set **Tab Condition** to `Y`

3. Click **OK** *** ### Step 3: Create Main Tab – Leave Request 1. From **Tools > Tabs**, drag **2‑Layer Tab** 2. Set **Title** to `Leave Request` 3. Click **Add**

*** ### Step 4: Create Leave Request Module (1‑1) 1. From **Tools > Module**, drag **1‑1 Module**

2. Click **Pencil icon** to configure module

3. Configure: * **Module Name**: `Leave Request` * **Table Name**: `wf_service_request (T)`

4. Set **SQL Work Queue** ``` select wf_service_request.request_id, wf_service_request.requester, wf_service_request.sub_request_type from wf_service_request where wf_service_request.request_type = '04' ```

5. Click **OK** *** ### Step 5: Configure Layout 1. Click **Configuration Layout** 2. Select **2 Column** 3. Click **Accept**

*** ### Step 6: Configure REQUEST\_ID Field 1. Drag **Text Box** to first cell

2. Click **Pencil icon**

3. Configure: * Source: `readonly` * FIELD\_ID: `REQUEST_ID` * Populate ShowFieldName → `Request Id`

4. Enable Search & alignment

*** ### Step 7: Configure REQUESTER Field 1. Drag **Text Box** to table

2. Configure FIELD\_ID = `REQUEST`

*** ### Step 8: Append New Row Click **Append Row**

*** ### Step 9: Add Leave Type (Dynamic List) 1. From **Tools > Field**, drag **Dynamic List** to the first cell of the new row 2. Configure: * Table Name: `wf_ms_sub_request_type` * Column Show: `SUB_REQ_NAME` * Column Value: `SUB_REQ_TYPE_ID` * Condition Value: `request_type='04'` * FIELD\_ID: `SUB_REQUEST_TYPE` * ShowFieldName: `Leave Type` * Enable Search / Alignment Left 3. Click **OK** *** ### Step 10: Add Project Field 1. Drag **Dynamic List** to the second cell 2. Configure: * Table Name: `wf_ms_project` * Column Show: `PROJECT_NAME` * Column Value: `PROJECT_ID` * FIELD\_ID: `PROJECT` 3. Click **OK** *** ### Step 11–12: Contact Info & Request Type #### Contact / Tel * Field Type: **Text Area** * FIELD\_ID: `CONTACT_INFO` * ShowFieldName: `Contact/Tel.` #### Request Type * Field Type: **Hidden** * FIELD\_ID: `REQUEST_TYPE` * Default Value: `04` *** ### Step 13–24: Decision Fields (Supervisor → Authorize) For each decision level, add fields in order: #### Dynamic List * Table: `wf_ms_list_box` * Column Show: `DISPLAY_NAME` * Column Value: `DISPLAY_CODE` * Condition Value: * Supervisor: `CATEGORY_CODE='SUP_PM_DECISION'` * Head: `CATEGORY_CODE='HEAD_DECISION'` * HR: `CATEGORY_CODE='HR_DECISION'` * Authorize: `CATEGORY_CODE='AUTHORIZE_DECISION'` * FIELD\_ID: * `DECISION_SUP_PM` * `DECISION_HEAD` * `DECISION_HR` * `DECISION_AUTH` #### Remark (Text Box) * FIELD\_ID: * `DECISION_SUP_PM_REMARK` * `DECISION_HEAD_REMARK` * `DECISION_HR_REMARK` * `DECISION_AUTH_REMARK` *** ### Step 25: Configure Leave Request Module Key 1. Open **Leave Request Module Configuration** 2. Add Module Key: * Module Key: `REQUEST_ID` * KeyLen: `10` * Sequence: `REQUEST_ID_SEQ` 3. Click **OK** *** ### Step 26: Create “Normal Leave” Tab 1. From **Tools > Tabs**, drag **Normal Tab** 2. Title: `Normal Leave` 3. Columns: `1` 4. Click **Add** *** ### Step 27: Create Normal Leave Module (1‑Many) * Module Name: `Normal Leave` * Table Name: `wf_leave_req_item (T)` *** ### Step 28–33: Normal Leave Fields #### Hidden Fields * `LEAVE_ITEM_ID` * `REQUEST_ID` #### Leave Item Fields * **Leave Type** (List Box) * Values: Errand / Sick / Vacation / Other * **Specify** (Text Box) * **Start Date** (Calendar) * **End Date** (Calendar) *** ### Step 34–39: Normal Leave Module Buttons Add Module Buttons: | Button | Page Action | Button Action | | ------ | ----------- | -------------------------------------------------- | | Add | SUB\_SEARCH | popupActionFlow('\[MODULE\_ID]') | | Delete | SUB\_SEARCH | \[MODULE\_ID]Delete() | | Save | INSERT | actionFormSubmit('insertMany','Y') | | Save | UPDATE | actionFormSubmit('insertMany','Y') | | Cancel | INSERT | $('#many\_\[MODULE\_ID]\_dialog').dialog('close'); | | Cancel | UPDATE | $('#many\_\[MODULE\_ID]\_dialog').dialog('close'); | *** ### Step 40: Normal Leave Module Keys * Parent Key: `REQUEST_ID` * Item Key: * `LEAVE_ITEM_ID` * Sequence: `LEAVE_ITEM_ID_SEQ` *** ### Step 41–54: Replacement Leave Tab & Module #### Tab * Title: `Replacement Leave` #### Module * Module Name: `Replacement Leave` * Table: `wf_leave_req_item (T)` #### Fields * Hidden: `LEAVE_ITEM_ID`, `REQUEST_ID` * Calendar: `WORK_DATE` * Text Box: `RW_NO` * Calendar: `START_DATE` (Leave Date) #### Module Buttons (Same pattern as Normal Leave) #### Module Keys * Item Key: `LEAVE_ITEM_ID` * Parent Key: `REQUEST_ID` *** ### Step 55–61: Entity Buttons (Leave Request) Add **Entity Buttons** under Leave Request tab: | Button | Page Action | Button Action | | ------ | -------------- | -------------- | | Add | ENTITY\_SEARCH | addEntity() | | Delete | ENTITY\_UPDATE | deleteEntity() | | Cancel | ENTITY\_INSERT | cancelEntity() | | Cancel | ENTITY\_UPDATE | cancelEntity() | | Save | ENTITY\_INSERT | saveEntity() | | Save | ENTITY\_UPDATE | saveEntity() | | Search | ENTITY\_SEARCH | searchResult() | *** ### Final Result (Overview) The completed Leave Request Entity screen will look like the following:

*** ### Summary In this section, you have: * Created the Leave Request entity * Configured module, layout, and fields * Enabled search and read‑only behavior * Prepared the entity for Normal Leave and Replacement Leave tabs --- # 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/leave-control-app/app-designer/create-leave-request-entity.md?ask= ``` 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.