How neozhu/workflow works
Project Type and Purpose
• ApprovalFlow is a full-stack, server-side Blazor web application.
• Purpose: internal enterprise workflow and approval system with eight form types and seven functional modules.
(Implied) File Structure
• Although the file tree provided is minimal, a standard Blazor Server project will include:
• A .csproj at root
• /Pages for Razor components (UI pages)
• /Shared for common layouts/components
• /Data or /Services for EF Core DbContext, repositories, and business logic
• /wwwroot for static assets (CSS/JS/images)
• Configuration files (appsettings.json)
• Deployment artifacts: release.zip (build output), publish-dotnet8.zip (published site), IIS configuration.
README Insights
• Technical stack: .NET 7, Blazor Server, EF Core, MS SQL Server Express, IIS
• Core functional modules: Dashboard, Workflow Engine, My Tasks, Warehouse Verify, Check-in/Check-out, Workflow Configuration, System Management
• Eight distinct form processes, each driven by the workflow engine.
Relationships and Interactions
• Client Browser ↔ IIS/Kestrel (SignalR) ↔ Blazor Server pages
• Blazor Server services → EF Core DbContext → SQL Server Database
• Workflow Engine module calls data layer to persist and query process states
• Authentication service integrated at the server boundary
• Notification service invoked by business logic upon state changes
Architectural Patterns and Design Principles
• Component-based UI (Blazor Razor Components)
• Server-side rendering with real-time updates via SignalR
• Layered architecture: Presentation → Business/Workflow → Data
• Dependency Injection for services (e.g., IWorkflowManager, IRepository<T>)
• Configuration-driven workflows (workflow definitions stored in DB or JSON)