ScheduleAllocationSortInput
One ordering term for listScheduleAllocations.
Fields
Which allocation field to order by.
Possible values (3)
START_ATOrder by the booked start time, i.e. the scenario's own timeline order. This is the key the pagination walks and the default when no sort term is given.
END_ATOrder by the booked finish time, which diverges from START_AT order wherever allocations overlap or run for unequal lengths.
CREATED_ATOrder by when the allocation row was first booked rather than where it sits on the timeline — the way to see what a planner or the optimizer added most recently.
ASC for earliest-first, DESC for latest-first.
Possible values (2)
ASCSort in ascending order (A-Z, oldest first)
DESCSort in descending order (Z-A, newest first)
Referenced by (1)
Exact type SDL
"""One ordering term for listScheduleAllocations."""
input ScheduleAllocationSortInput {
"""Which allocation field to order by."""
field: ScheduleAllocationSortField!
"""ASC for earliest-first, DESC for latest-first."""
direction: SortDirection!
}