Leave Types
Summary
Leave types are tenant-scoped, first-class configuration, but several declared restrictions are not enforced during request creation.
Audience
Leave/HR administrators, employees, analysts, product owners, QA, and implementers.
Concepts
| Property | Confirmed business meaning | Current maturity |
|---|---|---|
| Name | Human-readable request category; required when saving a type. | Implemented. |
| Code | Optional short identifier. | Implemented as metadata. |
| Paid | Declares paid/unpaid nature. | Stored; Payroll compatibility still uses a textual convention, so Transitional. |
| Balance applicability | Requests and balances share the Leave type text. | Implemented relationship; explicit balance-required flag does not exist. |
| Allow half day | Declares half-day eligibility. | Stored but not confirmed as enforced by request calculation. |
| Allow carry forward | Declares carry-forward eligibility. | Stored; processing Not implemented. |
| Maximum days per year | Optional annual cap. | Stored but enforcement Not implemented. |
| Active | Enables/disables a type. | Stored; request validation against active types Not implemented. |
The source contains a default fallback category named Casual Leave. Development-only seed data is not a production Leave catalog and is intentionally not presented as tenant policy. Eligibility, request restrictions, precedence, and policy assignment beyond tenant/type require confirmation.
Source References
microservices/src/leave-service/Domain/Leave/LeaveConfig.csmicroservices/src/leave-service/Domain/Leave/LeaveConstants.csmicroservices/src/leave-service/Application/LeaveWorkflows.cs
Related Articles
See Also
Keywords
- Leave
- Leave Types
- Workforce management
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly