Preparing FSM Performance Data for Review
Prepare the HAR file, capture note, and configuration files so you can review the recorded activity in context.
Validating the Capture
Reopen the saved file with Network's Import HAR or Import control and confirm that request rows appear. You do not need to examine each request.
Record the capture filters in the capture note, including the script filter. Totals in a filtered capture cover only the retained requests.
For an empty or incomplete capture, record the limitation with the file:
-
If the request list was empty during recording, clear the text filter and select All to check that requests were recorded. Record any filter changes.
-
If loading does not finish, export the available data and record when you stopped waiting. Unfinished requests or response data may be missing. Save any later completed capture separately.
HAR files and configurations can contain credentials, session keys, personal information, and business data. Chrome and Edge's sanitized export removes some sensitive headers, but other sensitive content can remain. Do not assume that Safari exports are sanitized. Use an approved review and redaction process before sharing files with another person or an approved AI tool. Keep the original files protected.
Collecting Supporting Information
Keep account, version, session, and configuration details with each HAR file, including when you collect several captures together. The following table lists the information needed to interpret each capture.
|
Capture Detail |
Information to Record |
|---|---|
|
Account |
Account name and exact NetSuite account ID where the activity was recorded. |
|
Account Type |
Production or sandbox account. For a sandbox account, include the exact sandbox account ID and its name or number, such as SB1 or SB2. |
|
NetSuite version |
NetSuite release running in the account. Record this separately from the FSM version. |
|
FSM version |
Installed FSM version at the time of capture. |
|
Application and session |
FSM Mobile or Schedule Board, person and role, loading behavior, expected result, and visible result. Include the application details from Preparing the Capture. For an activity capture, identify the action. |
|
Capture conditions |
HAR file name, date and time, time zone, browser, device, connection, filters, loading state, and approximate elapsed time. Identify unfinished loading or missing data. |
|
Configuration identity |
Active configuration record name or ID and the date the configuration files were collected. Identify configuration changes between file collection and the recorded activity. |
For instructions on collecting configuration files, see FSM Configuration Maintenance. The comparison requires the unmerged custom configuration and the account's clean base-product Preview, which contains standard settings without customer overrides.
Capture the HAR file with the normal custom configuration active. Follow the precautions in FSM Configuration Maintenance when collecting the clean base-product Preview and restoring the normal configuration.
Keep the HAR file, capture note, and configuration files together. Use files from the same account, account type, and FSM version. Identify any differences in file source or collection date.
Reviewing and Comparing Captures
Continue with FSM Configuration Maintenance for the assessment, proposed changes, and testing process. Before starting the review, confirm that the HAR file opens and that account details, versions, and supporting files are recorded and identified.
For a comparison capture, repeat the same loading activity with comparable sessions and roles, data, device, and connection. Record the configuration version used for each capture. For the Schedule Board, retain comparable dates, visible resources, and filters. Label each HAR file separately to keep results from different sessions distinct.
Additional Information
- FSM Configuration Record
-
Preparing for FSM Configuration Maintenance
-
Reviewing Custom FSM Configuration
-
Preparing FSM Configuration Changes