01 — Development (Studio From Scratch)

Use HRLXProLeaveUtilsV2, HRLXProSecurityUtilsV2, and u_* columns only — not legacy LeaveRequestUtil or duration_days.

How development objects relate

Application (HR Leave)
  └── Tables: employee_v2 ←── bal_v2
                 ↑              ↑
                 └── req_v2 ────┴── audit_v2
                       │
        ┌──────────────┼──────────────┐
        ▼              ▼              ▼
  Script Includes   Business Rules   Client Scripts
  LeaveUtilsV2  ←── BR1 days/approver
                ←── BR2/BR4 events
                ←── BR3 audit/balance
  SecurityUtils ←── ACLs (ch.02)
  LeaveUtils    ←── CS2 GlideAjax
                       │
        ┌──────────────┼──────────────┐
        ▼              ▼              ▼
   UI Policy/Action   Menu/Modules   Flow Approval
   (sick / Submit)    (navigator)    (Ask For Approval)

Rule 0 — Before any object (Application + Update Set + Studio)

Repeat these checks before creating or editing any application file. This section is also section 00 Update Set — create the capture set first.

1. Application picker — top-right globe / application menu → select HR Leave (x_786686_hr_leave). Never leave Global selected when creating scoped artifacts.
2. Update Set — All → System Update Sets → Local Update Sets → New:

   Field	Value
   Name	HR Leave – Build
   Application	HR Leave
   State	In Progress
   Description	Captures all HR Leave lab artifacts

   After submit: open the record → click Make Current. Direct list: {BASE}/sys_update_set_list.do
3. Open Studio — {BASE}/$studio.do → confirm header shows HR Leave.

Part 1: Application Setup

Purpose

Creates the scoped HR Leave application container. All other OBJ artifacts belong to scope x_786686_hr_leave and app sys_id e5f5bc9493a303507520703efaba104d on the lab instance.

Navigation path

Direct URL

Prerequisites

• PDI or dev instance with admin + app_creator roles.
• Rule 0 Update Set can be created immediately after app exists.

Form fields

Step-by-step create

1. Open Studio.
2. Click Create Application.
3. Enter every field from the table. Scope must be x_786686_hr_leave.
4. Click Create. Studio opens HR Leave workspace.
5. Classic verify: Application record → Scope = x_786686_hr_leave.
6. Proceed to Rule 0 Update Set → HR Leave – Build → Make Current.

Verify checklist

• Application picker lists HR Leave.
• Scope prefix on new tables is x_786686_hr_leave_.
• Application Menu stub exists (modules added in Modules).

Demo / test

Part 2: Table — HR Employee (employee_v2)

Purpose

Stores HR employee profiles linked to platform users. BR1 reads u_manager to populate leave request approver.

Navigation path

Direct URL

Prerequisites

• Part 1: Application Setup Application HR Leave.
• Rule 0 Update Set current.

Table form fields (create the table first)

Where: Studio → Create Application File → Table · Direct: {BASE}/sys_db_object.do

Column form fields (each column New)

On Columns related list → New: set Column label, Type, Max length, Reference. Element name = code below.

Form Layout — x_786686_hr_leave_employee_v2

1. All → System Definition → Tables → open x_786686_hr_leave_employee_v2 (or Studio → Tables).
2. Related link Form Layout → New or edit default.
3. Drag fields into sections: Profile (u_user, u_employee_id, u_department, u_grade, u_join_date), Management (u_manager).
4. Save.

List Layout — x_786686_hr_leave_employee_v2

1. Same table record → related link List Layout.
2. Add columns (left to right): User, Employee ID, Department, Manager, Join Date, Grade.
3. Save → open list URL and confirm columns appear.

Step-by-step create

1. Studio → Create Application File → Table.
2. Label: HR Employee · Name: employee_v2 → full name x_786686_hr_leave_employee_v2.
3. Extends table: leave blank (standalone).
4. Submit table record.
5. For each column in the table above: Table → Columns related list → New:
   • Element = column name · Column label = friendly name · Type = as listed · Max length · Reference · Application = HR Leave.
6. Complete Form Layout and List Layout steps above.

Verify checklist

• List opens: employee_v2 list
• Dictionary: {BASE}/sys_dictionary_list.do?sysparm_query=name=x_786686_hr_leave_employee_v2^elementSTARTSWITHu_
• Six u_* columns under HR Leave application.

Demo / test

Part 3: Table — Leave Request (req_v2)

Purpose

Core leave request table. Business rules, Flow, catalog, portal, and REST all target this table.

Navigation path

Direct URL

Prerequisites

• Part 1: Application Setup Application.
• Part 2: Table employee_v2 (for u_employee_ref reference).

Table form fields (create the table first)

Where: Studio → Create Application File → Table · New table

Column form fields (each column New)

On Columns related list → New: set Column label, Type, Max length, Reference. Element name = code below.

Choice values — u_leave_type

Choice values — u_state

Form Layout — x_786686_hr_leave_req_v2

1. All → System Definition → Tables → open x_786686_hr_leave_req_v2 (or Studio → Tables).
2. Related link Form Layout → New or edit default.
3. Drag fields into sections: Request (u_number, u_requested_for_user, u_employee_ref, u_leave_type), Dates (u_start_date, u_end_date, u_days_count), Approval (u_approver_user, u_reason), Status (u_state).
4. Save.

List Layout — x_786686_hr_leave_req_v2

1. Same table record → related link List Layout.
2. Add columns (left to right): Number, Requested For, Leave Type, Start Date, End Date, Days, State, Approver.
3. Save → open list URL and confirm columns appear.

Step-by-step create

1. Studio → Create Application File → Table.
2. Label: Leave Request · Name: req_v2 → x_786686_hr_leave_req_v2.
3. Create all columns per field table. For Choice columns add values in Choice List related list.
4. Table record → Display field = u_number.
5. Dictionary: mark u_days_count read-only on form (optional dictionary flag).
6. Complete Form Layout and List Layout above.

Verify checklist

• Ten u_* columns exist.
• Choice fields show five states and three leave types.
• Reference picker on u_employee_ref shows employee_v2 rows.

Demo / test

Part 4: Table — Leave Balance (bal_v2)

Purpose

Tracks per-employee leave entitlement and usage by year and leave type. BR3 recalculates on approval.

Navigation path

Direct URL

Prerequisites

• Part 2: Table employee_v2.
• Part 20: System Properties property for default entitled days (can seed manually first).

Table form fields (create the table first)

Column form fields (each column New)

On Columns related list → New: set Column label, Type, Max length, Reference. Element name = code below.

Form Layout — x_786686_hr_leave_bal_v2

1. All → System Definition → Tables → open x_786686_hr_leave_bal_v2 (or Studio → Tables).
2. Related link Form Layout → New or edit default.
3. Drag fields into sections: Employee (u_employee_ref, u_year, u_leave_type), Balance (u_entitled, u_used, u_remaining).
4. Save.

List Layout — x_786686_hr_leave_bal_v2

1. Same table record → related link List Layout.
2. Add columns (left to right): Employee, Year, Leave Type, Entitled, Used, Remaining.
3. Save → open list URL and confirm columns appear.

Step-by-step create

1. Studio → Table → Name bal_v2.
2. Add six columns per table.
3. Reuse u_leave_type choice values from req_v2.
4. Form/List layouts per steps above.

Verify checklist

• bal_v2 list opens.
• Reference to employee_v2 works.

Demo / test

Part 5: Table — Leave Audit (audit_v2)

Purpose

Append-only audit trail for leave state changes. BR3 writes rows automatically.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.

Table form fields (create the table first)

Column form fields (each column New)

On Columns related list → New: set Column label, Type, Max length, Reference. Element name = code below.

Form Layout — x_786686_hr_leave_audit_v2

1. All → System Definition → Tables → open x_786686_hr_leave_audit_v2 (or Studio → Tables).
2. Related link Form Layout → New or edit default.
3. Drag fields into sections: Audit (u_leave_ref, u_event_type, u_old_state, u_new_state, u_actor).
4. Save.

List Layout — x_786686_hr_leave_audit_v2

1. Same table record → related link List Layout.
2. Add columns (left to right): Leave Request, Old State, New State, Event Type, Actor, Created.
3. Save → open list URL and confirm columns appear.

Step-by-step create

1. Studio → Table → audit_v2.
2. Add five columns.
3. Layouts as above.

Verify checklist

• audit_v2 list opens.
• Reference to req_v2 works.

Demo / test

Part 6: Script Include — HRLXProLeaveUtilsV2

Purpose

Server-side utility for business-day calculation, approver resolution, audit writes, balance recalc, and GlideAjax for CS2.

Navigation path

Direct URL

Prerequisites

• Part 1: Application Setup.
• Tables Table HR Employee..05 exist.

Form fields

Extends AbstractAjaxProcessor for ajaxGetBusinessDays.

Step-by-step create

1. Studio → Script Include → New.
2. Fill form fields table.
3. Paste full script below into Script field.
4. Save — fix any syntax errors.

Full script (paste-ready)

/**
 * Script Include: HRLXProLeaveUtilsV2
 * Scope: x_786686_hr_leave
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Client callable: true  (extends AbstractAjaxProcessor)
 * Purpose: Leave calculations + helpers (business days, approver, balance, audit).
 *
 * Create in ServiceNow:
 *   Studio > Create Application File > Script Include
 *   Name: HRLXProLeaveUtilsV2
 *   Client callable: checked
 */
var HRLXProLeaveUtilsV2 = Class.create();
HRLXProLeaveUtilsV2.prototype = Object.extendsObject(global.AbstractAjaxProcessor, {

    /**
     * Count business days (Mon-Fri) inclusive between two date strings.
     * @param {string} startDate - 'yyyy-MM-dd'
     * @param {string} endDate   - 'yyyy-MM-dd'
     * @return {number}
     */
    calculateBusinessDays: function (startDate, endDate) {
        if (!startDate || !endDate) return 0;
        var start = new GlideDateTime(startDate + ' 00:00:00');
        var end = new GlideDateTime(endDate + ' 00:00:00');
        if (end.before(start)) return 0;

        var days = 0;
        var cursor = new GlideDateTime(start);
        while (!cursor.after(end)) {
            var dow = cursor.getDayOfWeekLocalTime(); // 1=Mon ... 7=Sun
            if (dow >= 1 && dow <= 5) days++;
            cursor.addDaysLocalTime(1);
        }
        return days;
    },

    /**
     * Resolve the approver (employee's manager) and set it on the record.
     * @param {GlideRecord} currentRecord - leave request record
     */
    setApproverFromEmployee: function (currentRecord) {
        var empId = currentRecord.getValue('u_employee_ref');
        if (!empId) return;
        var emp = new GlideRecord('x_786686_hr_leave_employee_v2');
        if (emp.get(empId) && emp.u_manager) {
            currentRecord.u_approver_user = emp.getValue('u_manager');
        }
    },

    /**
     * Write an audit row when the state changes.
     */
    auditStateChange: function (leaveSysId, oldState, newState, eventType) {
        var a = new GlideRecord('x_786686_hr_leave_audit_v2');
        a.initialize();
        a.u_leave_ref = leaveSysId;
        a.u_old_state = oldState || '';
        a.u_new_state = newState || '';
        a.u_event_type = eventType || 'state_change';
        a.u_actor = gs.getUserID();
        a.insert();
    },

    /**
     * Recalculate remaining balance for an employee/year.
     */
    recalculateBalance: function (employeeSysId, year) {
        var used = this._sumApprovedDays(employeeSysId, year);
        var bal = new GlideRecord('x_786686_hr_leave_bal_v2');
        bal.addQuery('u_employee_ref', employeeSysId);
        bal.addQuery('u_year', year);
        bal.query();
        if (bal.next()) {
            bal.u_used = used;
            bal.u_remaining = parseInt(bal.getValue('u_entitled') || 0, 10) - used;
            bal.update();
        }
    },

    _sumApprovedDays: function (employeeSysId, year) {
        var total = 0;
        var gr = new GlideAggregate('x_786686_hr_leave_req_v2');
        gr.addQuery('u_employee_ref', employeeSysId);
        gr.addQuery('u_state', 'approved');
        gr.addQuery('u_start_date', '>=', year + '-01-01');
        gr.addQuery('u_start_date', '<=', year + '-12-31');
        gr.addAggregate('SUM', 'u_days_count');
        gr.query();
        if (gr.next()) total = parseInt(gr.getAggregate('SUM', 'u_days_count') || 0, 10);
        return total;
    },

    /**
     * GlideAjax entry point for client-side day calculation.
     */
    ajaxGetBusinessDays: function () {
        return this.calculateBusinessDays(
            this.getParameter('sysparm_start'),
            this.getParameter('sysparm_end')
        );
    },

    type: 'HRLXProLeaveUtilsV2'
});

Verify checklist

• Active record under HR Leave.
• No compile error banner.
• Background test returns 5 for Mon–Fri range.

Demo / test

var util = new x_786686_hr_leave.HRLXProLeaveUtilsV2();
gs.info('Days: ' + util.calculateBusinessDays('2026-09-01', '2026-09-05'));

Part 7: Script Include — HRLXProSecurityUtilsV2

Purpose

Centralized read/write authorization logic consumed by table ACLs on req_v2.

Navigation path

Direct URL

Prerequisites

• Part 6: Script Include (same app scope).

Form fields

Step-by-step create

1. Studio → Script Include → New.
2. Name = HRLXProSecurityUtilsV2, Client callable = false.
3. Paste script below. Save.

Full script (paste-ready)

/**
 * Script Include: HRLXProSecurityUtilsV2
 * Scope: x_786686_hr_leave
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Client callable: false
 * Purpose: Centralized security checks used by ACLs.
 *
 * Used by ACL scripts, e.g.:
 *   answer = new x_786686_hr_leave.HRLXProSecurityUtilsV2().canReadLeave(current);
 */
var HRLXProSecurityUtilsV2 = Class.create();
HRLXProSecurityUtilsV2.prototype = {

    initialize: function () {
        this.userId = gs.getUserID();
    },

    /** HR admin can do anything. */
    isHrAdmin: function () {
        return gs.hasRole('x_786686_hr_leave.hr_admin');
    },

    /** Can the current user READ this leave request? */
    canReadLeave: function (current) {
        if (this.isHrAdmin()) return true;
        // owner
        if (current.getValue('u_requested_for_user') === this.userId) return true;
        // approver / manager
        if (current.getValue('u_approver_user') === this.userId) return true;
        // manager of the employee
        return this._isManagerOfEmployee(current.getValue('u_employee_ref'));
    },

    /** Can the current user WRITE this leave request? */
    canWriteLeave: function (current) {
        if (this.isHrAdmin()) return true;
        var state = current.getValue('u_state');
        // owner can edit only while draft/submitted
        if (current.getValue('u_requested_for_user') === this.userId) {
            return (state === 'draft' || state === 'submitted');
        }
        // approver can act when submitted
        if (current.getValue('u_approver_user') === this.userId) {
            return (state === 'submitted');
        }
        return false;
    },

    _isManagerOfEmployee: function (employeeSysId) {
        if (!employeeSysId) return false;
        var emp = new GlideRecord('x_786686_hr_leave_employee_v2');
        if (emp.get(employeeSysId)) {
            return emp.getValue('u_manager') === this.userId;
        }
        return false;
    },

    type: 'HRLXProSecurityUtilsV2'
};

Verify checklist

• Record active under HR Leave.
• Used by ACLs ACL scripts.

Demo / test

Part 8: Business Rule BR1 — Calculate Days

Purpose

Calculates u_days_count and sets u_approver_user from employee manager before save.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.
• Part 6: Script Include HRLXProLeaveUtilsV2.

Form fields

Step-by-step create

1. Studio → Business Rule → New.
2. Fill every field from table. Check Advanced.
3. Paste script below into Script field.
4. Save. Confirm Active = true.

Full script (paste-ready)

/**
 * Business Rule: BR1 - Calculate Days + Approver
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * When:   before
 * Insert: true   Update: true
 * Order:  100
 *
 * Calculates u_days_count and resolves the approver before saving.
 */
(function executeRule(current, previous /*null when inserting*/) {

    var util = new x_786686_hr_leave.HRLXProLeaveUtilsV2();

    if (current.u_start_date.changes() || current.u_end_date.changes() || current.isNewRecord()) {
        current.u_days_count = util.calculateBusinessDays(
            current.getValue('u_start_date'),
            current.getValue('u_end_date')
        );
    }

    if (current.u_employee_ref.changes() || current.isNewRecord()) {
        util.setApproverFromEmployee(current);
    }

})(current, previous);

Verify checklist

• BR order: 100, 200, 250, 300.
• All Active on req_v2 under HR Leave.

Demo / test

Part 9: Business Rule BR2 — On Submit Event

Purpose

Queues submitted event when u_state becomes submitted (notifications + Flow trigger).

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.
• Part 6: Script Include HRLXProLeaveUtilsV2.

Form fields

Step-by-step create

1. Studio → Business Rule → New.
2. Fill every field from table. Check Advanced.
3. Paste script below into Script field.
4. Save. Confirm Active = true.

Full script (paste-ready)

/**
 * Business Rule: BR2 - On Submit Fire Event
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * When:   after
 * Update: true   Insert: true
 * Order:  200
 *
 * Fires an event when state becomes 'submitted' (drives notification / flow).
 */
(function executeRule(current, previous) {

    if (current.u_state.changesTo('submitted')) {
        gs.eventQueue(
            'x_786686_hr_leave.leave_v2.submitted',
            current,
            current.getValue('u_approver_user'),
            current.getValue('u_number')
        );
    }

})(current, previous);

Verify checklist

• BR order: 100, 200, 250, 300.
• All Active on req_v2 under HR Leave.

Demo / test

Part 10: Business Rule BR3 — Audit State Change

Purpose

Writes audit_v2 row on state change; recalculates balance on approval.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.
• Part 6: Script Include HRLXProLeaveUtilsV2.

Form fields

Step-by-step create

1. Studio → Business Rule → New.
2. Fill every field from table. Check Advanced.
3. Paste script below into Script field.
4. Save. Confirm Active = true.

Full script (paste-ready)

/**
 * Business Rule: BR3 - Audit State Change + Balance
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * When:   after
 * Update: true
 * Order:  300
 *
 * Writes an audit row on any state change and recalculates balance on approval.
 */
(function executeRule(current, previous) {

    if (!current.u_state.changes()) return;

    var util = new x_786686_hr_leave.HRLXProLeaveUtilsV2();
    util.auditStateChange(
        current.getUniqueValue(),
        previous ? previous.getValue('u_state') : '',
        current.getValue('u_state'),
        'state_change'
    );

    if (current.u_state.changesTo('approved') && current.u_employee_ref) {
        var year = new GlideDateTime(current.getValue('u_start_date')).getYearLocalTime();
        util.recalculateBalance(current.getValue('u_employee_ref'), year);
    }

})(current, previous);

Verify checklist

• BR order: 100, 200, 250, 300.
• All Active on req_v2 under HR Leave.

Demo / test

Part 11: Business Rule BR4 — Approve / Reject Event

Purpose

Queues approved/rejected events for notifications.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.
• Part 6: Script Include HRLXProLeaveUtilsV2.

Form fields

Step-by-step create

1. Studio → Business Rule → New.
2. Fill every field from table. Check Advanced.
3. Paste script below into Script field.
4. Save. Confirm Active = true.

Full script (paste-ready)

/**
 * Business Rule: BR4 - Fire Approved / Rejected Events
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * When:   after
 * Update: true
 * Insert: false
 * Order:  250
 *
 * Drives notifications for approved and rejected leave requests.
 * Requires events registered in Event Registry (see events.md).
 */
(function executeRule(current, previous) {

    if (current.u_state.changesTo('approved')) {
        gs.eventQueue(
            'x_786686_hr_leave.leave_v2.approved',
            current,
            current.getValue('u_requested_for_user'),
            current.getValue('u_number')
        );
    }

    if (current.u_state.changesTo('rejected')) {
        gs.eventQueue(
            'x_786686_hr_leave.leave_v2.rejected',
            current,
            current.getValue('u_requested_for_user'),
            current.getValue('u_number')
        );
    }

})(current, previous);

Verify checklist

• BR order: 100, 200, 250, 300.
• All Active on req_v2 under HR Leave.

Demo / test

Part 12: Client Script CS1 — Validate Dates

Purpose

Client-side validation: end date cannot precede start date on req_v2 form.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2 table/form.

Form fields

Step-by-step create

1. Studio → Client Script → New.
2. Fill fields. Type = onChange, Field = u_end_date.
3. Paste script. Save.

Full script (paste-ready)

/**
 * Client Script: CS1 - Validate Dates
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * Type:   onChange
 * Field:  u_end_date
 *
 * Shows an error if end date is before start date.
 */
function onChange(control, oldValue, newValue, isLoading, isTemplate) {
    if (isLoading || newValue === '') return;

    var start = g_form.getValue('u_start_date');
    var end = g_form.getValue('u_end_date');
    if (!start || !end) return;

    if (end < start) {
        g_form.showFieldMsg('u_end_date', getMessage('End date cannot be before start date'), 'error');
        g_form.clearValue('u_end_date');
    } else {
        g_form.hideFieldMsg('u_end_date', true);
    }
}

Verify checklist

• Client script list shows Active on req_v2.

Demo / test

Part 13: Client Script CS2 — Calc Days (GlideAjax)

Purpose

Calls HRLXProLeaveUtilsV2.ajaxGetBusinessDays to preview u_days_count before save.

Navigation path

Direct URL

Prerequisites

• Part 6: Script Include client-callable Script Include.
• Part 12: Client Script CS1 can share u_end_date onChange.

Form fields

Step-by-step create

1. Create Client Script after Script Include HRLXProLeaveUtilsV2.
2. onChange on u_end_date — same field as CS1 (both execute).
3. Paste script. Save.

Full script (paste-ready)

/**
 * Client Script: CS2 - Calculate Days (GlideAjax)
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Table:  x_786686_hr_leave_req_v2
 * Type:   onChange
 * Field:  u_end_date
 *
 * Calls HRLXProLeaveUtilsV2.ajaxGetBusinessDays asynchronously to fill u_days_count.
 */
function onChange(control, oldValue, newValue, isLoading, isTemplate) {
    if (isLoading || newValue === '') return;

    var start = g_form.getValue('u_start_date');
    var end = g_form.getValue('u_end_date');
    if (!start || !end || end < start) return;

    var ga = new GlideAjax('x_786686_hr_leave.HRLXProLeaveUtilsV2');
    ga.addParam('sysparm_name', 'ajaxGetBusinessDays');
    ga.addParam('sysparm_start', start);
    ga.addParam('sysparm_end', end);
    ga.getXMLAnswer(function (answer) {
        if (answer !== null && answer !== '') {
            g_form.setValue('u_days_count', answer);
        }
    });
}

Verify checklist

• Browser dev tools → Network → GlideAjax to HRLXProLeaveUtilsV2.

Demo / test

Part 14: UI Policy — Sick Requires Reason

Purpose

When leave type is sick, makes u_reason mandatory on the req_v2 form.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2 with u_leave_type and u_reason.

Form fields

UI Policy Action (related list New)

Step-by-step create

1. Application = HR Leave.
2. All → System UI → UI Policies → New.
3. Fill policy fields. Condition builder: Leave Type is sick.
4. Submit policy.
5. Related list UI Policy Actions → New → u_reason mandatory true.
6. Save action. Verify policy Active.

Verify checklist

• Leave type Sick → red asterisk on Reason.
• Annual → Reason not mandatory.

Demo / test

Part 15: UI Action — Submit

Purpose

Form button that moves draft leave requests to submitted state (triggers BR2 and Flow).

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2.
• Part 9: Business Rule BR2 BR2 for event.

Form fields

Step-by-step create

1. Studio → UI Action → New on req_v2.
2. Fill fields. Uncheck Client checkbox.
3. Paste server script below in Script field.
4. Save. Open draft req_v2 → Submit button visible.

Full script (paste-ready)

current.u_state = 'submitted';
current.update();
action.setRedirectURL(current);

Verify checklist

• Button only on draft records.
• After click state = submitted.

Demo / test

Part 24: Application Menu

Purpose

Top-level Application Navigator entry for HR Leave modules.

Navigation path

Direct URL

Prerequisites

• Part 1: Application Setup with Create application menu checked.

Form fields

Step-by-step create

1. If missing: Studio → Application Menu → New → fill fields.
2. Save. Confirm appears in Application Navigator.

Verify checklist

• Navigator shows HR Leave heading.

Demo / test

Part 25: Modules

Purpose

Four list modules linking to req_v2, employee_v2, bal_v2, audit_v2 tables.

Navigation path

Direct URL

Prerequisites

• Part 24: Application Menu menu. Tables Table HR Employee..05.

Form fields

Step-by-step create

1. Module → New for each row. Application Menu = HR Leave.
2. Type = List → Table = as listed. Order as table.
3. Roles: restrict Employees/Balances/Audit to hr_admin; Requests to all three roles.

Verify checklist

• Four modules under HR Leave menu.
• URLs x_786686_hr_leave_*_list.do open.

Demo / test

Part 27: Flow Designer — Leave Approval

Purpose

When leave state becomes submitted, sends approval to u_approver_user; on approve/reject updates u_state.

Navigation path

Direct URL

Prerequisites

• Part 3: Table req_v2 with u_state, u_approver_user.
• Part 8: Business Rule BR1 BR1 fills approver.
• manager1 user for approval tests.

Form fields — Create Flow wizard

Trigger — Record Updated

Action 1 — Ask For Approval

If Approved → Update Record

Else → Update Record

Step-by-step create

1. Flow Designer → Create Flow → Name HRLX Leave Approval, Application HR Leave.
2. Add trigger → Record Updated → table req_v2 → condition u_state is submitted + changes.
3. + → Ask for Approval → fill Action 1 table → Rules: Anyone approves → Done.
4. + → Flow Logic → If → condition "approval was Approved".
5. Yes branch → Update Record → u_state = approved.
6. Else branch → Update Record → u_state = rejected.
7. Save → fix any red errors (missing approval rule is common).
8. Test → pick sample submitted req_v2 → Run test.
9. Publish → Publish new version → wait for Published status.

Verify checklist

• Submitted req creates sysapproval_approver for manager.
• Approve → u_state approved → BR3 audit + BR4 event.
• Reject → u_state rejected.

Demo / test

Optional — CS1 on u_start_date

Duplicate CS1 logic on u_start_date onChange (same script body) so validation runs when the user changes start date after end date is set.

Development verify / demo checklist

1. Update Set — HR Leave – Build is current; Customer Updates shows new artifacts.
2. Tables — Four _v2 lists open; dictionary shows u_* columns only (Schema).
3. Script Includes — HRLXProLeaveUtilsV2 client-callable; Background script: new x_786686_hr_leave.HRLXProLeaveUtilsV2().calculateBusinessDays('2026-06-01','2026-06-05') → 5.
4. Business Rules — New req_v2 sets u_days_count and u_approver_user (BR1); submit fires event (BR2); approve writes audit + balance (BR3/BR4).
5. Client Scripts — End date before start shows error (CS1); valid range fills u_days_count via GlideAjax (CS2). Optional: duplicate CS2 on u_start_date onChange.
6. UI Policy — Sick → u_reason mandatory.
7. UI Action Submit — Draft → submitted visible only on draft.
8. Menu + Modules — HR Leave navigator shows four modules.
9. Flow — Submit → manager approval → approved/rejected.

Extended properties catalog: PROFESSIONAL_HR_CREATE_PROPERTIES_AND_LINKS.html · Master OBJ index: STUDIO_CREATE_ALL_OBJECTS_01_16.html