Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 7 of 357 synchronized guides.
Administer ERPat Field Service: Lite and Pro feature flags, the full permission set, the settings hub sub-tabs, notification events, the six per-tenant cron jobs, the AI-assist opt-in with data-privacy acknowledgement, and the client and end-user API stacks.
Standard operating procedures for ERPat Field Service: intake and triage requests, convert to work orders, schedule and dispatch technicians, execute jobs on site with tasks, photos, signature, parts and time, review and approve, quote, bill, and run the customer portal and offline app.
Troubleshooting and FAQ for ERPat Field Service: fix missing availability slots, parts not reducing stock, invoices that will not create, and AI assist that appears unavailable, plus a glossary of module terms and how to escalate to support.
Operator overview of the ERPat Field Service module: run the full service-to-cash lifecycle for on-site work — requests, work orders, dispatch, mobile execution, parts, quotes and billing — with a customer portal and an offline technician app.
Set up ERPat Field Service from zero: enable the module, run migrations, assign permissions, choose Lite or Pro, add service templates, skills and technicians with HR schedules, register customer sites and assets, and load the demo dataset.
Data and screen reference for ERPat Field Service: sidebar screens and routes, the work-order/request/assignment lifecycle statuses, the sixty fs_* data areas, cron jobs, dashboard widgets, the profile tab, system-log events, and both API endpoint lists.
The live Field Service module files inspected to write this guide: the 26 controllers, 61 models, 10 migrations covering 60 tables, 5 cron jobs, 15 config sidecars, 3 libraries, helpers, seeder and tests under modules/FieldService.