FSM Mobile Number Element Normalizes precision and step Values in 2026.07.2

This page is primarily a property reference for the FSM Mobile Number element, but it embeds two version-gated behavioral changes effective in 2026.07.2 that require configuration updates.

What changed

precision property

• Accepted range is a whole number 0 through 8. Default is 8 (up to 8 decimal places).
• 2026.07.2 breaking behavior: If "precision": null is still present in a Number element configuration, FSM Mobile will silently normalize it to "precision": 8. Previously null was accepted without coercion.
• A unit precision (from a named formatting profile) takes precedence over this property. This property does not add a stored-value validation rule — it only limits decimal entry and display.

step property

• Accepted value is a positive number or null. Default is null (no increment constraint).
• 2026.07.2 breaking behavior: If "step": "any" (string) is still configured, FSM Mobile will normalize it to null, meaning no increment validation is applied. Replace "any" with an explicit positive number (e.g., 0.01) or remove the property entirely.
• When no unit precision applies, a whole-number step displays zero decimal places; a fractional step displays decimal places matching the increment (e.g., 0.25 → 2 decimal places).

Other properties (no version-specific changes)

• value — stored numeric value; numeric strings are coerced during resource normalization. Prefer JSON number literals (1.25) over strings ("1.25").
• min / max — inclusive validation limits; number or null.
• stepper — boolean; shows +/− controls. Works with step but does not change validation by itself.
• unit — string identifier selecting a named Number formatting profile from the mobile context's unit collection. Controls display precision and prefix/suffix; does not affect stored value, min, max, step, stepper, or value.

What to do

1. Audit existing FSM Number element configurations for "precision": null. Replace with a whole number 0–8 that matches your required decimal places. If you want maximum precision, set 8 explicitly.
2. Search for "step": "any" in your configurations. Replace with a positive numeric increment (e.g., 1, 0.01, 0.25) or remove the step property to accept any value.
3. These normalizations happen silently at runtime — they will not throw errors, but the resulting behavior may differ from your intent. Test Number element entry and validation in a sandbox on 2026.07.2 before production rollout.
4. Review the related reference pages Configuring FSM Mobile Number Elements and Unit Definitions for FSM Mobile Number Elements for full context on unit-precision precedence rules.

Note: The source page is structured as a property reference table, not a traditional release note. The version-specific details above are the only net-new behavioral changes; the rest is existing reference documentation. Oracle does not specify which SuiteScript modules, REST endpoints, or SuiteTalk operations are involved in authoring these configurations — consult your FSM implementation for the relevant customization entry points.