Absence
An absence: the period an employee was away from work, booked for them by HR.
- Summary view
- AbsenceList, 10 fields. What a list returns by default.
- Detail view
- Absence, 10 fields. The default for a single read and for every write.
- Read with
- api:
read: andabsences::absences manage - Write with
- api:
write: andabsences::absences manage
An absence with no end is still running and reaches through now everywhere it is read, so planning capacity and reporting both keep counting it until someone closes it. The free-text note absences once carried was purged as health data and is not exposed here.
Used by
Fields
- Detail only
- Only in the detail view.
- Only with include
- Only when you ask for it with include.
- Server-assigned
- Set by plnnrly, never by a request.
The employee this absence is for. Writing it requires the absences::manage permission.
The employee the absence is for. Renders as an {"id": N} reference unless expanded, and stays a reference when the employee has since been deleted.
Manager who filed or approved the absence, or null when none was recorded. The foreign key nulls on delete, so removing the manager leaves the absence behind unattributed.
The manager who filed or approved the absence; absent when none was recorded.
When the absence ends, or null while it is still running. An ongoing absence reaches through now everywhere it is read (planning capacity and reporting both count it), and that reach is uncapped, so an absence nobody closed keeps consuming capacity. RFC 3339 UTC.
Variants
AbsenceList 10 fields
What a collection returns, and what ?view=summary returns on a single record.
The same fields as the detail object.
AbsenceSummary 3 fields
The embedded form: what you get when another resource carries this one and you did not include it.
Leaves out: user_id, user, manager_id, manager, created_at, updated_at, links
AbsenceLinks 1 field
The links object on this resource.
Keys: self
Something wrong or missing on this page? Tell us