Domain Data Types

The data type you specify in the attribute definition determines how the application interprets the values in the domain. For example, you define an attribute with a list of values domain. You define the attribute values to be 1, 5, 10. To write configuration rules that perform numeric computations using these values, you must select the data type Integer or Number when defining the attribute.

The domain of an attribute can be one of the following data types:

  • Boolean. Use this data type when the user's input is true or false, yes or no. If you specify the Integer data type for these inputs, the application assigns 1 for True or Yes inputs. False and No are assigned 0.

  • Number. The attribute value can be any positive or negative real number. In Boolean expressions, numbers greater than 0 are interpreted as true. Omit commas when specifying the domain. For example, enter 10,000 as 10000.

    Note: When you specify a number, make sure that the number of fractional digits is consistent with the regional or locale setting, defined in the Administration - Data, then the Locale view. If you do not, rules written against the attribute may not behave as anticipated, because the UI displays the number based on the regional or locale setting.
  • Integer. The attribute value can be any positive or negative whole number. If a computation results in a fractional amount, the result is rounded to the nearest whole number. In Boolean expressions, integers greater than 0 are interpreted as true. Omit commas when specifying the domain. For example, enter 10,000 as 10000.

  • String. The attribute value can be letters, numbers, or any combination. Attributes with this data type cannot be used as operands in a computation or as the result of a computation. The only arithmetic operator that can be used with this data type is = (equals). For example, you can write rules that test if the user has picked a specific string from a list of values.

  • Date. The attribute value is interpreted as a date and must be in the correct date format. The system administrator sets date format defaults. Arithmetic computations using dates is not supported. For example, you cannot increase or decrease a date using a computation. All comparison operations are supported for dates. For example, you can compare two dates and determine whether one is earlier than (<), later than (>), or the same as (=) another date. Data type mismatches cause the user's input to be rejected, or can cause indeterminate results. For example, comparing a date data type to an integer data type.