HR Leave Professional Solution — Navigation & Deployment Tutorial

Platform: ServiceNow Australia (current family · Sep 2026)
Application: Custom · Scope x_786686_hr_leave · sys_id c84db0e8839f0b509f02b0d6feaad3c9
HTML portal: html/index.html
Replace {BASE} with your instance, or enter it once at the top of the HTML portal.

This is the execution path for a mature HR Leave solution: Foundation → Development → Security → Experience → Automation → Integration → Analytics → Testing → Deployment.

1. Solution architecture

Employee Center / Service Portal
        │
        ▼
Record Producer / Catalog Item
        │
        ▼
x_786686_hr_leave_req_v2
   │       │        │
   │       │        └─ Events → Notifications
   │       └─ Flow Designer → Manager approval
   └─ Business Rules → Balance + Audit
        │
        ├─ REST / Integration Hub → HR/ERP
        ├─ Reports / Dashboard / PA
        └─ ATF + ACL validation

Core data:

2. Administration foundation

Tutorial

1. Create one Update Set per deployment stage.
2. Create Groups first, then assign Roles to Groups.
3. Add test users to Groups; avoid direct role grants.
4. Create table and field ACLs for employee, manager, HR admin, and integration.
5. Put environment-specific values in System Properties.

Gate A: employee sees only own requests; manager sees assigned requests; HR admin sees all; integration role can execute only the API.

3. Development

Build order

1. Tables and Dictionary fields.
2. Script Includes (reusable logic).
3. Business Rules (server orchestration).
4. Client Scripts and UI Policies.
5. Flow Designer.
6. Catalog / Record Producer.
7. Portal or Employee Center.

Copy-ready scripts: SCRIPTS_INVENTORY.html and HTML → html/scripts/index.html.

Gate B: date validation works; business days calculate; approver resolves; state change creates audit; approval updates balance.

4. Catalog and employee experience

Gate C: employee submits from Catalog/Employee Center and receives the created request number.

5. Automation and notifications

Gate D: submitted/approved/rejected events appear in Event Log and the correct recipient receives each notification.

6. Integration

Security requirements: dedicated integration user, scoped integration role, no credentials in scripts, properties/credential records per environment.

Gate E: positive and negative API tests pass; unauthorized request returns 401/403; logs contain no secrets.

7. Reports and dashboards

Required dashboard: Requests by state, requests by type, pending approvals, days by month, approval time, rejection rate.

Gate F: HR role sees dashboard; employee cannot discover restricted report data; PA collector has a successful run when licensed.

8. Testing and deployment

Deployment sequence:

1. Freeze Update Set and peer review.
2. Export/import or retrieve; Preview before Commit.
3. Resolve collisions deliberately—never skip without evidence.
4. Run ATF smoke suite.
5. Validate ACLs using impersonation.
6. Validate Flow, events, notifications, reports, and integration.
7. Record rollback steps and release evidence.

Gate G: no unresolved Update Set errors; ATF passes; audit trail and rollback plan are documented.

9. Module maturity extensions

Do not force every module into HR Leave. Add a module only when there is a business capability, license, owner, data contract, and support model.

10. Australia upgrade readiness

1. Confirm family/build: {BASE}/stats.do.
2. Review skipped changes and customizations.
3. Test on sub-production before production.
4. Re-run ATF and role-based UAT.
5. Prefer Flow Designer over new legacy Workflow.
6. Validate licensed workspace routes because plugins and UI versions can change.
7. Keep the scoped API names and table names unchanged during family upgrade.

Study sequence: ../SERVICENOW_ONE_WEEK_STUDY_DEPLOY_AUSTRALIA.html → this tutorial → module-specific documents → ATF/Deployment gates.