Time Off Territory prerequisites and downtime data model
Key Takeaway
Before reps log time off, an admin activates the required trigger handlers, configures downtime categories, and configures business hours. Your organization's own time-off reasons go in Downtime Category, not in the restricted Downtime Type field.
Time Off Territory lets field sales reps block out time during normal business hours when they are away from their territory, such as vacation, sick days, or training. Each block is a Territory User Downtime record tied to a user and a territory, so the org can track time that is not spent on customer-facing activities. Before reps use Time Off Territory, an admin completes setup so that time off matches working hours and does not conflict with other scheduled activities.
The Territory User Downtime data model
The TerritoryUserDowntime object is available in API version 65.0 and later. A downtime record includes these fields:
| Field | What it holds |
|---|---|
UserId | The user who logs the downtime |
OwnerId | Polymorphic owner field that can point to a User or a Group |
TerritoryId | The rep's territory, a reference to Territory2 |
StartDate | Start date and time |
EndDate | End date and time |
SlotType | Morning, Afternoon, Evening, or AllDay |
DowntimeCategory | Picklist you extend with your own values |
DowntimeType | Restricted picklist with a fixed set of standard values |
SourceSystemIdentifier | The external record ID |
SourceSystemName | The name of the source system |
OwnerId and UserId are separate fields.
The Downtime Category (DowntimeCategory) and Downtime Type (DowntimeType) fields are different fields. The standard values of Downtime Type are:
- Civic Activity
- Disciplinary
- Holiday
- Personal Absence
- Training
- Unexcused
- Vacation
Because TerritoryId points to Territory2, each downtime record belongs to a territory from Enterprise Territory Management. Life Sciences Cloud territory management is integrated with Enterprise Territory Management. Territory downtime is one of the territory-related data model objects in Life Sciences Cloud territory management.
The two source system fields support downtime records imported through data integrations.