ScheduleScenarioSortInput
One ordering term for listScheduleScenarios. The first term drives keyset pagination (which always keys on createdAt); any further terms are applied as additional tie-breaking sorts.
Fields
Scenario attribute to order by.
Possible values (5)
NAMEOrder by the scenario's name column. Applied only as a tie-breaker: the list always keys its pagination on createdAt, and the first sort term contributes just its direction.
VERSIONOrder by the planner-assigned revision number, so successive revisions line up numerically. Tie-breaker only, on top of the createdAt keyset walk.
STATUSOrder by the stored status string, which sorts alphabetically (ARCHIVED, DRAFT, PUBLISHED, SIMULATION) rather than in lifecycle order. Tie-breaker only, on top of the createdAt keyset walk.
CREATED_ATOrder by when the scenario was first persisted — the column the keyset pagination itself walks, newest first unless the first sort term asks for ASC.
UPDATED_ATOrder by the timestamp of the most recent accepted mutation, bringing recently-touched scenarios together. Tie-breaker only, on top of the createdAt keyset walk.
ASC or DESC. On the first sort entry this also sets the direction of the keyset pagination walk; defaults to DESC when no sort is given.
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 listScheduleScenarios. The first term drives keyset pagination (which always keys on createdAt); any further terms are applied as additional tie-breaking sorts.
"""
input ScheduleScenarioSortInput {
"""Scenario attribute to order by."""
field: ScheduleScenarioSortField!
"""
ASC or DESC. On the first sort entry this also sets the direction of the keyset pagination walk; defaults to DESC when no sort is given.
"""
direction: SortDirection!
}