FSM Mobile Asset History Configuration Reference

This topic includes the following sections:

• Mapped Properties and Units

• Default JSON

The following table lists properties, default values, and effects for routes/mobile.history. Property paths are relative to this resource. Standard labels use FSM translations.

Property	Accepted Values and Units	Default Value	Effect
label, icon	Strings.	Translated History label. icon: "bookmark".	Changes tab presentation.
hidden	Boolean value or template tag that resolves to a Boolean value.	"${ !options.asset && !event.asset }".	Omits the resource when neither Asset context is available. Removing the condition doesn't supply an Asset.
remote	Boolean value.	true.	Retrieves articles separately on demand. Retain it for the supplied History experience.
readonly	Boolean value.	true.	Removes create, edit, and delete actions. The combined history is not a supported general record-editing resource.
search	Boolean value.	true.	Enables server-assisted search on the History list. It doesn't add a search control to a task's detail page or add NetSuite filters.
article.sortby	Top-level mapped property name.	"date".	Orders combined server articles in ascending text order. This ordering is separate from UI sorting and search-column sorting.
article.task	Named CRM Task search.	record: "task", all: true. Selected Asset and Completed status.	Supplies CRM Task history. Retain number for the final filter and the task ID used to combine sources.
article.projecttask	Named Project Task search.	Included only when Project Management is enabled. record: "projecttask", all: true, with selected Asset and Completed status.	Supplies Project Task history. The standard source omits assigned-technician and phone maps.
article.inventory	Named Sales Order search.	record: "salesorder", all: true. Line Asset matches the selected Asset.	Supplies rows containing items and quantities grouped by their CRM Task or Project Task identity. It doesn't read fulfillment quantities.
article.files	Named native-file search.	record: "file", all: true. Service-upload folder matches the selected Asset.	Supplies file rows grouped by task identity extracted from the folder. It doesn't search the custom Field Service File associations.
element.inventory, element.files	Table elements.	Types "table".	Display the respective mapped arrays. Child elements identify their table through parent.
element.size	Number element, configured in bytes.	unit: "byte". Child of files.	Formats the file-size value supplied by the map. For more information, see Mapped Properties and Units.
element.<name>.column	Number or other accepted column value.	details: 1, date: 2. item: 1, quantity: 2. filename: 1, description: 2, size: 3.	Changes list columns at the appropriate top level or table-child level.

For information about these reusable controls, see FSM Mobile Resource Properties Reference and FSM Mobile Element Reference.

Mapped Properties and Units

The following table lists mapped properties, their standard sources, and their dependencies.

Mapped Property	Standard Source	Dependency
number	custevent_nx_task_number for both task sources.	Entries without a number are removed by the supplied History behavior.
date	CRM Task: Field Service Start Date, otherwise Start Date. Project Task: Start Date.	Supplies the Date element and the server's sortby property.
details, actions	details: source-specific summary formula. actions: custevent_nx_actions_taken.	Supply historical task content. The summaries can shorten Case details and messages.
assigned, phone	CRM Task: assigned#, employee.mobilephone.	Not supplied by the standard Project Task map. Adding an element alone doesn't populate these values.
Inventory source id	Sales-order line Task (custcol_nx_task) or Project Task (custcol_nx_projecttask), with the corresponding record prefix.	Matches the relevant task article identity.
inventory	Array containing item and quantity.	Element children use parent: "inventory".
File source id	Task identity extracted from the service-upload folder.	Matches the completed task article. A file row alone is not a retained History entry.
files	Array containing name, document, description, and size.	Element children use parent: "files". document supplies native ID and download address.
File description	Native description.	Can include metadata appended during upload. It differs from the Files tab's cleaned description map.
File size	Native documentsize, in KB, without conversion in the standard History map.	The supplied Size element is configured as bytes. Keep this difference between source and display units in mind when changing the display. A byte-based map requires conversion.

The named sources are combined by matching task IDs. For information about generic named-source behavior and map flags, see FSM Searches and Field Mapping. History additionally removes combined entries without number through its supplied behavior.

Default JSON

The following fragment shows the standard resource controls and CRM Task selection. Labels, detail formulas, other maps, and the other named sources remain inherited. The fragment is not the complete History definition.

            {
  "routes/mobile": {
    "history": {
      "icon": "bookmark",
      "hidden": "${ !options.asset && !event.asset }",
      "search": true,
      "remote": true,
      "readonly": true,
      "article": {
        "sortby": "date",
        "task": {
          "all": true,
          "record": "task",
          "filters": [
            ["custevent_nx_task_asset", "anyof", "${ options.asset || event.asset }"],
            "and",
            ["status", "is", "COMPLETE"]
          ],
          "map": {
            "number": "custevent_nx_task_number",
            "date": "formuladate:nvl({custevent_nx_start_date},{startdate})[date]",
            "actions": "custevent_nx_actions_taken",
            "assigned": "assigned#",
            "phone": "employee.mobilephone"
          }
        }
      }
    }
  }
} 

          

When Project Management is enabled, the standard article.projecttask search uses the same filter array for the asset and status with record type "projecttask". Its date map is "startdate[date]".

Standard inventory source at routes/mobile.history.article.inventory:

            {
  "all": true,
  "record": "salesorder",
  "filters": ["custcol_nx_asset", "anyof", "${ options.asset || event.asset }"],
  "map": {
    "id": "*formulatext:nvl2({custcol_nx_task}, 'task-'||{custcol_nx_task.id}, 'projecttask-'||{custcol_nx_projecttask.id})",
    "inventory": [
      {
        "item": "item#",
        "quantity": "quantity"
      }
    ]
  }
} 

          

Standard file source at routes/mobile.history.article.files:

            {
  "all": true,
  "record": "file",
  "filters": [
    "formulatext:case when {folder} like '%task-%-${ options.asset || event.asset }-%' then 'T' else 'F' end",
    "is",
    "T"
  ],
  "map": {
    "id": "*formulatext:regexp_replace({folder}, '^([[:alpha:]]*-[[:digit:]]+).*', '\\1')",
    "files": [
      {
        "name": "name",
        "document": {
          "id": "=internalid",
          "url": "formulatext:'mobile/file/'||{internalid}"
        },
        "description": "description",
        "size": "documentsize"
      }
    ]
  }
} 

          

These formulas are reproduced as existing standard mappings. Their presence is not proof of poor performance or an instruction to replace them. For the shared decision rules, see Reducing Formulas in FSM Searches. For information about measurement and data capture, see Capturing FSM Performance Data.

Additional Information

• FSM Mobile Resource Properties Reference
• FSM Mobile Element Properties
• FSM Search Result Processing
• Capturing FSM Performance Data

Related Topics

• Configuring FSM Mobile Asset History
• Customizing FSM Mobile Asset History Presentation and Sources

General Notices