Operations
Planner service
Staff or fleet service pending coverage, or already covered.
Schemas: PlannerServiceDto
Example
Generated from the schema
A staff or fleet service of an order that is pending coverage or already covered. When staffMemberId and vehicleId are null the service is uncovered. The identifier you use to assign it is orderServiceId, not an id. List the services of a date window with GET /api.
Attributes
Service line identifier. It is the one passed when assigning.
Which row this is. A service comes as ONE summary row (the service itself, with staffMemberId and vehicleId always null) plus one detail row per person or vehicle assigned to it, all with the same orderServiceId. A service is covered when it has detail rows with an assignee, and uncovered when it only has the summary row.
Available options: summary, detail
Order the service is attached to; an empty string on internal services, which belong to no order.
Human-readable number of that order; an empty string on internal services.
Order status.
Customer of the order; null if not recorded.
Associated project; null if not applicable.
Project name; null if not applicable.
Catalogue service it comes from.
Service name.
Type: crew, fleet or general.
Assigned staff member. Only detail rows carry it; it is null on the summary row even when the service is covered.
Assigned vehicle. Only detail rows carry it; it is null on the summary row even when the service is covered.
Service start in ISO 8601 UTC.
Service end in ISO 8601 UTC.
Service line status.
How many units of the service are requested.
Linked schedule task; null if there is none.
Resources needed to cover it.
Show child attributesHide child attributes
What is needed: personnel or vehicle.
Available options: personnel, vehicle
How many are needed.
Values
- rowKind
summary,detail
Returned by
GET /api/v1/planner/services— List the services to cover
Modified by
No operation.
Was this page helpful?