web

ProcureFlow

Purchase requisition and approval workflow on Spring Boot and Angular.

GitHub repo (opens in a new tab) ↗

~/problem

Shows how role-based access, a multi-step approval chain and container-first deployment fit together in a typical internal business system.

An enterprise demo covering purchase requisition, tiered approval, purchase order and invoice with five roles. Spring Boot 4 on Java 21, an Angular 20 frontend, PostgreSQL, JWT login and OIDC single sign-on through a local Keycloak.

~/highlights

  • Approval chain length depends on requisition amount (ADR 0004, tiered thresholds).
  • Five roles: Employee, Department Manager, Procurement Officer, Finance Approver, Admin.
  • Stateless JWT with BCrypt, plus Spring Security OIDC login against Keycloak, with SSO identity linking (ADR 0008).
  • Flyway migrations, append-only by convention; Spotless enforces formatting in mvn verify.
  • Testcontainers integration tests, Karma tests, multi-stage non-root Docker images.
  • CI has build, test, lint and image build for both sides, plus a security workflow.

~/architecture

Architecture of ProcureFlowAngular frontend connects to Spring Boot API. Spring Boot API connects to PostgreSQL, Keycloak. PostgreSQL has no outgoing connections. Keycloak connects to Spring Boot API.Angular frontendSpring Boot APIPostgreSQLKeycloak
Angular frontend → Spring Boot API
Standalone components and signals; dashboards for each role.
Spring Boot API → PostgreSQL, Keycloak
Requisition workflow, approval chain, catalog, vendors, departments.
PostgreSQL
Schema managed by Flyway.
Keycloak → Spring Boot API
Local OIDC identity provider for SSO.

~/stack

  • Java 21
  • Spring Boot 4
  • Angular 20
  • PostgreSQL
  • Keycloak
  • Flyway
  • Testcontainers
  • Docker

~/status

Complete demo with seeded accounts. MIT. Docker-based verification relies on CI because the authoring sandbox blocked registries.