Department Master

Navigation Path

Company → Masters → Department Master

1. Department List Page

URL

/masters/department-master

Page Description

• Displays a list of all departments configured in the system
• Allows admins to manage organizational departments
• Provides actions to add, edit, and delete department records

List Table Columns

Row Actions

2. Add Department Page

Triggered From

Department List Page → Add Department button

Page Description

• Allows admins to create a new department
• Used for employee mapping, reporting, and organizational structure

Add Department – Fields

Actions

Validation Rules

• Department Name is mandatory
• Duplicate department names are not allowed

3. Edit Department Page

Triggered From

Department List Page → Edit icon

Page Description

• Allows updating existing department details
• All fields are pre-filled with saved data

Editable Fields

Actions

4. Delete Department Confirmation Alert

Triggered From

Department List Page → Delete icon

Alert Content

• Confirmation message before deletion

Actions:

• Confirm / Yes → Deletes the department
• Cancel → Closes the alert without action

Delete Behavior

• Department is removed permanently after confirmation
• Deletion may be restricted if the department is mapped to employees or other records

Field Definitions, Usage, and Calculation Logic

This section provides a technical analysis of the Department Master's data structure and its role in organizational hierarchy.

1. Field Definitions

2. Field Usage & System Impact

3. Business & Calculation Logic

The Department Master operates as a foundational entity for organizational reporting.

A. Unique Identity Management

The system enforces department uniqueness using a MongoDB partial index:

• Scope: The uniqueness of departmentName is only evaluated where isDeleted.status is false.
• Tenant Isolation: All operations are strictly partitioned by companyId, allowing different tenants to have overlapping department names.

B. Bulk Import Engine

The allInOneDepartmentImport logic facilitates the mass upload of organizational structures:

• Mapping: It maps the Excel description column directly to departmentName.
• Upsert Strategy: If a department with the same name exists (and is not deleted), it updates the existing record with any new metadata; otherwise, a new department is initialized.
• Error Handling: Missing descriptions or duplicate names in the import file are captured in an error log returned to the user, ensuring partial success for valid rows.

C. Relational Integrity

Departments are a mandatory reference in Designations, Units, and Employee Profiles. Deletion is logically restricted at the controller level if active employee records are still assigned to the department.

The Department Master module interacts with the following API endpoints:

Base URL

export const DEPARTMENT_URL = '/api/departmentMaster'

Endpoints

RTK Query Hooks

The following hooks are available for frontend integration:

• useCreateDepartmentMutation
• useGetAllDepartmentsQuery
• useGetDepartmentByIdQuery
• useUpdateDepartmentMutation
• useDeleteDepartmentMutation

End of Documentation