tbl_employeegeofencingrule

-1 rows


Description

Module: HRMS Geo-fencing Module
Purpose: Manages the assignment of geo-fencing rules to individual employees with configurable weightage for attendance calculation and compliance scoring.
Data: Each row represents a specific geo-fencing rule assigned to an employee, defining how their location data should be evaluated for attendance and compliance purposes.
Process Usage:
- Links employees to specific geo-fencing rules and locations.
- Configures rule importance through weightage values for scoring calculations.
- Enables personalized location tracking policies for different employee roles.
Key Points:
- Many-to-many relationship between employees and geo-fencing rules.
- Weightage-based scoring system for compliance evaluation.
- Flexible rule assignment supporting different tracking requirements per employee.
Business Impact: Enables customized location tracking policies, supports role-based attendance rules, and provides weighted compliance scoring for field workforce management.

Columns

Column Type Size Nulls Auto Default Children Parents Comments
employeegeofencingruleid bigserial 19 √ nextval('tbl_employeegeofencingrule_employeegeofencingruleid_seq'::regclass)

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for each employee geo-fencing rule assignment.
employeeid varchar 500 null
tbl_employee.employeeid fk_tbl_employeegeofencingrule_employeeid R

FK: public.tbl_employee.employeeid
Purpose: Identifies the employee to whom this geo-fencing rule is assigned.
Dependency: Links rule assignments to employee master records for personalized tracking.
geofencingruleid int8 19 null
tbl_geofencingrule.geofencingruleid fk_tbl_employeegeofencingrule_geofencingruleid R

FK: public.tbl_geofencing_rule.GeoFencingRuleId
Purpose: References the specific geo-fencing rule being assigned to the employee.
Usage: Defines the location, radius, timing, and validation criteria for employee tracking.
weightage int8 19 null

Format: Long (Integer)
Purpose: Defines the importance or scoring weight of this rule in overall compliance calculations.
Business Logic:
- Higher weightage = Greater impact on overall compliance score
- Used in weighted average calculations for attendance compliance
- Enables prioritization of critical location rules
Examples: Office attendance rule might have weightage 100, while client site rule might have weightage 50.
createdby varchar 50 √ null
createddate timestamp 29,6 √ null
modifiedby varchar 50 √ null
modifieddate timestamp 29,6 √ null

Indexes

Constraint Name Type Sort Column(s)
pk_tbl_employeegeofencingrule_employeegeofencingruleid Primary key Asc employeegeofencingruleid
uq_tbl_employeegeofencingrule_employeeid_geofencingruleid_weigh Must be unique Asc/Asc/Asc employeeid + geofencingruleid + weightage

Relationships

Close relationships within degrees of separation