FSM Job Safety Record
A Field Service Job Safety record stores a safety assessment associated with service work. It is a Field Service Management (FSM) custom record that holds the assessment outcome, notes, the person recorded as completing the check, and signature content. Its supplied relationships identify an asset and a customer relationship management (CRM) task.
Your account's forms and FSM Mobile configuration determine which assessment questions you see and which values you must enter. Creating a Job Safety record doesn't make a safety assessment required for every service visit.
Record Information
Use record and field IDs when working with searches, mappings, and integrations. Account labels can differ from the supplied English labels.
The following table summarizes the supplied record information.
|
Property |
Value |
|---|---|
|
Record type |
FSM custom record |
|
Record name |
Field Service Job Safety |
|
Record ID |
|
|
Record identity |
NetSuite Internal ID ( |
|
Supplied NetSuite form |
Field Service Job Safety ( |
The record ID identifies the custom record type for record operations and searches. An FSM Mobile resource ID or tab label identifies the record's configured presentation. Neither replaces the record type ID. The word Job in this record's name refers to service work, not the native NetSuite project record type (job).
Forms
FSM supplies the Field Service Job Safety entry form (custform_nx_jobsafety). The supplied form is marked as preferred, with the Store Form with Record box checked. With Store Form with Record checked, NetSuite retains the form used to create a record. NetSuite uses that form when the record is viewed or edited. Account form and role choices can affect the form used for entry. For native selection and storage behavior, see Custom Entry Form Properties.
The supplied form groups Asset and Task under related records and presents Safety Check Outcome, Safety Check Notes, Completed By, and Signature as service details. These FSM fields are optional on the supplied form. Account-created forms can present additional custom assessment fields or impose different requirements.
When an FSM Mobile resource generates elements from a NetSuite form, it uses the form's field definitions and applicable initial values. Generating these elements is separate from retaining a NetSuite UI form with a saved Job Safety record. Resource mappings determine which values are read or saved. Displaying a question alone doesn't create a field to store its answer.
For form selection, generated fields, and overrides in FSM Mobile, see Form Properties. For element types and validation, see FSM Mobile Element Reference.
Record Relationships
The supplied relationships are stored on the Job Safety record. Each single-selection field can reference one related record. Several assessments can reference the same asset or CRM task.
|
Related Record |
Relationship and Field ID |
Purpose |
|---|---|---|
|
Asset |
Job Safety Asset ( |
Identifies the equipment or site assessed. This is a reference, not an asset hierarchy relationship. |
|
CRM Task |
Job Safety Task ( |
Associates the assessment with a service visit and supports the Job Safety child sublist on the supplied FSM Task form. |
|
Employee |
Job Safety Completed By ( |
Identifies the person recorded as completing the safety check. It is separate from the task's assignee and team. |
The Job Safety record has no supplied direct case, customer, project, or project task field. A linked CRM task can provide further service context through its own relationships. A CRM task associated with a project remains a CRM task, not a project task.
The supplied Task relationship specifies that its value is cleared when its parent task is deleted. This doesn't define a cascade that deletes the Job Safety assessment. Account scripts and workflows can impose additional deletion behavior.
An account can add custom relationships, but a custom link doesn't automatically provide FSM inheritance, visibility in FSM Mobile, history, report inclusion, or synchronization. For the linked records' own data and relationships, see FSM CRM Task Record and FSM Asset Record.
FSM Fields
The following table lists the seven supplied custom fields and the native External ID field used by FSM. The supplied record definition provides no fixed initial selections or values for the custom fields.
|
Field |
Field ID |
Purpose |
Values and Behavior |
|---|---|---|---|
|
Asset |
|
Identifies the asset assessed. |
Selects one asset. This value is separate from the Asset field on the CRM task. |
|
Task |
|
Identifies the related CRM task. |
Selects one task as the parent record. |
|
Safety Check Outcome |
|
Records the assessment result. |
Selects from Field Service Pass Fail ( |
|
Safety Check Notes |
|
Stores notes about the safety check. |
Text Area field, distinct from native User Notes and System Notes. |
|
Completed By |
|
Records the employee associated with the completed check. |
Stores an employee reference. The field alone doesn't establish who entered or synchronized the record. |
|
Signature |
|
Stores signature content associated with the safety check. |
Rich Text field. A configured FSM Mobile form can present it as a signature element. Stored signature content is separate from the task's completion state. |
|
Idempotency Key |
|
Retains the older custom creation-identity value for compatibility. |
Current standard FSM Mobile record creation uses native External ID instead. This field is not a safety result or processing-completion indicator. |
|
External ID (native) |
|
Stores the record's external identity, including the creation key used when FSM Mobile follows the standard synchronization path. |
FSM stores its FSM Mobile creation key with the |
For current creation identity and duplicate-request handling, see FSM Mobile Duplicate Creation Protection. No supplied Job Safety field indicates that a script is running or that all assessment data has synchronized.
Creation and Update Sources
The following table describes how assessments can be created or updated.
|
Source |
Record Effect |
|---|---|
|
NetSuite entry |
Creates or edits an assessment using the applicable form and permissions. The supplied Task form can display linked assessments through its Job Safety sublist. |
|
Configured FSM Mobile resource |
Can create or update mapped assessment values when the resource targets |
Saving locally in FSM Mobile is separate from successful synchronization with NetSuite. Initial values for Completed By, Asset, and Task depend on the applicable form, resource defaults, mappings, and account rules.
Used by FSM Features
The following table summarizes the FSM capabilities that use this record.
|
Feature or Capability |
Record Use |
|---|---|
|
Configured FSM Mobile safety assessment |
Holds the mapped results of the configured assessment. Shared form and element configuration determines its presentation and requirements. |
|
Uses External ID to recognize an earlier creation when the resource uses standard record synchronization. |
Record Constraints and Data Requirements
All seven supplied custom fields are optional in the record definition and supplied form. A customized form, FSM Mobile validation, or an account script can require additional data. Requirements configured for an FSM Mobile resource don't automatically apply to all NetSuite records of this type.
The Task link doesn't impose a one-assessment-per-visit limit. Article-count limits in FSM Mobile control the configured resource and don't establish a database-wide uniqueness rule.
Safety Check Outcome and Signature describe assessment data. Neither value alone confirms that the CRM task or a required FSM Mobile resource is complete, or that work may proceed. These outcomes depend on the relevant workflow and validation rules.
Linking an assessment to a task or asset doesn't automatically add it to a service report. Report data selection and the template must include the assessment. For report behavior and setup, see FSM Service Reports and Notifications.