User Event and Client Record Deployments
Field Service User Event handles beforeLoad, beforeSubmit, and afterSubmit. It selects the FSM handler for the record type. Field Service Client handles interactive form events, including initialization, field changes, and save checks. It can request server actions through the Suitelet.
The following table lists supplied User Event and Client deployments by record type.
|
Record |
User Event Deployment |
Client Deployment |
|---|---|---|
|
Project task |
|
|
|
Item fulfillment |
|
|
|
CRM task |
|
|
|
Field Service Consumable |
|
|
|
Subsidiary |
|
No supplied record-level deployment |
|
Service item |
|
No supplied record-level deployment |
|
Time bill |
|
|
|
Transfer order |
|
No supplied record-level deployment |
|
Field Service Configuration |
|
|
|
Field Service Asset |
|
|
|
Estimate (quote) |
|
|
|
Field Service Recurrence |
|
No supplied record-level deployment |
|
Case |
|
|
|
Sales order |
|
|
|
Expense report |
|
|
|
Customer |
|
No supplied record-level deployment |
|
Project |
|
|
|
Invoice |
|
|
|
Opportunity |
|
|
|
Employee |
|
|
|
Field Service Notification |
|
No supplied record-level deployment |
No dedicated User Event or Client deployment for the Field Service Error record appears in the supplied deployment definitions. Error capture and maintenance occur through the reporting and processing paths described in this reference.
These record deployments are supplied as Released, Deployed, and Audit. The deployments include all internal roles and the supplied NetSuite external center roles. User Event deployments use Field Service System (customrole_nx_system) as their supplied execution role. Event and context filtering, along with account permissions, still affect whether a handler runs. A broad audience does not establish that every handler runs on every operation.
Record Processing Associations
The following table links record topics to the scripts and processing results described in this reference.
|
Record Topic |
Scripts and Capabilities |
Result Evidence |
|---|---|---|
|
FSM Case Record |
Case User Event and Client deployments. Program, Recurrence, Status, Unbilled, Notification, and Consumable deployments. Generated case callbacks for related work. |
Case fields, child tasks, project or transaction links, and related records. A processing request or banner does not establish that all changes occurred. |
|
FSM CRM Task Record |
Task User Event and Client deployments. Time, Status, Time Zone, Recurrence, and Notification jobs. Related processing described after this table. |
Time bills, status and date changes, related records, and transaction results. A cleared request field alone can be insufficient. |
|
FSM Asset Record |
Asset User Event and Client deployments. Asset inheritance and location job. Generated callbacks for automatic project creation. Item Fulfillment scripts for transaction-based asset processing. |
Inherited child values, linked task and project task locations, and created or linked projects or assets, as applicable. |
|
Field Service Error Record |
Shared reporters in User Event, Suitelet, and Scheduled paths. Error maintenance deployment and deployment-specific error consumers. |
Captured context and consequences for affected work. This record does not indicate execution status or provide a universal error severity classification. |
CRM tasks can also be affected by asset and location, Program, Consumable, and related-work processing.
Examples of Record Processing Indicators
The following table links record information to processing. Full field definitions are provided in the record topics.
|
Record Information |
Associated Deployment |
Interpretation |
|---|---|---|
|
Case Update Unbilled ( |
|
Requests assessment of an FSM case for recalculation. Related errors can exclude the case. |
|
Case or CRM task Update Status ( |
|
Requests status assessment. The same field ID does not make case and task processing identical. |
|
CRM task Log Activities ( |
|
Requests activity-based Time processing. Clearing the request does not establish that a time bill was created. |
|
Case or CRM task Notification Pending ( |
|
Indicates pending notification assessment. Delivery is a separate result. |
|
Asset Update Location ( |
|
Requests propagation of relevant asset location changes to qualifying linked work. |
|
Parent and child asset values differ in configured inherited fields |
|
The inheritance assessor derives eligible work from the data comparison. No universal box indicates whether asset inheritance is running. |
|
CRM task Destroy ( |
|
Marks deletion work requested by the related-work mechanism. It does not establish that deletion finished. |