Skip to main content

Job Opening Management UI

Purpose​

Provides the protected workspace for listing, creating, editing, closing, and viewing candidates associated with compatibility job positions.

Talent → Recruitment; protected route for the job-opening workspace. The legacy Recruitment root redirects here.

Intended users and preconditions​

The navigation targets recruiter and HR-admin audiences. An authenticated tenant user must pass the Recruitment feature guard; lookup data is loaded from the workspace endpoint.

Main components​

Header actions, metrics, opening form, card/table view switch, filters, candidate side panel, status badges, and error banner.

Fields, columns, and sections​

The form includes job, organization, hiring, opening-count, experience, location, employment, status, description, and compensation-range fields. Lists show opening and status details; exact sensitive values are intentionally not reproduced here.

Filters and actions​

Search and status filtering are client-side. Confirmed actions are add, edit, close, switch view, and view related candidates.

Validation​

The UI requires a title and a positive opening count. Backend lifecycle and tenant validation remain authoritative.

UI states​

  • Loading: A loading state replaces the opening list.
  • Empty: The list and related-candidate panel have explicit no-record states.
  • Success: Save and close operations reload workspace data and reset or retain selection as coded.
  • Error: Load, save, and close failures render sanitized page errors.

Permission behavior​

The route and menu use Recruitment feature evidence. The component has no per-action permission check; authoritative API enforcement is incomplete.

API dependencies​

Uses compatibility workspace, position create/update, and position-status endpoints.

Opening status is Draft, Open, or Closed. Public visibility is tied to open positions. A dedicated requisition UI is absent.

Screenshot placeholder​

Capture only sanitized, non-production data after product and privacy review. No screenshot is embedded in this Draft page.

Requisition Workflow UI boundary​

No requisition route or component was found. Workflow-managed submission/decision behavior is API-only, so the UI flow is an explicit gap:

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentJobOpeningsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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