tbl_geofencingrulenotification

-1 rows


Description

Module: HRMS Geo-fencing Module
Purpose: Defines notification rules and recipients for geo-fencing events, enabling targeted alerts for boundary violations, idle time, GPS status changes, and other location-based events.
Data: Each row represents a specific notification configuration that determines who gets notified, how they get notified, and for what type of geo-fencing event.
Process Usage:
- Configures alert recipients and delivery methods for geo-fencing rule violations.
- Supports different notification types (email, SMS, push) and event categories.
- Enables targeted notifications to specific employees or roles for different event types.
Key Points:
- Multi-channel notification support with configurable delivery methods.
- Granular event type classification for precise alert targeting.
- Flexible recipient assignment (specific employees or role-based).
Business Impact: Ensures timely awareness of location compliance issues, enables quick response to attendance anomalies, and provides comprehensive monitoring of field workforce movements.

Columns

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

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for each notification configuration.
geofencingruleid int8 19 null
tbl_geofencingrule.geofencingruleid fk_tbl_geofencingrulenotification_geofencingruleid R

FK: public.tbl_GeoFencingRule.geofencingruleid
Purpose: Links this notification configuration to its parent geo-fencing rule.
Cardinality: Many-to-One (multiple notifications per geo-fencing rule)
Usage: Associates notification settings with specific geo-fencing rule events.
Business Logic: Notifications are triggered when their parent geo-fencing rule conditions are met.
notificationtype varchar 100 null

Format: String (from GeoFencingRuleNotificationConstant.NOTIFICATION_TYPE)
Purpose: High-level categorization of the notification event type.
Common Values:
- “BOUNDARY_VIOLATION”: Employee moves outside geo-fenced area
- “IDLE_TIME”: Employee remains stationary beyond tolerance
- “GPS_STATUS”: GPS turned on/off during working hours
- “PUNCH_VIOLATION”: Punch operation violates geo-fencing rules
- “COMPLIANCE_ALERT”: General compliance issue detected
Usage: Determines which events trigger this notification.
notificationsubtype varchar 100 null

Format: String (from GeoFencingRuleNotificationConstant.NOTIFICATION_SUB_TYPE)
Purpose: More specific classification within the main notification type.
Common Values:
- For BOUNDARY_VIOLATION: “ENTER”, “EXIT”, “DWELL_OUTSIDE”
- For IDLE_TIME: “STATIONARY_START”, “STATIONARY_END”, “EXCESSIVE_IDLE”
- For GPS_STATUS: “GPS_ON”, “GPS_OFF”, “SIGNAL_LOST”
- For PUNCH_VIOLATION: “OUTSIDE_PUNCH_IN”, “OUTSIDE_PUNCH_OUT”, “MISSING_PUNCH”
Usage: Provides granular control over which specific events trigger notifications.
sendtype varchar 100 null

Format: String (from GeoFencingRuleNotificationConstant.SEND_TYPE)
Purpose: Defines how the notification should be delivered to recipients.
Common Values:
- “EMAIL”: Send via email
- “SMS”: Send via text message
- “PUSH”: Send via mobile push notification
- “IN_APP”: Show notification within application
- “MULTI_CHANNEL”: Send via multiple channels simultaneously
- “ESCALATION”: Escalate to higher authorities after certain conditions
Usage: Controls the delivery mechanism for different urgency levels and recipient preferences.
employeeid varchar 500 √ null
tbl_employee.employeeid fk_tbl_geofencingrulenotification_employeeid R

FK: public.tbl_employee.employeeid
Purpose: Identifies the specific employee who should receive this notification.
Usage Scenarios:
- Direct manager notifications for their team members
- HR notifications for compliance issues
- Employee self-notifications for their own violations
- Security team for boundary breaches
Business Logic: NULL value might indicate role-based or system-wide notifications.
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_geofencingrulenotification_geofencingrulenotificationid Primary key Asc geofencingrulenotificationid

Relationships

Close relationships within degrees of separation