H HIGHRULEZSYS / HIGH-01

INITIALIZING INTERFACE

0%
  • INTERFACEREADY
  • PROFILEOK
  • AUTOMATIONONLINE
  • INFRASTRUCTUREONLINE
  • EXPEDITION DATASYNCED
  • SECURITYACTIVE
LAT 3.0500LON 101.5183NODE / SELANGOR MY
SKIP TO CONTENT

PROJECT003

OneFlow

PPG AEN Hackathon 2026 prototype: a connected employee lifecycle demo around mock Workday — cases, role tasks, journeys and simulated automation. Not a production HR platform.

  • CATEGORYAUTOMATION
  • YEAR2025
  • STATUSHACKATHON PROTOTYPE
  • ACCESSPUBLIC

STATUS ONLINE

  • DEMO / ONLINE
  • LAST CHECK · JUST NOW
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Docker
OneFlow project visual

01 FRAMING

Hackathon prototype

OneFlow was built for PPG AEN Hackathon 2026, Challenge 4 (Team Error 404). It is a working Next.js demo with synthetic personas and simulated automation — not an officially deployed production employee platform, and not a Workday replacement.

02 CHALLENGE

What we set out to solve

Onboarding, offboarding, workplace admin, access provisioning and resource management were fragmented across teams and systems. The challenge asked for end-to-end lifecycle visibility, less admin load and clearer compliance/access governance — at prototype depth, without claiming measured ROI.

03 JOURNEY

Employee and admin experience

  1. 01
    Mock Workday trigger

    Demo directory where hire/exit status changes create lifecycle cases in OneFlow — no live Workday API.

  2. 02
    Employee onboarding

    Guided first-day journey: readiness countdown, tasks, induction and access-card forms, inbox and profile.

  3. 03
    Employee offboarding

    Exit clearance journey with remaining actions and last-working-day visibility.

  4. 04
    Role task queues

    HR, IT Security, onsite IT, facilities, hiring manager, finance and related roles see owned work — not a single shared inbox.

  5. 05
    Admin dashboard

    Volumes, overdue items, Needs Attention, lifecycle cases, templates, reports and demo reset controls.

  6. 06
    Simulated automation

    Automation runs are simulated locally. A “Live” mode is an explicit Phase 2 stub — integrations are not connected.

04 SCREENS

Demo walkthrough

Synthetic demo data only. Persistent UI banner marks mock Workday data and simulated automation.

PROJECT HUBHackathon hub entry for the Workday mock and OneFlow demo.
ONBOARDINGEmployee onboarding dashboard with first-day journey progress.
ADMIN OVERVIEWAdministrator operations view with preboarding and offboarding metrics.
MY TASKSRole-filtered onboarding action queue in the demo workspace.
LIFECYCLE CASESOnboarding and offboarding case board for demo readiness tracking.
MOCK WORKDAYMock HR directory used to trigger hire and exit lifecycle events.

05 ARCHITECTURE

Prototype approach

The UI is Next.js App Router. A DataService facade persists to browser localStorage — not Dataverse. Auth is demo email/password in client session storage. Optional AWS SES exists only for demo mail delivery. A documented Microsoft production path (Entra, Dataverse, Power Automate, Power BI) is proposal-only.

LIFECYCLE FLOWDesign plate for the guided onboarding concept supporting the prototype screens.Design diagram / not a screenshot

06 TECHNOLOGY

What the demo runs on

Confirmed from the Error404 / OneFlow package — not the proposed Microsoft production stack.

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Docker
  • AWS SES (optional)

07 OUTCOME

What the prototype proves

OneFlow validates an operating model: Workday as source of event, OneFlow as orchestration for cases, role-owned tasks and employee journeys. It does not measure lead-time or satisfaction KPIs, and it does not connect to live enterprise systems. The public demo remains labeled as mock data with simulated automation.

OneFlow — Case Study | HIGHRULEZ