Skip to main content

Checklist and Task API Boundaries

Summary​

The verified checklist-like HTTP boundary is a generic monolith onboarding-task save operation plus task data in the HR Operations workspace. No dedicated onboarding checklist or offboarding clearance checklist API was found.

Audience​

Developers, QA, support, and solution architects.

Verified task behavior​

The save operation creates or updates a tenant-scoped task for an employee. It requires an employee and task name, validates that the employee belongs to a resolvable tenant, and defaults empty category/status values. The workspace returns visible tasks for non-employee-only users, with a bounded result size.

Not implemented​

  • Dedicated checklist definition and instance operations
  • Mandatory-task completion enforcement
  • Task dependencies or ordered steps
  • Bulk checklist assignment
  • Offboarding clearance items
  • Asset-return task linkage
  • Document checklist validation
  • Checklist completion as a prerequisite for onboarding or exit completion

The frontend onboarding page appends a documents-submitted/pending note to completion input. That client behavior is not a checklist API and is not server-enforced on the extracted path.

Requires confirmation​

  • Whether generic onboarding tasks are actively used by the current portal.
  • The intended relationship between tasks and Recruitment onboarding aggregates.
  • Whether offboarding clearance should reuse this model or receive a separate API.
  • Task ownership, due-date, status vocabulary, and deletion policy.

Source References​

  • Controllers/HrOperationsController.cs
  • Models/OnboardingTask.cs
  • Data/AppDbContext.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx

See Also​

Keywords​

  • Generic onboarding task
  • Checklist API
  • Clearance gap

Revision Information​

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