FSM Task View Configuration
This reference is intended for administrators and developers who configure task naming, service report controls, and Assigned field behavior.
This topic includes the following sections:
Automatic Task Naming
The views/task/autoname configuration prepares the CRM Task title for automatic naming when the Task model has an automatic-name mapping. Selecting a Field Service Task Type on an editable form prevents manual entry and supplies the temporary To Be Generated value. Clearing the type restores manual entry and the earlier name where available. Relevant noninteractive saves can also receive a temporary name.
The following table describes the hidden property for the Task naming component.
|
Property |
Accepted Value |
Standard Default |
Effect |
|---|---|---|---|
|
|
Boolean value. |
|
Turns off this name-field component. |
The Task model controls the generated name, and the view doesn't provide a naming template. Hiding this component doesn't turn off model naming. For automatic naming configuration, see FSM Record Model Configuration.
Complete Standard Object
This object shows the complete declared standard defaults.
{
"views/task/autoname": {
"hidden": false
}
}
CRM Task Service Report Button
The views/task/servicereport configuration adds the CRM Task Service Report button in view mode when the Task has a Field Service Task Type and its status is Completed. The standard button selects servicereport from notification.taskEmail, opens the preview, and asks for confirmation before requesting email.
For this view's hidden, name, label, notification, send, success, error, and delay properties, see Configuring FSM Service Report Buttons. That section includes preview-only configuration and report and email selection. Hiding the button doesn't stop automatic Task notifications.
Complete Standard Object
This example shows the complete declared standard defaults.
{
"views/task/servicereport": {
"hidden": false,
"name": "custpage_nx_servicereport",
"label": "custcollection_fsm.report_task_servicereport_button_label",
"notification": "servicereport",
"send": "custcollection_fsm.report_task_servicereport_confirm_message",
"success": "custcollection_fsm.report_task_servicereport_success_message",
"error": "custcollection_fsm.error_generic_error_message",
"delay": 1000
}
}
Optional Assigned Field
The views/task/unassigned configuration makes the Assigned field optional on CRM task browser forms after page initialization, allowing the form to accept an unassigned task. The standard component waits 1,000 milliseconds before applying the change to accommodate NetSuite form initialization.
The following table describes the configuration property.
|
Property |
Accepted Value |
Standard Default |
Effect |
|---|---|---|---|
|
|
Boolean. |
|
Turns off the adjustment that makes the Assigned field optional. |
The adjustment applies to the form. It doesn't supply an assignee, select an available resource, or remove every other model, role, or platform validation that may apply when saving a Task.
Complete Standard Object
This example shows the complete declared standard defaults.
{
"views/task/unassigned": {
"hidden": false,
"delay": 1000
}
}
The delay: 1000 value is the component's standard initialization timing in milliseconds. It is included for completeness, but this topic doesn't establish a supported timing override.