1. Field Service Management
  2. Field Service Management Administration
  3. Field Service Management Configuration
  4. Field Service Management Configuration Architecture

Field Service Management Configuration Architecture

Field Service Management (FSM) configuration has two layers:

The following sections explain how each layer works:

Core Product Configuration

Core product code controls the fundamental behavior of FSM. NetSuite installs the core product as a SuiteApp. SuiteApp object IDs include nx or fsm, and object names begin with Field Service.

The core product configuration comes with the product and is built into the core product code. Only the FSM product team can change it. Changes to the core code go to all accounts when they upgrade to the latest SuiteApp version.

The core product configuration runs independently in each account and adapts to that account's NetSuite features, preferences, and settings. Adapting to these account-specific settings makes each account's core configuration unique.

Custom Configuration

To review or modify the custom configuration, go to Field Service > Administration > Configuration.

When FSM is deployed in an account, FSM creates and activates an initial custom configuration. The default configuration supports common use cases and makes tasks and content available in FSM Mobile after deployment.

Modify the default configuration to meet account-specific business requirements.

Field Service Management Configuration Fundamentals

NetSuite stores custom configuration as JavaScript Object Notation (JSON) in the Field Service Configuration record.

FSM features are organized into modules. To modify a feature, add or update the relevant module in the configuration file. For example, the following entry adds configuration for FSM Mobile:

            {
  "routes/mobile": {}
}

Common configuration modules include:

Module

Purpose

views

Controls NetSuite user interface elements, such as custom sublists and buttons.

models

Controls data sourcing, validation, and record events.

routes/mobile

Contains configuration for FSM Mobile.

routes/scheduler

Contains configuration for the Schedule Board.

For example, the following entry adds configuration for the accounting module:

            {
   "accounting": {}
}

For details about the available configuration sections, see Configuration File Structure.

Related Topics

General Notices