Points to consider when selecting a field type
The field type cannot be changed midway, so you need to select the type in advance, taking into account the variation of input values.
For example, if you define a string type field and start entering values, and then want to change it to an integer type or rich text type,
You will need to define a new field and then work on migrating the entered data and develop an extension.
When adding a field, refer to the table below to determine the type according to the contents of the existing results.
We recommend that you then sample and model the actual design information and verify the validity of the metamodel.
When to use and points to consider for each field type
Field type | When to use | Points to consider |
---|---|---|
String | Highly versatile, it can handle long text including line breaks. | While the input format is free, the disadvantage is that the input information is not formatted. However, it is possible to check the format of the input information using an extension. |
Integer | Can handle quantities, number of times, and their upper and lower limits. | If the unit of the value is not uniquely defined, consider using another field that expresses the unit, or using a string type to enter the value and unit together. Cannot handle indefinite values. If the initial value is not set, the initial value will be zero. For example, it is possible to set the negative integer "-1" as indefinite and set it as the initial value. |
Real number | Can handle calculated design values and their thresholds. | Same as integers |
Boolean value | Can handle information that can be expressed as two values, such as ON/OFF or enabled/disabled. | Cannot handle indefinite values. To express three values including indefinite, consider using an enumeration type. When the document is output, it will be displayed as "True"/"False". If you want to display it as "Existence"/"None", consider using an enumeration type or rewriting it with an extension. |
Rich Text Edit Tool | You can centrally manage diagrams, tables, appearance and design images in Office documents along with design information. | Elements in diagrams cannot be subject to traceability management. For details, please refer to "When to use rich text". |
Enum Type | You can define unit systems for numerical values and universal options for the target domain. | The options are defined in the metamodel and cannot be changed at design time. |