Big Locations

When operating with large volumes of service objects, the amount of work is usually split across several days and resources. During the split, all itemsPlanned are automatically copied onto each task of the split task group. OMD supports the definition of the process flow preference bigLocation allowing mobile workers to close such a task without having to confirm or cancel each individual itemsPlanned. On the other hand, all copies of a processed service object will be removed from the other tasks in the split task group to avoid double processing of the same service object. In case the last task with copies of service objects was closed with a set of unprocessed service objects, OMD will automatically create an unplanned new task with the original identifier and a random BL_ postfix holding the orphans. At the end, all service objects are processed or cancelled and no copy should exist anymore.

Note that this mechanism requires all service objects to be part of an initially uploaded single task. It is different from a scenario where each service object is represented by a single task. In the latter case, a service object needs to be rebooked when a collection of tasks was opened and the service object of the lead task is returned back to the planner.