Field Service
Einsätze vor Ort
Wofür sie gedacht ist
Schedule on-site jobs for customers: who does the work, where, when, which parts were used and whether the customer must sign off. Site addresses and contacts are personal data and treated as such.
Was das Paket leistet und was nicht
On-site jobs for customers, done by a technician: scheduled, en route, in progress, done or cancelled. A job records the customer, the site, the technician, the planned day and start (minutes since midnight), the parts used and whether the customer must sign off. Site address and contact details are personal data. Needs the Human Resources and Products packages.
Modelle
field_service_job
An on-site job for a customer
Lesegruppe: field_service.user. Schreibgruppe: field_service.user.
| Feld | Art | Datenklasse | Personenbezogene Daten | Gruppe | Agenten sehen | Beschreibung |
|---|---|---|---|---|---|---|
name | text | none | nein | field_service.user | im Klartext | Short title of the job, for example Replace boiler pump |
customer_id | ref → party | none | nein | field_service.user | im Klartext | The customer the job is for |
site_name | text | none | nein | field_service.user | im Klartext | Name of the site, for example Main warehouse |
site_address | longtext | internal | ja | field_service.user | maskiert | Street address where the work is done; often a person's home |
site_city | text | internal | ja | field_service.user | maskiert | City of the site |
site_postcode | text | internal | ja | field_service.user | maskiert | Postcode of the site |
site_country | text | none | nein | field_service.user | im Klartext | Country of the site |
site_contact_name | text | internal | ja | field_service.user | maskiert | Name of the person to meet on site |
site_contact_phone | text | internal | ja | field_service.user | maskiert | Phone number of the person to meet on site |
technician_id | ref → hr_employee | internal | ja | field_service.user | maskiert | Technician assigned to the job |
priority | select (low, normal, high, urgent) | none | nein | field_service.user | im Klartext | How urgent the job is: low, normal, high, urgent |
description | longtext | none | nein | field_service.user | im Klartext | What has to be done and what the customer reported |
scheduled_on | date | none | nein | field_service.user | im Klartext | Planned day of the visit (YYYY-MM-DD) |
scheduled_start_minute | number | none | nein | field_service.user | im Klartext | Planned start in minutes since midnight (540 is 09:00) |
planned_minutes | number | none | nein | field_service.user | im Klartext | Planned duration in minutes |
signature_required | bool | none | nein | field_service.user | im Klartext | Whether the customer has to sign off the work before it counts as done |
signed_by | text | internal | ja | field_service.user | maskiert | Name of the person who signed off the work |
signed_on | date | none | nein | field_service.user | im Klartext | Day the customer signed off (YYYY-MM-DD) |
work_report | longtext | none | nein | field_service.user | im Klartext | What was done, written by the technician |
state | select (scheduled, en_route, in_progress, done, cancelled) | none | nein | field_service.user | im Klartext | Job status: scheduled, en_route, in_progress, done, cancelled |
field_service_part
A part or product used on a job
Lesegruppe: field_service.user. Schreibgruppe: field_service.user.
| Feld | Art | Datenklasse | Personenbezogene Daten | Gruppe | Agenten sehen | Beschreibung |
|---|---|---|---|---|---|---|
job_id | ref → field_service_job | none | nein | field_service.user | im Klartext | The job the part was used on |
product_id | ref → product | none | nein | field_service.user | im Klartext | The product that was used |
quantity | number | none | nein | field_service.user | im Klartext | How many units were used |
unit_price | money | none | nein | field_service.user | im Klartext | Price per unit charged to the customer (minor currency units, e.g. cents) |
note | text | none | nein | field_service.user | im Klartext | Remark about the part, for example serial number |
Workflows
field_service_job
| Aktion | Bewegt | Wer sie ausführen darf | Freigabe |
|---|---|---|---|
field_service_job.depart | state: scheduled → en_route | field_service.user | nein |
field_service_job.start | state: en_route → in_progress | field_service.user | nein |
field_service_job.complete | state: in_progress → done | field_service.user | nein |
field_service_job.cancel | state: scheduled → cancelled | field_service.manager | nein |
Berechtigungsgruppen
Von dieser App verwendete Gruppen:
field_service.managerfield_service.user
Freigabeschritte
Kein Schritt dieser App braucht eine Freigabe, abgesehen vom Löschen von Datensätzen.
Was Agenten tun können und was nicht
Ein Agent kann Datensätze dieser App lesen, durchsuchen, anlegen und aktualisieren sowie Aktionen ausführen, die keine Freigabe brauchen, und zwar innerhalb der Berechtigungsgruppen seines Tokens.
Diese Schritte kann er nur vorschlagen, und eine Person muss sie freigeben: field_service_job.delete, field_service_part.delete.
Personenbezogene Daten werden als Platzhalter maskiert: field_service_job.site_address, field_service_job.site_city, field_service_job.site_postcode, field_service_job.site_contact_name, field_service_job.site_contact_phone, field_service_job.technician_id, field_service_job.signed_by.
Abhängigkeiten
baseproducthr
Installation
Installieren Sie sie in der App Customize (Marktplatz) oder über die Kommandozeile:
obop modules install-from field_serviceErfordert eine Datenbank und Administratorrechte.
Selbst bauen
Der Modulleitfaden zeigt, wie Apps wie diese geschrieben werden