Capturing FSM Performance Data
As an administrator, you can capture browser activity to review Field Service Management (FSM) performance. Capture the initial page load in FSM Mobile or the Schedule Board to record requests for the current view and configuration.
The capture produces an HTTP Archive (HAR) file containing recorded requests and responses, including available timings and returned data. Keep the HAR file with a capture note and configuration files so you can review the loading activity in context. You can examine these files with an implementation partner or an approved analysis tool.
Prepare the capture, record the initial page load in your browser, and collect the supporting information for review.
Preparing the Capture
Open FSM Mobile or the Schedule Board for the relevant person and role. Keep the normal browser and connection settings, and leave the normal custom configuration active.
Do not clear site data or reset FSM Mobile to prepare a capture. These actions can place pending work at risk. Before reloading the Schedule Board, save or cancel proposed scheduling changes through your normal process.
The following table describes when the initial load is complete and which application details to record.
|
Application |
Loading Completion |
Session Details |
|---|---|---|
|
FSM Mobile |
The initial jobs and supporting data have loaded, and you can use the application. |
Technician and role, approximate job count, online or offline state, and whether the session is a reload or first use. Identify captures from an administrator's FSM Mobile emulator. |
|
Schedule Board |
The initial resource rows and work have loaded, and you can use the Schedule Board. |
Dispatcher and role, view and dates, visible resource rows, and panel filters. |
Create a capture note to keep with the HAR file. Record the date and time, browser, device, connection, and approximate loading duration. Describe the loading behavior, visible result, and expected result. Include the session details from the table.
A desktop or emulator capture represents that session. It does not establish performance on another device or in an installed FSM Mobile app.
Recording the Initial Page Load
You should use Chrome or Safari for this capture. Microsoft Edge is an additional option when Chrome or Safari is not practical.
Open the browser's inspection tools and click the Network tab before reloading the page. Requests completed before the tools open may be missing. If you reload the page first, reload it again with Network open.
The procedures use All request types with script in the text filter. This combination focuses the list on NetSuite service traffic and retains the page response and later data requests. Keep All selected because restricting the capture to Fetch/XHR can omit part of the Schedule Board's initial load.
The Schedule Board refreshes data automatically. Save the HAR file promptly after the initial load, before the next automatic refresh where possible. Stop recording first if the browser provides that control. If a refresh overlaps the initial load, keep the capture and record the refresh activity in the capture note.
For the capture procedure, see the topic for your browser:
After saving the capture, see Preparing FSM Performance Data for Review.
Capturing a Specific Activity
After the initial-load capture, you can record a separate activity for more detail. Examples include opening an FSM Mobile tab, changing Schedule Board dates, or scrolling to different resources.
Prepare Network with the same settings, clear only the request list, and perform the activity instead of reloading the page. Describe the action in the capture note. If you record a save, include the visible outcome. A HAR file alone cannot confirm that every related NetSuite update completed.
Additional Information
- FSM Configuration Record
-
Preparing for FSM Configuration Maintenance
-
Reviewing Custom FSM Configuration