Ordering Activities in the Route
Activity-related commands deal with ordered and not-ordered activities.
Not-Ordered Activities can be completed at any time of the day and appear at the top of the list in the GUIs, and can be started at any time. Relative order of not-ordered activities is not significant.
(If activity is uploaded through the Inbound API and its service window time is not specified in the transaction, it becomes unordered. The 'unordered' flag can be set by the user through Manage when either creating a new activity or updating an existing one. Then even if a service window is set in the Inbound Interface, the activity will stay unordered).
Ordered Activities should be started within the period defined with the service window start and service window end values. In the GUIs, earlier activities are higher in the list.
Activities are ordered in the resource's route (activity ordering is not significant for buckets):
by service window end values
if they are the same, activities are ordered by the service window start values
if they are the same, activities are ordered by their SLA window end values
if they are the same, activities are ordered by their SLA window start values
if they are the same, activities are ordered by the activity ID
When a route contains ordered finish-to-start linked activities, such links have higher priority in the activities ordering than any other criteria. The activities are ordered according to their sequence in the link and afterwards the service window, SLA and ID are checked.
Here is an example of correct ordering by the activity service window:
| Number | Service Window Start | Service Window End |
|---|---|---|
1 |
8:00 |
10:00 |
2 |
10:00 |
11:00 |
3 |
8:00 |
12:00 |
4 |
10:00 |
12:00:00 |
When activities are updated, they are again reordered by the same criteria, if necessary.