Numeric fields store signed integers, floating point values, or
fixed precision values.
Style
Important: You cannot change the style of a
Numeric field after a process app is published. For example, you
cannot change an integer field to a floating point field. However, there is a
way to reset the field and change it if you intend to deploy the process app to
a different environment. For more information, see
Modifying Locked Elements in a Published Process App.
- Integer
The maximum positive integer accepted is 2147483643, and the minimum
negative integer accepted is –2147483648.
- Floating point
The maximum and minimum accepted range of values are determined by
your server hardware.
Note: SBM Composer respects
the regional option set for your computer for floating point and fixed
precision values. For example, if your regional option is "Czech," a
comma is used instead of a decimal point.
- Fixed precision
The maximum and minimum accepted range of values are determined by
your server hardware.
- Digits displayed after the decimal point
Specify the number of digits (with a minimum of 0 and a maximum of
15) you want to appear after the decimal point. This option is available only
when the
Fixed precision option is enabled.
Note: Some large integer and floating point values are reserved for
internal use. Integer values larger than 2147483643 and floating point numbers
between 4294967292.000 and 4294967295.99999 cannot be used in
Numeric fields for this reason.
Display
- Prefix and
Suffix
Type any plain text and HTML tags you want to display before and
after the field's values. Note the following:
- The rendered HTML is visible in preview mode and at runtime, but
not in the form editor.
- HTML formatting applies to the prefix and suffix for the field
label, but not to the value of the field.
- Use the
< and
> character entities to display the less
than (<) or greater than (>) signs, respectively. Otherwise, these signs
will be interpreted as HTML code. Use the
character entity for each extra space
you want to display.
- By default, there is no space between the field value and its
prefix or suffix. If you want a space to appear between the prefix or suffix
and the field value, then you must add spaces.
Note: For best results, formatting changes should be applied using
styles on custom forms rather than by adding HTML tags to the field's prefix
and suffix. For more advanced HTML formatting, create a custom form for your
workflow, and then add an HTML/JavaScript widget to the form.
- Show thousands separator
Select this option to display values with commas (such as
"1,000" for "1000").
Note: SBM Composer respects
the regional option set for your computer. For example, if your regional option
is "Czech," a space is used instead of a comma.
-
Span entire row on forms
Select this option to make this field the only field to appear on a
single row.
Search & Query
- Appears in
report field lists
Select this option to include the field in lists on report forms.
Note: If this option is cleared after the field is used in a report,
the changed setting is ignored for that report; that is, the field will still
appear until it is removed from the report definition.
See
General Tab of the Field Property Editor for related information.
-
Appears on lookup form and relational field value
lookup
Select this option to add the field to the Auxiliary Data search
form in
SBM Application Administrator
and the Advanced Lookup Tool and Relational Field Value Lookup forms.
Note: The field order for the Advanced Lookup Tool and Relational Field
Value Lookup forms for primary items is determined by the default field order
of the table's first project in the project hierarchy. Projects are defined in
SBM Application Administrator.
- Appears on
searches for this table
Select this option to specify that the field will be available for
selection on the Advanced Search page. This setting applies to primary and
auxiliary tables. See
Considerations for Advanced Search for additional information.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.