Time Clock: Job Targeting Modes for Geofences

Geofences can now target jobs by mode. A geofence can apply to every job on a time clock, only to a specific list of jobs, or to every job except a listed set — and the "except" mode keeps covering jobs added to the time clock later.

What's New

• Updated guide: Geofences — new Job Targeting section, an anyExcept create example, and jobIdsMode added to the property, request-body, and response tables

Key Improvements

• jobIdsMode on create and get: Create geofences accepts jobIdsMode, and both Get geofences and Get geofence return it. Allowed values are any, specific, and anyExcept. The default is specific, so existing integrations are unaffected.
• any: the geofence applies to every job on the time clock. Pass an empty jobIds array; the field is ignored.
• specific: the geofence applies only to the jobs listed in jobIds. This is the previous behavior.
• anyExcept: the geofence applies to every job on the time clock except those listed in jobIds, including jobs created after the geofence. No follow-up call is needed when a new job is added.
• Validation: jobIds is still capped at 100 entries, must contain parent job IDs only, and must reference jobs on the time clock in the path. The "Job IDs are required based on the account configuration" error applies only in specific mode — any and anyExcept are accepted with an empty jobIds.