How does moving activities work?
When you identify an activity or a group of activities that are in jeopardy, you can move the activities to another resource or a bucket for re-assignment at a later time. To move an activity that's En route, you must stop the travel, change its status to Pending, and then move it.
You can move activities from three different locations in the interface:
List view: You can move one activity or multiple activities at once. The application proposes resources that might be a good match for the activity. You can also choose where a new activity fits in the new resource’s schedule.
Time view: From this view, you can drag an activity from one resource to another. You can move only one activity at a time. The application chooses the best time in the resource’s schedule and automatically moves the job to that time slot.
Map view: From this view, you can drag an activity from one resource to another. You can move only one activity at a time. The application chooses the best time in the resource’s schedule and automatically moves the job to that time slot.
-
A resource called in sick and you've already assigned a route to the resource.
-
A resource is assigned activities that might place them in an overtime situation.
-
An activity is in jeopardy after routing.
-
A resource requested a particular day off, but the calendar doesn't reflect it as a non-working day and a route has already been assigned to the resource.
If you try to move 1000 and more activities at once from a bucket to a resource, the Activity Details page may not open from the Dispatch Console or the Routing Report page. Oracle Fusion Field Service Core Application dowloads information about recently moved activities to the mobile device.
The best practice is to move not more than 100 activities at once from a bucket to a resource's route.