LMS Consolidated Limitations
Summary
This consolidates verified limitations from LMS Epics 12.1–12.5 and the current UI/operations audit.
Audience
Business, product, engineering, QA, support, operations, architecture, security, and implementation reviewers.
Reference Content
| Area | Verified limitation | Classification |
|---|---|---|
| Authorization | Training endpoints lack registered authentication/authorization enforcement | Not implemented |
| Tenant/employee ownership | Tenant filters exist; header trust and ESS employee ownership remain incomplete | Transitional |
| Business policy | Eligibility, prerequisites, mandatory-training governance, attendance, recommendations, and several approvals incomplete | Transitional |
| Course UI | No dedicated editor, catalog browser, module/lesson editor, or material manager | Partial |
| Learner UI | ESS is read-only; no start/complete, assessment-taking, or certificate workspace | Partial |
| Session lifecycle | No UI/API completion, cancellation, attendance, participant, or capacity behavior | Not implemented |
| Certificate lifecycle | No produced expiry, revoke, renew, or compensation behavior | Not implemented |
| Events | No domain-event layer, inbound Training consumer, or active Training relay trigger | Transitional |
| Reliability | Replay, cleanup, dead-letter policy, terminal publisher retry, reconciliation, and ordering guarantees absent | Foundation |
| Documents | HTTP work and local save are not distributed-transactional; compensation absent | Transitional |
| Database | No explicit optimistic concurrency/version fields or reconciliation ownership | Foundation |
| UI quality | No dedicated LMS UI test suite or confirmed accessibility conformance | Foundation |
| Operations | No production runbook, alert policy, service objectives, rollback workflow, or named escalation roster | Foundation |
| Integrations | No Workflow integration or direct Employee validation integration | Not implemented |
Unsupported behavior remains Draft and must not be presented as operationally ready.
Requires confirmation
Policy ownership, fine-grained authorization, operational governance, future-state terminology, and retirement criteria require confirmation where not implemented.
Source References
docs/modules/lms/business/known-limitations.mddocs/modules/lms/technical/technical-limitations.mddocs/modules/lms/api/api-limitations.mddocs/modules/lms/database/data-integrity-and-transactions.mddocs/modules/lms/events/event-limitations.mdUI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsxmicroservices/src/training-service/Program.cs
Related Articles
See Also
Keywords
- LMS reference
- LMS Consolidated Limitations
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly