Request Templates
A Form Template defines the fields a technician fills out on a service request — an installation checklist, a repair report, a maintenance inspection, and so on — so the same kind of job always collects the same information, including photos and a customer signature.
Where it lives
Field Service → Form Templates. The list shows each template's name, request type, number of sections, whether it's the default, and whether it's active.
Key attributes
- Template Name (required) and Description
- Request Type — Installation, Repair, Maintenance, Inspection, Emergency, or Other. Service requests are offered only templates of their own type.
- Default template for its request type — new requests of that type pick this template automatically
- Active — switch it off to retire a template without deleting it
- Sections, each with a Section Title and a list of fields
Each field has a Field Name, a Field type, a Default value, a Required flag, and an optional Auto-populate source.
| Field type | What the technician gets |
|---|---|
| Text | A single-line box |
| Number | A numeric box |
| Date | A date picker |
| Dropdown | A select list of the options you enter |
| Checkbox | A single tick box |
| Text Area | A multi-line box |
| Signature | Capture signature, which opens a pad to sign on |
| Photo | Take or upload photo |
Building a template
Create a new template, enter a Template Name, and pick a Request Type. On an empty template, picking a type fills in a ready-made set of starter sections for that type — site information, equipment details, checklists, completion, and so on. Once the template has sections, changing the type leaves them alone.
Edit freely from there: Add section and Add field, set each field's type and options, and drag the handles to reorder sections and fields. For a Dropdown, type each choice into Dropdown options and press Enter. Use Preview form to see it exactly as a technician will, then save.
A template won't save while a dropdown has no options, or while two fields anywhere in the template share the same name — answers are stored by field name, so each one must be unique.
Auto-populate
A field can take its value from the service request instead of being typed:
- Service Address — the full address or its parts, and the site contact's name, phone, and email
- Customer — the customer's name, email, and phone, and the company name from the site
- Asset — the asset's name
- Service Request — the request number, description, requested date, and scheduled date
- Workforce — the assigned technician's name, phone, and email
While the source has a value, the field shows it read-only; when the source is empty, the field can be typed into. When the request is saved, auto-populated values and defaults are stored with the answers, so the technician's copy and the printed form both show them — and if you change the customer or address and save, the stored answer follows.
How templates connect to requests
When you create a request, the default template for its type is picked for you (or the only active template of that type, if there's no default). Changing the request's type switches to that type's default. You can also choose a template under More on the new-request screen, or on the request's Overview tab.
Once a template is chosen, a Form tab appears on the request with its sections and fields. Required fields must be filled in before the request can be completed.