One stop's position in a stored route order (route sequence run). xMatix writes one entry per approved stop when it creates a run, and lists them on the run's Entries tab. Entries are not added or edited from the standard screens. A stop added to the route after the run was computed has no entry, so new plans place it after the ranked stops in authored order.
Fields
| Field | Label | Type | Required | What it does |
|---|
Rank | Rank | Number | | The stop's position in this order, starting at 1. |
RouteSequenceId | Route Sequence | Lookup → RouteSequence | | The run this position belongs to. |
Score | Score | Number | | Filled on Mostly Followed runs only: the number of started visits to this stop divided by the number of plans in the history used, rounded to two decimals. A value of 1 means the stop was visited on every plan; empty means the stop has never been visited. Optimized runs leave it empty. |
VisitRouteStopId | Route Stop | Lookup → VisitRouteStop | | The route stop being placed. A stop moved to another beat by Outlet Transfer keeps its entries in the old beat's runs. |
Actions
| Action | Label | Type | What it does |
|---|
Clone | Clone | ServerAction (Clone) | Create a copy of this record |
DeleteEntity | Delete | Delete | DeleteEntity |
DeleteHeader | Delete | Delete | DeleteHeader |
DeleteRow | Delete | Delete | DeleteRow |
EditEntity | Edit | Edit | EditEntity |
EditHeader | Edit | Edit | EditHeader |
EditRow | Edit | Edit | EditRow |
NewHeader | New | New | NewHeader |
