Jobs
A jobJobA high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address. is the unit of work that everything else hangs off: every taskTaskA unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource., every appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. traces back to one. Jobs flow into Dime.Scheduler from the back office, so most days an administrator does not have to think about them - until a planner reports an address that won't geocode, a stale order that nobody planned, or a duplicate job nobody can find in the back office anymore. This page is where you sort those situations out.
Geocoding addresses
The biggest reason to come here is geocoding. A job without coordinates cannot show up on the map, and planners working with map-based dispatching depend on every relevant job being plotted. There are two ways to trigger geocoding:
- The Geocode All toolbar button runs across every job that does not yet have coordinates. It is the same routine that runs nightly to pick up new arrivals, so use it when you want results faster than waiting for the next nightly pass.
- Each row has a small geocode button that geocodes just that job. Reach for it when an individual job's address changed and you don't want to wait.
For the routine to produce sensible results, the address needs to be unambiguous. "Papa John's Pizza, Rome" could be the Italian capital or a small city in Floyd County, Georgia - the algorithm picks one and you may not like which. Use international conventions like ISO 3166 country codes; the localization view maps localized country names to their ISO equivalents to make this easier. Read more about geocoding.
Inspecting a job's tasks
Open a job's row to expand a side panel listing every open taskOpen taskA task that has not been scheduled yet. It waits in the open task list to be placed on the planning board. linked to it. From here you can sort, filter, and (covered below) delete tasks one by one - useful when you need to clean up a single task without disturbing the rest of the job.
Cleaning up jobs and tasks
Stale jobs and tasks accumulate: a back-office system imported an order that was later cancelled, a connector pushed duplicates during a migration, a customer reported the wrong job number. This page lets planners and administrators delete them directly, without having to go back to the source system.
Deleting jobs
- Select one or more jobs in the grid (checkboxes, multi-select supported).
- Click Delete in the toolbar.
- The toolbar switches to a confirmation strip. Optionally tick Also delete linked appointments to cascade the delete to every appointment backed by the selected jobs.
- Confirm.
With the cascade option on, appointments are removed in the background and a notification fires when the cleanup is done.
Deleting tasks
Tasks are deleted from the per-job side panel:
- Expand the job's tasks side panel.
- Select one or more tasks.
- Click Delete and confirm. The same Also delete linked appointments option applies.
Deleting jobs or tasks is permanent within Dime.Scheduler - the records are gone. If the data originated in a back-office system, however, the next sync may re-import it. For jobs that should stay gone, delete them at the source too.