-
Notifications
You must be signed in to change notification settings - Fork 0
Route Tasks
jperl edited this page Apr 26, 2012
·
4 revisions
The task board displays all of the Route Tasks for a day based on the GetRouteTasksForDaySQL function logic:
- A RouteTask is generated for each service for that day (that is not yet in Route) -FUTURE: Eventually the user will be able to define Route Task generation logic
- Any RouteTasks from previous days** that are On Hold will generate a Task
- FUTURE Any RouteTasks from previous days** that are not in Routes and not Cancelled or Completed will generate a Task**
**RouteTasks from previous days only include RouteTasks without a delayed child (where DelayedChildId == null)
When a RouteTask is generated from a delayed RouteTask. The parent will have it's DelayedChildId set:
A. The GetRouteTasksForDaySQL returns ParentRouteTaskId
B. Task has an extension class with a DelayedParentId property (not stored in the database) that is set when it is created in the dispatcher
C. InsertRouteTask/UpdateRouteTask, sets the DelayedChildId for the DelayedParent (stored in the database) if the DelayedParentId!=null
D. DeleteRouteTask is not possible for past Routes (route tasks)