Merging Core Product and Custom Configuration
At runtime, Field Service Management (FSM) merges the core product configuration with the custom configuration. The custom configuration can override or extend default FSM behavior.
Keep only one custom configuration file active. Mark all other configuration record inactive.
Configuration Merge Behavior
When you add a custom configuration, understand how the merge logic works.
Objects
In JavaScript Object Notation (JSON), an object contains properties enclosed in braces ({}). Objects such as element, article, or map are merged property by property. Only the properties in your custom configuration override the corresponding core product configuration properties.
Copy only the properties you want to change into your custom configuration. This helps future product updates apply correctly and makes your customizations easier to identify.
Arrays
Arrays are values enclosed in square brackets ([]). Arrays such as filter and item are not merged. If you override an array, the custom configuration replaces the entire base array. If you add only a new value, the default behavior is removed. Copy the complete base array from the core configuration, and add your changes.
Configuration at Runtime
At runtime, the configuration JSON merges with the core product code to control how FSM works. The core product code always runs, and the custom configuration merges with it.
If there's no custom JSON, FSM runs using the core product behavior.
The Configuration Preview feature lets you view the runtime configuration in your account. For more information, see Configuration Preview.
For related information, see the following topics: