Skip to main content

Workflow Compatibility

Summary​

Compatibility is limited to runtime and identity accommodations. No alternate Workflow API surface or canonical/legacy domain-object pair exists.

Compatibility routing​

Implemented accommodations​

Startup enables legacy timestamp behavior for the database provider. Authentication accepts two configured token-key families. Tenant/identity extraction recognizes multiple claim and metadata names plus limited tenant-key aliases.

Frontend and gateway boundary​

The portal calls Workflow-relative paths through its shared API client. Static inspection found no Workflow route in Gateway source, so deployed transport is Requires confirmation.

Canonical model​

All direct endpoints use the same DTO and aggregate model. No compatibility controller, legacy DTO set or adapter layer was found.

Limitations​

Compatibility aliases are embedded in the tenant adapter. No deprecation policy, route fallback or version negotiation is implemented.

Requires Confirmation​

Effective ingress routing, alias retirement and token-family ownership require confirmation.

Source References​

  • microservices/src/workflow-service/Program.cs
  • microservices/src/workflow-service/Infrastructure/Persistence.cs
  • microservices/src/workflow-service/Api/WorkflowEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
  • microservices/src/gateway-api/Program.cs

See Also​

Keywords​

Workflow architecture, approval engine, Workflow Service, technical foundation.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20