Configuring FSM Mobile Asset History
Configure routes/mobile.history to control the supplied History tab, which displays read-only asset history in FSM Mobile. For information about History behavior and the records it combines, see FSM Mobile Asset History.
This topic includes the following sections:
Include history in the matching CRM Task or Project Task event resource rule. The standard visibility condition requires options.asset or event.asset. For information about the shared resource-rule structure, see Selecting Resources. Don't replace an account's existing tab array with a one-tab example.
For default properties and mappings, see FSM Mobile Asset History Configuration Reference.
For examples of changes to History presentation and record sources, see Customizing FSM Mobile Asset History Presentation and Sources.
Dependencies and Customization Limits
Keep the following dependencies and limits in mind when customizing History:
-
Retain
readonly: truefor the combined History view. Changing this flag alone doesn't provide supported editing for the combined record sources or nested tables. -
Asset context comes from the requested Asset or event. Adding an unrelated property or element doesn't supply a valid record reference to these searches.
-
Task numbers, source IDs, array names, and child-element
parentvalues are different dependencies. Altering one without the corresponding maps can hide history or associate rows incorrectly. -
The default file search depends on the service-upload folder naming used by Files. It is not a search of every native attachment or every Field Service File association.
-
A copied resource definition doesn't automatically retain the specialized final
numberfilter. Apply these overrides to the suppliedhistoryresource. For the examples, see Customizing FSM Mobile Asset History Presentation and Sources. -
A resource-rule ID with a numeric suffix, such as
history-1, resolves to the suppliedhistorydefinition. Reusing that definition with a requested Asset context is different from copying its JSON under an unrelated resource name. -
all: trueapplies to each named source. It doesn't remove NetSuite execution limits or prove that unrelated record types are covered.
When Changes Apply
Display controls apply when FSM Mobile receives the revised resource definition. Source filters and maps affect subsequent History requests without changing the original task, transaction, or file records. Removing history from a matching resource rule removes that tab for those jobs without deleting historical data.