What the Program Feature Automatically Sets or Controls
The Field Service Management (FSM) Program feature uses the following records and fields:
|
Record |
Field |
Behavior |
|---|---|---|
|
Project |
Field Service Update Program |
When you check this box and submit the Project, it schedules the Program script (customdeploy_nx_program) to reconcile Cases and Tasks with your Program rules. After it finishes processing, the script clears the checkbox. |
|
Project |
Status |
NetSuite uses this status to decide whether to create or delete Program-generated work. See Project Status Field for the statuses that trigger Program processing and deletion behavior. |
|
Project |
Start Date |
The Program uses this to calculate the first Case date and the dates after that. Cases can't be created with a start date that's earlier than the Project Start Date.
Note:
The Start Date field is the default used by NetSuite. However, it's overridden by the Field Service Start Date field, if this is populated. |
|
Project |
End Date |
Sets the Project's cutoff date after which NetSuite won't create more Cases, unless you use the Field Service Program Create Until field. |
|
Project |
Field Service Start Date |
If populated, this field replaces the Start Date as the starting point for the first Case date. It's possible for the Field Service Start Date to be earlier than a Project's Start Date. This can be useful if you have a Program with alternating case types, and you want to change which case type is created first. See Reading the Program Subtab - Example 2. |
|
Project |
Field Service Program Create Until |
Used when the Project doesn't have an End Date to tell NetSuite how far ahead to create Cases. See Program Feature Minimum Requirements. |
|
Project |
Field Service Project Type |
Determines whether the Project can create a Program. See Program Feature Minimum Requirements. |
|
Project |
Field Service Time Zone |
NetSuite uses this field to set the time zone on generated Projects, Cases, and Tasks so they match the Asset's time zone. This can be important for reporting and if you work across multiple time zones. |
|
Case |
Type |
NetSuite sets this when it creates the Case. In the FSM configuration, it pulls this from case.type in program.projectrules for the matching Project Type. |
|
Case |
Details |
You can configure FSM to set this from Project data by mapping the Case Details field from the Project Comments field. |
|
Case |
Assigned |
You set this in the FSM configuration. |
|
Case |
Asset |
You can configure this to copy from the Project's asset field. |
|
Case |
Multi-asset field |
You can set this from a Project multi-select Asset field using projectmap and projectrules in the FSM configuration. |
|
Case |
Update Program |
If a Case has an associated Program, checking and submitting this field schedules the Program script to create any missing Tasks for the Case. After it runs, the script clears the checkbox. |
|
Task |
Type |
If configured, FSM creates Tasks under Program-created Cases and sets the Task Type from |
|
Task |
Assigned |
You can set this from Case-mapped data (casemap). |
|
Task |
Start |
You can set this from Case-mapped data (casemap). |
|
Task |
End |
You can set this from Case-mapped data (casemap). |
|
Task |
Skill |
You can set this from Case-mapped data (casemap) when NetSuite creates the Tasks. |
|
Task |
Priority |
You can set this on Program-created Tasks through configuration (for example, by mapping a Project or Case value to the Task). |
For more information, see Viewing the Program on a Project in NetSuite