Customizing FSM Mobile Asset History Presentation and Sources
Use these examples to change the History tab's presentation, record sources, and display elements in FSM Mobile. For default properties and mappings, see FSM Mobile Asset History Configuration Reference.
This topic includes the following sections:
Review the shared configuration constraints and timing before making changes. For more information, see Dependencies and Customization Limits and When Changes Apply in Configuring FSM Mobile Asset History.
To exchange the two principal list columns, merge this fragment:
{
"routes/mobile": {
"history": {
"element": {
"date": { "column": 1 },
"details": { "column": 2 }
}
}
}
}
To omit inventory history and its query, remove the named source and hide its table together:
{
"routes/mobile": {
"history": {
"article": {
"inventory": null
},
"element": {
"inventory": { "hidden": true }
}
}
}
}
The null value removes the inherited source during configuration merging. Hiding the table alone doesn't remove its query. This change affects the History view without deleting Sales Order lines or disabling Consumable processing.
Task filters can be narrowed for the intended historical scope. A replacement filter array must express that whole intended scope, including Asset and completion conditions where required. Changing only CRM Task selection leaves the Project Task source unchanged.
Changing the mapped file description can make its presentation consistent with Files. For example, use the Files tab's cleaned-description expression at history.article.files.map.files[0].description. The files map is an array: replace it with the complete required row map, retaining native file identity and download link. For information about the cleaned-description expression, see Configuring Categorized Files Tabs in FSM Mobile. Map units must also match the display: native KB values require multiplication by 1,024 when supplied to a byte-formatted Size element.
Additional Record Sources and Elements
The supplied History tab can be extended with additional record sources, mapped values, and display elements. Each additional named source under routes/mobile.history.article needs its own record type, search filters, and field map. Sources that add information to an existing task entry must return the matching task identity. The supplied final number filter continues to apply to the combined entries.
Define each additional display element manually under routes/mobile.history.element. Use an element name that matches the mapped value, and specify a suitable type and label. For repeating rows, define the table and its child elements, including their parent values. Adding a source or mapped value doesn't automatically create the elements needed to display it. Adding an element doesn't automatically retrieve its data.
Additional sources and elements require configuration and maintenance and can affect runtime processing. The searches, mappings, and element definitions must be configured and maintained together. Each additional source search can increase retrieval time and processing usage, and additional returned data can increase response size. Adding another displayed value from an existing source can use that source's map without requiring a separate source search.
Alternative History Tabs
FSM Mobile configuration also supports separate custom history tabs with their own record selection and presentation. The Service History custom-tab example, deployed in many accounts, demonstrates this approach. Its servicehistory resource combines Sales Order, Install, Maintenance, and Repair searches with manually defined display elements to present an alternative history view.
Custom history tabs use FSM Mobile's general configuration capabilities. Configure a separate resource rather than overriding routes/mobile.history. Define the custom resource under routes/mobile.<resource ID> and include its ID in the appropriate event resource rule. Its searches, maps, and elements determine which records appear and how they are displayed. The example illustrates an alternative configuration. Its record types and fields depend on the account's configuration.
For information about the shared configuration mechanisms, see Selecting Resources, FSM Mobile Resource Properties Reference, FSM Searches and Field Mapping, and Configuring Elements.