tbl_geofencingrule

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for each geo-fencing rule.

Format: String
Purpose: Human-readable name identifying the geo-fencing rule.
Examples: “Office Attendance Zone”, “Client Site Monitoring”, “Field Staff Tracking”, “Remote Work Perimeter”
Usage: Displayed in rule selection interfaces and reports.

Format: String
Purpose: Defines which punch operations are restricted by geo-fencing.
Common Values:
- “BOTH”: Both punch-in and punch-out require geo-fencing compliance
- “PUNCH_IN_ONLY”: Only punch-in requires location validation
- “PUNCH_OUT_ONLY”: Only punch-out requires location validation
- “NONE”: No punch restrictions based on location
Usage: Controls attendance validation strictness.

Format: String (JSON Rule Engine Syntax)
Purpose: Defines which employees are subject to this geo-fencing rule based on organizational attributes.
JSON Structure Examples:
- Department-based: {"department": ["SALES", "FIELD_OPS"]}
- Location-based: {"officeLocation": ["MUMBAI", "DELHI"]}
- Role-based: {"role": ["FIELD_STAFF", "REMOTE_WORKER"]}
- Composite rules with AND/OR logic
Usage: Dynamic rule assignment based on employee master data.

Format: Long
Purpose: Priority weight for rule evaluation when multiple rules apply to same employee.
Usage: Higher weightage rules take precedence in conflict resolution.
Business Logic: Used to determine which rule applies when employee qualifies for multiple geo-fencing rules.

Flag Type: Boolean
Purpose: Master switch for geo-fencing enforcement.
Values:
- TRUE: Geo-fencing is active and enforced
- FALSE: Geo-fencing is disabled (rule exists but not enforced)
Usage: Quick enable/disable of entire geo-fencing rule without deleting configuration.

Flag Type: Boolean
Purpose: Enables notifications when employees move outside geo-fenced boundaries.
Values:
- TRUE: Send alerts when boundary violations occur
- FALSE: No boundary violation notifications
Usage: Real-time monitoring of employee movement compliance.

Format: Float (Minutes)
Purpose: Grace period before sending boundary violation notifications.
Usage: Allows temporary boundary exits without immediate alerts.
Examples: 5.0 (5-minute grace period), 15.0 (15-minute tolerance)
Business Logic: Prevents false alarms for brief boundary crossings.

Flag Type: Boolean
Purpose: Enables notifications when employees remain idle at one location.
Values:
- TRUE: Monitor and alert for extended idle time
- FALSE: No idle time monitoring
Usage: Productivity monitoring and safety checks for field staff.

Format: Float (Minutes)
Purpose: Time threshold for idle location notifications.
Usage: Defines how long employee can remain stationary before alert triggers.
Examples: 30.0 (30 minutes idle), 120.0 (2 hours idle)
Business Logic: Balances productivity monitoring with reasonable break periods.

Flag Type: Boolean
Purpose: Enables notifications for GPS status changes (ON/OFF).
Values:
- TRUE: Alert when GPS is turned off during working hours
- FALSE: No GPS status monitoring
Usage: Ensures location tracking reliability and detects potential tampering.

Flag Type: Boolean (Soft Delete)
Purpose: Marks the rule as deleted while preserving historical data.
Values:
- TRUE: Rule is soft-deleted and inactive
- FALSE: Rule is active or available
Usage: Maintains referential integrity for historical tracking data.

Flag Type: Boolean
Purpose: Controls whether the rule is currently active and enforceable.
Values:
- TRUE: Rule is active and being enforced
- FALSE: Rule is configured but not currently active
Usage: Temporary deactivation without deleting rule configuration.

Format: String
Purpose: Defines which web platforms this geo-fencing rule applies to.
Common Values:
- “ALL”: All web browsers
- “CHROME_ONLY”: Chrome browser only
- “FIREFOX_ONLY”: Firefox browser only
- “NONE”: Not applicable to web platforms
Usage: Browser-specific rule enforcement for web-based tracking.

Format: String
Purpose: Defines which mobile platforms this geo-fencing rule applies to.
Common Values:
- “BOTH”: Android and iOS
- “ANDROID_ONLY”: Only Android devices
- “IOS_ONLY”: Only iOS devices
- “NONE”: Not applicable to mobile platforms
Usage: Platform-specific rule enforcement.

Format: String
Purpose: Controls punch operations from outside geo-fence on mobile devices.
Common Values:
- “BOTH”: Allow both punch-in and punch-out
- “PUNCH_IN_ONLY”: Allow only punch-in from outside
- “PUNCH_OUT_ONLY”: Allow only punch-out from outside
- “NONE”: No punches allowed from outside fence
Usage: Flexibility for emergency or exceptional situations on mobile.

Format: String
Purpose: Controls punch operations from outside geo-fence on web platforms.
Common Values: Same as mobile configuration but for web interface.
Usage: Different flexibility rules for web-based attendance.

Format: Integer
Purpose: Maximum number of punch-in operations allowed per day under this geo-fencing rule.
Usage: Controls how many times an employee can punch-in within a single day.
Actual Data Examples:
- 0: No punch-ins allowed (restrictive)
- 1: Single punch-in per day (standard)
- 2: Two punch-ins allowed (for split shifts)
- 4: Multiple punch-ins (flexible schedules)
Business Logic: Prevents time theft and ensures proper attendance patterns.

Format: Integer
Purpose: Maximum number of punch-out operations allowed per day under this geo-fencing rule.
Usage: Controls how many times an employee can punch-out within a single day.
Actual Data Examples:
- 0: No punch-outs allowed
- 1: Single punch-out per day
- 2: Two punch-outs allowed
Business Logic: Must correspond with punch-in limits for valid attendance sessions.

Format: Integer
Purpose: Maximum total number of punch operations (both in and out combined) allowed per day.
Usage: Overall control on daily attendance transactions.
Actual Data Examples:
- 0: No punches allowed at all
- 2: One punch-in + one punch-out (standard day)
- 4: Two punch-ins + two punch-outs (split shifts)
Business Logic: Ensures total punches don’t exceed reasonable daily limits.