tbl_resignationmaster

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for a specific resignation request.

FK: public.tbl_employee.employeeid
Meaning: The identifier of the employee who submitted the resignation request.
Usage: Links the request to the employee’s master data.

The employee’s Business Unit at the time of resignation.
Format: String
Dependency: Stores the employee’s company ID.

Java Field: requestType
Meaning: The type of separation request (e.g., Resignation, Retirement, Termination, End of contract).
Usage: Categorizes the separation event.

The detailed reason provided by the employee for their resignation.
Format: String (Large text)
Business: Used for analyzing employee turnover.

The date the employee submitted the resignation request.
Usage: Marks the start of the notice period calculation.

The requested last working date as proposed by the employee.
Usage: Used in conjunction with noticePeriod to calculate compliance.

Indicates which existing address the employee prefers for final communication (e.g., Permanent, Current).
Format: String (e.g., “Permanent Address”)

The standard contractual notice period for the employee in days (e.g., 30, 60, 90).
Format: Integer (days)

Java Field: address
Meaning: Any alternative/new address provided by the employee for communication.

The personal email address provided by the employee for post-employment contact.

Stores the file path or content of the attached formal resignation letter.

The final, approved last working date for the employee.
Usage: Determined by the HR/Manager after considering business needs and notice period compliance.

The creation date of the request row (system timestamp).
Note: This column is marked as updatable = false in the model.

Java Field: finalStatus
Meaning: The final, overall status of the resignation request.
Values: e.g., “Approved”, “Rejected”, “Cancelled”, “Revoked/Pull Back”

Java Field: cancelReason
Meaning: The reason provided if the request was cancelled, rejected, or revoked.

The difference in days between the contractual notice period and the employee’s requested notice period.
Logic: Calculated as (noticePeriod - actual notice given).

Java Field: rep1Status
Meaning: The action taken by the First Level Approver (Rep1).
Values: e.g., “Approved”, “Rejected”, “Pending”, “Relieving Date Proposed”

Java Field: rep2Status
Meaning: The action taken by the Second Level Approver (Rep2).
Values: e.g., “Approved”, “Rejected”, “Revoked/Pull Back”

A legacy or custom field, potentially used for an additional approval level or data point.

Java Field: attachment
Meaning: Stores the file path or ID for a supplementary document/attachment related to the request.

The relieving date proposed by the First Level Approver (Rep1).

The relieving date proposed by the Second Level Approver (Rep2).

The calculated shortfall in days based on the relieving date proposed by Rep1.

The calculated shortfall in days based on the relieving date proposed by Rep2.

The main status of Rep1’s approval stage (e.g., “Pending”, “Completed”).

The main status of Rep2’s approval stage (e.g., “Pending”, “Approved”, “Revoked/Pull Back”).

The main status of the HR approval stage (e.g., “Pending”, “Approved”, “Revoked/Pull Back”).

The sub-status/reason for the action taken by Rep1 (e.g., “Approved with shortfall”, “Rejected for business reasons”).

The sub-status/reason for the action taken by Rep2.

The sub-status/reason for the action taken by HR.

The number of days taken by Rep1 to process the request.

The number of days taken by Rep2 to process the request.

The number of days taken by HR to process the request.

The overall status of the Department Clearance process.
Values: e.g., “Pending Initiation”, “In Progress”, “Completed”, “Overdue”

The date the Department Clearance process was formally started.

The status of the Exit Interview process.
Values: e.g., "Not Initiated ", “Initiated”, “Not Required”, “Completed”

The date the Exit Interview process was formally initiated.

The specific status set by the First Level Approver (Rep1).
Values: e.g., “Approve”, “Reject”, “Revoked/Pull Back”

The timestamp when the First Level Approver (Rep1) processed the request.

The specific status set by the Second Level Approver (Rep2).

The timestamp when the Second Level Approver (Rep2) processed the request.

The specific status set by the HR Approver.

The timestamp when the HR Approver processed the request.

The reason provided by the employee or administrator for pulling back/revoking a submitted request.

The name of the workflow setup used for this specific resignation (e.g., “Manager-HR-Final”).
Usage: Defines the number of approvers and required clearances.

Configuration flag: Indicates if formal approval/rejection is mandatory for this workflow.

Configuration flag: Indicates if the multi-department No-Dues Clearance process is required.

Defines when the clearance process should be initiated (e.g., “On Submission”, “After HR Approval”, “X Days Before Relieving”).

The number of days used for the clearance initiation logic.

Detailed rule specifying the timing for triggering department clearance (e.g., relative to ActualRelievingDate).

Configuration flag: Indicates if an exit interview is mandatory for this resignation.

Employee’s age in years at the time of the request (likely derived from DOB).

The number of days before the relieving date to send notifications/reminders.

The date a scheduled job is/was set to initiate the department clearance.

Boolean flag: Indicates if the workflow initiation scheduler has been run for this record.

The relieving date approved by the HR department (often the final date).

Flag or JSON to store soft-deleted data or history details for auditing purposes.