tbl_leavereport

Primary key
Format: BigSerial (auto-increment)
Used as: Unique identifier for each report configuration.

JSON configuration defining report structure and layout
Format: JSON string
Structure: Contains pivot table configuration with rows, columns, values, and aggregators
Key Fields: rows[], cols[], vals[], aggregatorName, rendererName
Examples:
- Rows: [“Employee Id”, “Employee Name”, “Leave Code”]
- Columns: [“Month”] for cross-tab reports
- Values: [“No. Of Days”, “Closing Balance”] for aggregation
Usage: Drives the visual layout and data aggregation in the report output.

JSON configuration for report filtering criteria
Format: JSON string
Usage: Defines default filters and filterable dimensions for the report
Integration: Used in getLeaveReport() method to apply dynamic filtering based on user selection.

Human-readable name for the report
Format: String
Examples: “Leave Applied/Availed”, “Leave Balance Report”, “Team monthly leave count-Category Wise”
Usage: Displayed in report selection interfaces and dashboard widgets.

FK: public.tbl_companymaster.companyid
Meaning: Company that owns this report configuration.
Usage: Enables multi-tenant report configuration isolation.

Category identifier for the report
Format: String
Values: “appliedLeaveReport”, “leaveBalanceReport”, “teamLeaveReport”
Usage: Groups related reports and determines which query logic to execute in getLeaveReport() method.

JSON configuration for role-based access control
Format: JSON string
Structure: Defines which user roles/departments can access this report
Filter Criteria: Designation, Department, State, Branch, Pay Cadre, SBU, Employee Type
Usage: In getReportWidgets() method to filter reports based on user’s organizational attributes
Admin Override: Administrators bypass access control and see all reports.