05 — Workspace / UI Builder (Studio From Scratch)

How workspace objects relate

Part 1 Experience (HR Leave Workspace)
  ├── Part 2 Pages (My Requests, Team Approvals, Admin)
  ├── Part 3 Data resource → req_v2 table broker
  └── Part 4 List component + role bindings

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: Create Experience — HR Leave Workspace

Purpose

Now Experience workspace container scoped to HR Leave application.

Navigation path

Direct URL

Prerequisites

• Part 3: Table — Leave Request (01).
• Roles from 02 Administration.

Form fields

Step-by-step create

1. UI Builder → Create experience → fill fields → Create.
2. Confirm Application = HR Leave in header.

Verify checklist

• Experience opens in UI Builder.

Demo / test

Part 2: Pages — My Requests, Team Approvals, Admin

Purpose

Three routed pages for employee, manager, and HR admin personas.

Navigation path

Prerequisites

• Part 1: Create Experience.

Form fields

Step-by-step create

1. Add page → Name My Requests → Route my-requests.
2. Repeat for Team Approvals and Admin pages.
3. Add navigation menu items linking each page (Part 4).

Verify checklist

• Three pages listed in experience.

Demo / test

Part 3: Data Resource — req_v2

Purpose

Table data broker feeding list components with req_v2 records.

Navigation path

Prerequisites

• Part 2: Pages.

Form fields — My Requests broker

Team Approvals broker

Step-by-step create

1. Data Resources → Create → Table → req_v2.
2. Set conditions per page persona.
3. Columns: Number, Leave Type, Start, End, Days, State.

Verify checklist

• Data resource preview returns rows for test user.

Demo / test

Part 4: Bind List + Role Restrictions

Purpose

Attach list components to data resources and publish workspace with role access.

Navigation path

Prerequisites

• Part 3: Data Resource.

Step-by-step create

1. My Requests page → drag List → bind My Leave Requests data resource.
2. Team Approvals page → List → team broker filter.
3. Admin page → Lists for employee_v2 and bal_v2 — hr_admin only.
4. Navigation: menu items with role restrictions per page.
5. Publish workspace → assign roles employee, manager, hr_admin.
6. Impersonate each test user → open workspace URL.

Verify checklist

• employee sees only own requests on My Requests.
• manager sees submitted items awaiting approval.
• hr_admin sees admin lists.

Demo / test

Workspace verify checklist

1. Experience published under HR Leave.
2. Three pages with correct role gates.
3. req_v2 list filtered per persona.