FSM Mobile Element Properties and Defaults by Type

Note:

This reference is intended for administrators and developers who need supported element properties and defaults for Field Service Management (FSM) Mobile.

It lists supported properties and default values by element type and explains how configured values and NetSuite form loading affect initial values and element properties.

This topic includes the following sections:

• Value Defaults

• Form-Generated Properties and Initial Values

Value Defaults

A static value sets the initial default when FSM Mobile creates a new record. It doesn't reset or replace the value of a record that already exists. For a value expression, FSM Mobile can calculate or update the value when the expression runs in its applicable default or change context. The expression result must be accepted for the element type.

date and datetime use the current date or date-time only when "value" is omitted. To leave either element blank on a new record, explicitly set "value": "". This matches the stored blank representation. null is also normalized to "" for these types.

Form-Generated Properties and Initial Values

When a resource uses form, FSM loads the NetSuite form and translates its fields into elements for FSM Mobile. FSM then applies the resource's explicit element configuration over those definitions. A property can therefore be present in the generated element even when it is absent from the custom JSON.

Form loading supplies two separate kinds of information:

• Field information and initial values - The field ID supplies the element name. The field label, required status, read-only status, disabled status, and hidden status can supply the corresponding element properties. If NetSuite supplies an initial field value during form loading, FSM carries that value into the element's value. Select options are also loaded unless disabled by the form configuration.

• Properties added by FSM - The original NetSuite field type determines the FSM Mobile type and generated properties. For example, Text receives maxlength: 300. Text Area receives maxlength: 4000 and rows: 6. Long Text receives maxlength: 1000000 and rows: 12. These are FSM translation defaults. The form loader doesn't read NetSuite field restrictions for min, max, maxlength, or pattern.

A form-generated value, including an empty value supplied by NetSuite, takes precedence over the FSM Mobile type's initial-value fallback unless the element configuration overrides it. Initial values for fields loaded from a form vary with the field and record initialization context. Existing records use their loaded record values rather than being reset to these new-record defaults.

Omitting a property from an element override retains the generated property. Changing only type can also retain properties generated for the original field. Explicitly configure any affected properties, such as maxlength and rows, for the intended result.

The FSM Mobile Element Properties and Defaults by Type table identifies the relevant properties and defaults that vary by element type. For information about NetSuite field translation and form-loading options, see FSM Mobile Resource Properties Reference.

Important:

Check initial values as well as user-entered values against the element's effective limits. For example, a Text element generated from a form can receive a 500-character initial value and retain maxlength: 300. Loading the value doesn't automatically shorten it or increase the limit. Correct the initial value or configure an appropriate limit that the destination NetSuite field also accepts. Increasing an FSM Mobile limit doesn't change the NetSuite field's capacity.

The following table brings together each type's relevant properties and their defaults. The Common Element Properties are: type, name, parent, value, label, required, disabled, hidden, readonly, and class. Initial-value fallbacks are listed in FSM Mobile Element Types. A loaded form can supply a different initial value as explained in Form-Generated Properties and Initial Values.

The defaults apply only when a combined configuration or generated form definition doesn't already supply the property. Where the original NetSuite field type changes the result, the final column identifies that variation. heading supports only the properties listed in its row. Top-level elements and direct table children can also use column. For the column property, see Element-Specific Properties.

Type	Common Properties	Supported Properties	Type-Specific Defaults and Form Variations
checkbox	All	None	No additional properties. A form can supply a checked or unchecked initial value.
date	All	min, max, step	min: null, max: null, step: null. A form can supply its initial date instead of the current-date fallback.
datetime	All	min, max, step	min: null, max: null, step: 1 second. A form can supply its initial date-time instead of the current-date-time fallback.
email	All	pattern, placeholder	pattern: "", placeholder: "".
file	All	accept, downsample, maxsize	accept omitted. downsample uses the resource's imagesize value, normally 1080 pixels. The File input uses maxsize: 10240 KB for non-bitmap files.
heading	Subset supported, as listed in the next column.	type, name, parent, label, level, hidden	level: 1, label: "", hidden: false. name comes from the definition. parent omitted. No initial value.
html	All	rows, cols, maxlength, placeholder	rows: 3, cols: null, no configured maxlength, placeholder: "". A Rich Text field translated to HTML receives maxlength: 1000000, rows: 12. Inline HTML is read-only and receives map: "|".
image	All	accept, camera, downsample, maxsize	The default accept filter is listed in File and Image Selection and Upload Behavior. camera: false. downsample uses the resource's imagesize value, normally 1080 pixels. Image input doesn't apply maxsize.
number	All	min, max, precision, step, stepper, unit	min: null, max: null, precision: 8, step: null, stepper: false, unit: "". Form translation applies these values: Integer - precision: 0 Currency - precision: 2, unit: "usd" Float - precision: 8 Percent - precision: 4, unit: "percent"
password	All	pattern, placeholder	pattern: "", placeholder: "". Form translation supplies map: "|".
select	All	multiple, autoselect, barcode, options, placeholder, remote, search	multiple: false, barcode: false, options: [], placeholder: "", remote: false, search: false. Set autoselect explicitly. A form can supply options and an initial selection. A multiselect field receives multiple: true.
signature	All	width, height	width: 448, height: 148 pixels.
table	All	No additional properties. It is the only supported parent element type, and direct child elements use its name in parent.	No additional property defaults. Configure each child's limits separately.
tel	All	pattern, placeholder	pattern: "", placeholder: "".
text	All	barcode, maxlength, pattern, placeholder	barcode: false, maxlength: 300, pattern: "", placeholder: "". A form-loaded Text field receives this character limit even if custom JSON omits it. Its initial value can still be longer.
textarea	All	maxlength, rows, cols, placeholder	maxlength: 4000, rows: 6, cols: null, placeholder: "". Long Text receives maxlength: 1000000, rows: 12. A form-loaded Help field becomes a read-only Textarea with these ordinary Textarea limits and map: "|". A manually configured help compatibility type instead uses rows: 3 and has no generated maxlength.
time	All	min, max, step	min: null, max: null, step: 60 seconds. A form can supply an initial time.
url	All	pattern, placeholder, text	pattern: "", placeholder: "", text: "".

The following table lists JSON fragments for static element defaults. The form-generated variations in the property-support table still apply.

Time steps are in seconds, signature dimensions are in pixels, and character limits are in characters. For runtime dates, generated names, image filters, and values that vary by account, see the reference tables.

Element Type	Default Configuration
date	{ "type": "date", "min": null, "max": null, "step": null }
datetime	{ "type": "datetime", "min": null, "max": null, "step": 1 }
email	{ "type": "email", "pattern": "", "placeholder": "" }
heading	{ "type": "heading", "level": 1, "label": "", "hidden": false }
html	{ "type": "html", "rows": 3, "cols": null, "placeholder": "" }
image	{ "type": "image", "camera": false }
number	{ "type": "number", "min": null, "max": null, "precision": 8, "step": null, "stepper": false, "unit": "" }
password	{ "type": "password", "pattern": "", "placeholder": "" }
select	{ "type": "select", "multiple": false, "barcode": false, "options": [], "placeholder": "", "remote": false, "search": false }
signature	{ "type": "signature", "width": 448, "height": 148 }
tel	{ "type": "tel", "pattern": "", "placeholder": "" }
text	{ "type": "text", "barcode": false, "maxlength": 300, "pattern": "", "placeholder": "" }
textarea	{ "type": "textarea", "maxlength": 4000, "rows": 6, "cols": null, "placeholder": "" }
time	{ "type": "time", "min": null, "max": null, "step": 60 }
url	{ "type": "url", "pattern": "", "placeholder": "", "text": "" }

Additional Information

• FSM Mobile Resource Properties Reference
• FSM Expressions and Template Tags

Related Topics

• FSM Mobile Element Reference
• FSM Mobile Element Types
• FSM Mobile Element Properties
• FSM Mobile Element Validation Rules
• Configuring FSM Mobile Select Elements

General Notices