Configuration File Structure
The Field Service Management (FSM) config file is powerful and flexible but it can also get big and complex. Knowing the main sections helps you find settings faster, make changes, and connect the config to product features.
The config file has several key sections, each with a specific role in controlling FSM behavior.
|
Section |
Scope |
Features |
|---|---|---|
|
|
Controls app or server behavior of the mobile and scheduler |
Mobile app tabs, schedule board views |
|
|
Data sourcing, validation, record events |
Field mapping, auto-naming, default values |
|
|
NetSuite UI elements such as sublists and buttons |
Add Tasks sublist, field filters, custom button labels |
|
|
Email templates and service reports configuration, PDFs |
Case Service Report, Task Service Report, Project Task Service Report, and their email templates |
|
other sections |
Product automation, billing rules, global settings, miscellaneous features |
Preventative maintenance, billing rules, service reports, recurrence, custom business logic |
The routes Section
The routes section controls how FSM apps and services work, like the mobile app and the schedule board.
routes/scheduler
This section has all the config for the schedule board. It controls filters, color palettes, sorting, and which records show up as events or resources.
-
event– Sets which records show up as events. -
resource– Sets which records can be assigned as resources.
routes/mobile
This section has all the config for the FSM mobile app. It controls everything you see and do in the app, including which tabs or pages appear, their order, labels, and what data mobile users get.
-
event– Sets which records show as jobs on mobile. -
resources– Sets which tabs or pages you see in jobs. -
inventory– Shared data for every job. -
user– Data specific to each user. -
tabs– Sets up each mobile tab or page.
The models Section
Models define what data other parts of the config like views can use, and which fields that comes from or goes to. Models also set up things like auto-naming records when you save, and default values when FSM creates records, like cases for preventative maintenance. For example, if you want to update how asset data is sourced or checked, update models/asset.
The views Section
The views section controls NetSuite UI elements like custom sublists, buttons, and field filters. It doesn’t affect the mobile app or schedule board. For example, if you want to add a custom Add Tasks sublist to a case, edit views/case/tasks.
The notifications Section
This section manages email templates and PDF service reports. You can also set which templates to use for reports like Case, Task, or Project Task, and set up the content and recipients for automated emails. For example, if you want to update the template for the Task Service Report email, edit the right section in notifications.
Other Sections
Other sections covers global product features, automation, billing rules, and setting up automatic preventative maintenance cases and tasks. For example, if you want to change how preventative maintenance cases are made.