NextGen FSM

Non-mandatory boundaries for dynamic forms

Balance data integrity and field flexibility.  Dynamic forms typically enforce strict limits on data entry. However, with non-mandatory boundaries, you can submit values that fall outside ideal ranges, so non-critical data variances never block the workflow. 

Validation flow

Audience: Technicians

  1. Tap Save. The system first checks mandatory limits. 

    • If these fail, the save is blocked.

    • If strict limits are met, the system evaluates threshold limits.

    • If a threshold is exceeded, a warning notification appears.

  2. To save the form, acknowledge the warning.

Configure non-mandatory boundaries

Audience: Administrators

  1. Open the dynamic form template you want to configure.

  2. Select a Text, Integer, or Decimal node:

    • Text: Minimum/Maximum Length

    • Integer/Decimal: Minimum/Maximum Value

  3. For each node, set:

    • Strict Minimum Value

    • Strict Maximum Value

    • Threshold Minimum Value

    • Threshold Maximum Value

  4. Define the Threshold limits (the preferred range).

  5. To apply changes to the mobile app, click Save.

FSM mobile users

With mandatory boundaries

As a default, the Strict Minimum Value and Strict Maximum Value fields prevent invalid entries. 

With non-mandatory boundaries

If the Threshold Minimum Value and Threshold Maximum Value fields have been configured, you can submit a dynamic form with values that exceed the limits.

Important: These values still need to always respect the Strict Minimum Value and Strict Maximum Value settings. The app displays a warning if values exceed default limits.