Skip to main content

Employee Known Limitations

Summary​

This consolidated list contains only limitations confirmed across Employee Business, Technical, API, Database, Events, UI, and Operations reviews.

Audience​

  • Product owners, architects, developers, QA/support and DevOps engineers

Reference Content​

Transition and ownership​

  • Current UI uses monolith-compatible numeric identifiers and a broader DTO; extracted compatibility uses GUID identifiers.
  • Gateway cutover is not active by default and requires parity/approval.
  • Monolith and extracted stores coexist without a confirmed backfill runner, durable ID map, dual-write, or reconciliation tool.
  • Final source-of-truth and cutover ownership require confirmation.

UI​

  • Employee create/edit/details are modal/panel states, not dedicated routes.
  • No Employee timeline or notes UI is implemented in Labor.tsx.
  • No frontend test/spec files or test script were found.
  • Accessibility/responsive conformance requires audit; WCAG compliance is not claimed.
  • Component-level mutation permission checks are absent for core Employee actions; API enforcement is authoritative.

Service and operations​

  • Basic health does not prove database, broker, or downstream readiness.
  • Startup migration can affect availability; external migration ownership requires confirmation when suppressed.
  • Employee outbox processor is registered but no hosted invoker was found.
  • Retry ceiling, dead-letter path, backlog metrics, alerts, replay runbook, formal SLOs, and named on-call ownership are not implemented or require confirmation.

Contracts and governance​

  • Several Employee events have no confirmed consumers.
  • Formal event compatibility/deprecation governance is not implemented.
  • Employment type is not centrally constrained in the extracted domain.
  • Extracted named policies currently require authentication but do not enforce matching permission claims.
  • Business rules for probation, promotion, transfer, rehire, exit, and some lifecycle states remain incomplete or require confirmation.

Source References​

  • microservices/src/employee-service/docs/employee-compatibility-placeholders.md
  • microservices/src/employee-service/Program.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsx
  • microservices/src/gateway-api/Program.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • Employee limitations
  • transition gaps
  • governance gaps

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly