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.
Where it lives
Field Service → Form Templates.
Key attributes
- Template Name and Description
- Request Type — Installation, Repair, Maintenance, Inspection, Emergency, or Other. This is what a service request's own Request Type is matched against when offering templates to pick from.
- Default Template — a checkbox; Active — a switch to retire a template without deleting it
- Sections, each with a Title and a list of Fields
Each field has:
- A Name
- A Type — Text, Number, Date, Dropdown, Checkbox, Text Area, Signature, or Photo
- Required
- A Default Value
- An optional Auto-populate source — see below
Building a template
Click Add New, name the template, and pick a Request Type. If the template has no sections yet, choosing a Request Type loads a ready-made starter set of sections for that type, which you can edit freely — rename sections, add or remove fields, or add whole new sections with Add Section. Mark it Default Template if it should be offered first for its request type.
Auto-populate
A field can be set to pull its value from data already on the service request instead of asking the technician to retype it — options include the service address (full address, contact name, phone, email, or individual address lines), the customer's name, the asset's name, the service request's number or description, or the assigned workforce member's name, phone, or email. An auto-populated field is read-only by default, so it shows the pulled value but isn't accidentally overwritten.
How templates connect to requests
On a Service Request's Form Template field, only templates matching that request's Request Type are offered. Once one is selected, a Form tab appears on the request showing that template's sections and fields for the technician to fill in.