Numeric Fields

Numeric fields store signed integers, floating point values, or fixed precision values. A prefix and suffix can also be set for Numeric fields.
Tip: Numeric fields can be used as weights in Trend reports; to ensure accurate results when you use weights, ensure fields that use weighting always have values by setting a default value or setting the field as required.

Attributes

The following Numeric field attributes can be modified for default fields in projects and transition fields. Attributes set for fields in the Default Fields list apply to all transitions; attributes set for fields for a transition apply only to that transition.

Display Settings

The following display settings are defined in SBM Composer and can only be viewed in this interface:

Defaults

Specify a prefilled value for the field as needed.

Transition Actions

The following options are available for fields when you are editing a transition and enable you to control field values for the transition. For example, you may want to clear an existing value for a required field when a transition is executed, forcing users to provide a new value. These options apply to all field types for transitions.
  • Leave Value Unchanged

    Select to retain the field's current value when the transition is complete.

  • Clear Value

    Select to clear the field's current value.

  • Set Value to Default Value

    Select to use a default value for the field as the user executes the transition. You can then select a default value.

The following options apply to calculation options for Date/Time and Numeric fields. For details, refer to Calculating Values for Date/Time and Numeric Fields.
  • Set Value to Calculation

    Select this option to define a calculation that executes when the transition is executed, and then select the following options:

    • Calculate...

      From the first list, choose to perform the calculation before the Transition form opens, after the open form is submitted, or both.

    • First Operand

      Using the guidelines in About Operand Fields and Operator Selection Lists, specify a constant value, field, or date/time keyword to use as the first operand in the calculation. This will be filled with the current value of the first operand. The field selected from the list cannot be the same field as the field being edited, a field that could cause a recursive calculation, a deleted field, or a field in the Not Used section.

    • Operator

      Using the guidelines and tips in Calculating Values for Date/Time and Numeric Fields, select a valid operator for the calculation.

    • Second Operand

      Using the guidelines in About Operand Fields and Operator Selection Lists, enter a second constant or a valid field. Valid fields for the second operand are dependent on the field type, the first operand, and the operator. If the first operand or operator chosen causes the second operand to be invalid, the second operator is changed to a valid constant. The second operand cannot be the field being edited, a field that could cause a recursive calculation, a deleted field, or a field in the Not Used section.

  • Empty Operand Fields

    Select one of the following options:

    • Are Invalid

      Select to require users to provide values for fields used as operands for the calculation before the transition can be completed.

    • Skip Calculation

      Select to allow users to complete the transition without providing values for fields used as operands for the calculation. The calculation is skipped if values are not provided.

    • Treat as Zero

      Select to perform the calculation and treat empty values in fields used as operands for the calculation as zeros.

  • Add Calculation to Current Value

    Select to add the calculation to the field's current value. This enables you to increment the current value or to calculate the total of the calculation and the current value. This option is only available for Numeric fields and Date/Time fields set to record elapsed time.