Skip to main content

Helpdesk Business Limitations

Summary​

The module is Transitional. The following gaps are verified from source absence or inconsistent implemented behavior and must not be presented as supported features.

Audience​

Product, implementation, HR operations, security, QA, support and architecture.

Business Purpose​

Set safe expectations and focus remediation, acceptance and rollout decisions.

Actors​

Product owners accept scope; engineering resolves gaps; security assesses exposure; administrators operate only approved capabilities; QA validates corrections.

Business Process​

Limitations are reviewed by group, assigned an owner and either accepted as Foundation/Partial/Transitional, confirmed against deployment, or remediated before release.

Responsibilities​

Owners must not treat absent behavior as policy. Security must prioritize self-service visibility and service authorization. Product must define lifecycle and service-management requirements.

Business Rules​

Only implemented validation is authoritative. UI visibility is not proof of service authorization, tenant isolation is not requester isolation, and development seed values are not production policy.

Integrations​

Limitations affect Employee, Authentication, Notification, Document, Reporting, Dashboard and the absent Organization/Workflow connections.

Limitations​

Ticketing​

  • Transitional: generic status changes allow any defined status from any current status.
  • Not implemented: transition guards, resolution/cancellation codes, requester acceptance, templates, knowledge articles and satisfaction surveys.

Assignment​

  • Partial: only direct user assignment is implemented; identity eligibility is not verified.
  • Not implemented: teams, queues, skills, balancing, assignment acceptance, delegation and bulk routing.

Notifications​

  • Foundation: ten event types and audiences exist, but deployed delivery and templates require confirmation.
  • Requires confirmation: internal-comment events target both requester and assignee.
  • Not implemented: preferences, subscriptions, reminders and digest administration.

Reporting​

  • Partial: dashboard, SLA, agent-load and category summaries exist without date range/export/trends.
  • Transitional: one open-count calculation excludes WaitingForRequester while active-report logic includes it.
  • Partial: administration report cards render raw structured content.

Workflow​

  • Not implemented: no workflow orchestration, approval chain or policy-driven transition engine was found.

Self-service​

  • Transitional — material: the list path is tenant-scoped, not requester-scoped.
  • Transitional: form category/priority names do not match service identifier inputs.
  • Not implemented: employee detail, comments, attachments, closure and reopen actions.

Integration​

  • Transitional: direct service authorization is not established in the reviewed bootstrap.
  • Partial: Employee identity is stored but no directory validation lookup exists.
  • Not implemented: Organization routing and Workflow Service integration.
  • Requires confirmation: production gateway route, event consumer and Document Service availability.

UI​

  • Partial: admin supports worklist/actions but not reference-data/SLA administration or attachment upload/delete.
  • Partial: controls are not hidden according to current lifecycle state.
  • Not implemented: personal/team queue, saved views, rich reporting and escalation controls.

Requires Confirmation​

Release acceptance must confirm requester isolation, end-to-end authorization, contract alignment, production policies, integration deployment, audit/privacy controls and an approved lifecycle matrix.

Source References​

  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/gateway-api/EssEndpoints.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx

Reference Content​

The eight limitation groups above are the verified scope and risk reference for business acceptance.

See Also​

Keywords​

Helpdesk limitations, transitional, foundation, partial, not implemented, requires confirmation.

Revision Information​

Draft source-backed reference reviewed 2026-07-20; next quarterly review is 2026-10-20.