03 — Service Catalog (Studio From Scratch)

How catalog objects relate

Part 1 Category (HR Leave)
        │
        ▼
Part 2 Record Producer → Part 3 Variables
        │
        ▼
Part 4 Producer script (maps variables → req_v2)
        │
        ▼
Part 5 Publish → Employee Center / Portal catalog
        │
        ▼
BR1 days + approver → BR2 event → Flow 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: Catalog Category — HR Leave

Purpose

Groups the Submit Leave Request record producer under a dedicated HR Leave catalog category.

Navigation path

Direct URL

Prerequisites

• Part 1: Application Setup (01 Development).
• Rule 0 Update Set current.

Form fields

Step-by-step create

1. Service Catalog → Categories → New.
2. Fill Title, Description, Order from table. Active = true.
3. Submit. Note category sys_id for record producer.

Verify checklist

• Category HR Leave appears in category list.

Demo / test

Part 2: Record Producer — Submit Leave Request

Purpose

Service Catalog item that inserts submitted req_v2 from catalog variables.

Navigation path

Direct URL

Prerequisites

• Part 3: Table — Leave Request (01).
• Part 1: Roles employee role (02).
• Part 1: Catalog Category.

Form fields

Step-by-step create

1. Record Producers → New. Fill header fields from table.
2. Category = HR Leave. Table = req_v2. Roles = employee.
3. Save. Continue to Part 3 for variables and Part 4 for script.

Verify checklist

• Producer record saved under HR Leave application.

Demo / test

Part 3: Catalog Variables

Purpose

Four question variables mapped by the producer script to req_v2 u_* fields.

Navigation path

Direct URL

Prerequisites

• Part 2: Record Producer created.

Form fields — each variable New

Choice values for leave_type: annual, sick, personal (match req_v2 u_leave_type choices).

Step-by-step create

1. Open Submit Leave Request producer → Variables related list → New.
2. For each row: Name must match producer.* references in script. Set Label, Type, Mandatory.
3. Order: leave_type, start_date, end_date, reason.

Verify checklist

• Four variables on producer; names exactly leave_type, start_date, end_date, reason.

Demo / test

Part 4: Producer Script

Purpose

Server-side script maps catalog variables to req_v2 fields and sets state submitted. Source: src/catalog/RP_submit_leave.js.

Navigation path

Direct URL

Prerequisites

• Part 3: Catalog Variables.
• Part 8: BR1 calculates days on insert.

Step-by-step create

1. Open producer → Script tab.
2. Paste full script below.
3. Save.

Full script (paste-ready)

/**
 * Record Producer Script: Submit Leave Request
 * Application: Custom · Scope: x_786686_hr_leave · sys_id: 83d5298c932b8f107520703efaba1072
 * Target table: x_786686_hr_leave_req_v2
 *
 * Maps producer variables to record fields. Runs server-side when submitted.
 * Variables expected: leave_type, start_date, end_date, reason
 */
(function () {

    current.u_requested_for_user = gs.getUserID();
    current.u_leave_type = producer.leave_type;
    current.u_start_date = producer.start_date;
    current.u_end_date = producer.end_date;
    current.u_reason = producer.reason;
    current.u_state = 'submitted';

    // Link to employee profile of the current user (if exists)
    var emp = new GlideRecord('x_786686_hr_leave_employee_v2');
    emp.addQuery('u_user', gs.getUserID());
    emp.query();
    if (emp.next()) {
        current.u_employee_ref = emp.getUniqueValue();
    }

    // BR1 will calculate days and set the approver on insert.

})();

Verify checklist

• Script saves without syntax errors.

Demo / test

Part 5: Publish and Test

Purpose

Publish catalog item and verify end-to-end submit from Employee Center.

Navigation path

Direct URL

Prerequisites

• Parts 1–4 complete.
• employee1 user with employee role and employee_v2 seeded.

Step-by-step create

1. Record Producer → Related Lists → Catalogs → add to HR Leave category.
2. Service Catalog → open producer → Publish.
3. Login as employee1 → Employee Center → HR Leave → Submit Leave Request.
4. Fill variables → Submit.
5. Verify req_v2 created in submitted state; u_days_count and u_approver_user set by BR1.
6. Verify Flow starts for manager1 approval.

Verify checklist

• Catalog item visible to employee role.
• Submit creates req_v2 in submitted state.
• sysapproval_approver row for manager1.

Demo / test

Service Catalog verify checklist

1. HR Leave category active.
2. Record Producer scoped to HR Leave with four variables.
3. Producer script from src/catalog/RP_submit_leave.js pasted.
4. Published and visible in Employee Center.
5. E2E submit creates submitted req_v2.