Field Service Management Configuration File Hierarchy

The configuration file consists of objects enclosed in braces ({ }). An object can contain other objects, which creates a hierarchy.

The following example shows objects at different levels of the hierarchy:

          {
  "config": {
    "preview": true
  },
  "routes/mobile": {
    "import": {
      "file1": "filename"
    }
  }
}

In this example:

config and routes/mobile are sections at the same level inside the complete configuration object.
preview is inside the config object.
import is inside the routes/mobile object.
file1 is inside the import object.

Place each configuration change in the correct section of the hierarchy. Changes outside the expected section don't work as intended.

After you update the configuration file, verify your changes in the Preview text area next to the Editor text area. If a change doesn't appear in the expected section, confirm its location in the hierarchy.

Related Topics