FSM Project Task Model Reference
This reference is intended for administrators and developers who work with Project Task model mappings and sourcing behavior.
This model represents projecttask and inherits Activity mappings and sourcing. It adds number: "custevent_nx_task_number" and maps subsidiary from the Project when Subsidiaries is enabled. Its explicit prototype.defaults is empty.
Standard default structure (JSON fragment):
{
"models/projecttask": {
"prototype": {
"record": "projecttask",
"map": {
"name": "title",
"company": "company",
"project": "formulatext:nvl2(nullif({company.internalid}, {custevent_nx_customer.internalid}), {company.internalid}, '')|",
"status": "status",
"priority": "priority",
"message": "message",
"type": "custevent_nx_task_type",
"customer": "custevent_nx_customer",
"asset": "custevent_nx_task_asset",
"address": "custevent_nx_address",
"latitude": "custevent_nx_latitude",
"longitude": "custevent_nx_longitude",
"timezone": "custevent_nx_time_zone",
"id": "internalid",
"number": "custevent_nx_task_number"
},
"defaults": {}
}
}
}
The fragment includes the inherited Activity map. The prototype.map.subsidiary mapping is "job.subsidiary|" when Subsidiaries is enabled. It is omitted from the fragment.
The standard Company relationship permits a Project, rather than a Customer. The model clears its generated number on copy and uses the new internal ID when numbering the resulting record. Preserve the Project relationship. It determines customer and Asset sourcing. Project Task scheduling and assignment data have their own Schedule Board and FSM Mobile definitions.
Service report actions use Project Task notification definitions. For configuration of report templates and buttons, see FSM Service Report Configuration. Avoid adding report properties to this model.