Visual map — Ch.09 · Modules & Flow
Application menu + Ask For Approval flow
Navigator modules · exclusive flow
Development
Full visual path (all chapters): VISUAL_FROM_SCRATCH_00_16.html
Studio-only from scratch: Full create steps for navigator and approval flow. Cross-module study is optional reading.
Also open: Properties + Direct Links · Schema · Studio Create All Objects · Previous: 08 ATF Testing
How menu, modules, and flow relate
Part 1 Application Menu → Part 2 Modules (4 list links) Submit (UI Action / Catalog) → Part 3 Flow → Approval → BR3/BR4
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.
- Application picker — top-right globe / application menu → select HR Leave (
x_786686_hr_leave). Never leave Global selected when creating scoped artifacts. - Update Set — All → System Update Sets → Local Update Sets → New:
After submit: open the record → click Make Current. Direct list: {BASE}/sys_update_set_list.doField Value Name HR Leave – BuildApplication HR Leave State In Progress Description Captures all HR Leave lab artifacts - Open Studio — {BASE}/$studio.do → confirm header shows HR Leave.
If artifacts land in Global scope, delete them and recreate under HR Leave. ACLs and events created globally will not behave correctly for this app.
Verify Update Set: Create a test Script Include in Studio → open HR Leave – Build → Related List Customer Updates shows the new file.
Part 1: 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
| Field | Value |
|---|---|
| Title | HR Leave |
| Application | HR Leave |
| Order | 100 |
| Roles | x_786686_hr_leave.employee (minimum) |
Step-by-step create
- If missing: Studio → Application Menu → New → fill fields.
- Save. Confirm appears in Application Navigator.
Verify checklist
- Navigator shows HR Leave heading.
Demo / test
employee1 login → sees HR Leave menu after modules Modules.
Part 2: Modules
Purpose
Four list modules linking to req_v2, employee_v2, bal_v2, audit_v2 tables.
Navigation path
Direct URL
Prerequisites
- Part 1: Application Menu menu. Tables Table HR Employee..05.
Form fields
| Title | Type | Table | Order | Roles |
|---|---|---|---|---|
| Leave Requests | List | x_786686_hr_leave_req_v2 | 10 | employee, manager, hr_admin |
| Employees | List | x_786686_hr_leave_employee_v2 | 20 | hr_admin |
| Balances | List | x_786686_hr_leave_bal_v2 | 30 | hr_admin |
| Audit Trail | List | x_786686_hr_leave_audit_v2 | 40 | hr_admin |
Step-by-step create
- Module → New for each row. Application Menu = HR Leave.
- Type = List → Table = as listed. Order as table.
- 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
employee1 → only Leave Requests visible.
Part 3: 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
| Field | Value |
|---|---|
| Name | HRLX Leave Approval |
| Application | HR Leave |
| Description | Approval flow for submitted leave requests |
Trigger — Record Updated
| Field | Value |
|---|---|
| Trigger type | Record Updated |
| Table | x_786686_hr_leave_req_v2 |
| Condition | State [u_state] is submitted AND State changes |
| Run flow | Once per record (recommended) |
Action 1 — Ask For Approval
| Input | Value |
|---|---|
| Record | Trigger → Leave Request Record (data pill) |
| Table | x_786686_hr_leave_req_v2 |
| Approval field | u_approver_user |
| Approval reason | Leave approval required |
| Rules → Approve | Anyone approves (required — do not leave empty) |
If Approved → Update Record
| Record | Trigger record pill |
| Field map | u_state = approved |
Else → Update Record
| Field map | u_state = rejected |
Step-by-step create
- Flow Designer → Create Flow → Name HRLX Leave Approval, Application HR Leave.
- Add trigger → Record Updated → table req_v2 → condition u_state is submitted + changes.
- + → Ask for Approval → fill Action 1 table → Rules: Anyone approves → Done.
- + → Flow Logic → If → condition "approval was Approved".
- Yes branch → Update Record → u_state = approved.
- Else branch → Update Record → u_state = rejected.
- Save → fix any red errors (missing approval rule is common).
- Test → pick sample submitted req_v2 → Run test.
- 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
- employee1 submits leave (UI Action or catalog).
- manager1 → My Approvals → Approve.
- Verify state, audit_v2, bal_v2 updated.
Part 4: Professional Module Encyclopedias
Purpose
After HR Leave menu/flow works, use the professional implementer guides (same Part structure as 01 Development) for ITSM, CMDB, ITOM, ITAM, HRSD, CSM, FSM, SPM, GRC, SecOps, DevOps, App Engine — with direct URLs, properties, and navigator module publish steps.
Navigation path
Direct URL
Prerequisites
- Parts 1–3 complete for core HR Leave.
Related guides
- 00 Modules Index — hub + study order for all 12 modules
- ITSM · CMDB · ITOM · ITAM
- HRSD · CSM · FSM · SPM
- GRC · SecOps · DevOps · App Engine
- 12 Integration — Scripted REST after menu/flow works
Verify checklist
- Core app E2E works without optional modules.
- Modules Index opens and links resolve.
Demo / test
employee1 → HR Leave menu → submit → manager approves. Then open HRSD Part 13 for HR Leave cross-link.
Modules verify checklist
- HR Leave menu visible.
- Four modules with correct roles.
- Flow published and approving.