Support > Repository > Check the input > Required/warning
ja | en

There is a method of always entering mandatory check and a method of keeping warning display.

Example of execution

The item name of the item for which the mandatory check is specified is displayed in red. If you move the cursor with no input, it will be checked in real time as shown in Figure 1.

Figure 1 Realtime input check

Definition method

"Input check - required" is set to "O" in the detailed item setting dialog of the model item.

Figure 2 Specifying required input

Example of execution

Items for which "Warning" is set are also displayed in red letters. If you do not enter it, a warning will be displayed, but you can register again by clicking the "save" button again.(FIGS. 3 and 4)

Figure 3 Warning message is displayed when the first "Save" button is pressed
Fig. 4 When saving the second "Save" button, it is saved (leave blank).

Definition method

"Input check - required" is set to "warning" in the detailed definition of the model item.

Figure 5 Specification of required input (warning)
Warning designation does not work on the list update screen (including parent child model simultaneous update screen).

When the item is required, the following initial value is automatically set.

Item type initial value
Integer/1 byte integer/2 byte integer/4 byte integer/8 byte integer 0
4 byte floating point/8 byte floating point number 0.0

When this setting is made, a NOT NULL constraint is added to the relevant item of the table definition.That is, the table schema is changed.

Points to remember when reusing an existing table schema

Be careful when reusing an existing table schema.
Specifically, if a mandatory item has a NULL value, that data will not be hit by a search from Wagby.[More ...]

Points to note when defining submodels

Suppose you define a submodel and do not perform mandatory checks on the relevant items on the submodel side. (In other words, we assume a situation that mandatory checks are set for items on the main model side, but mandatory checks are not set for items on the submodel side.)

In this case, the main model performs the mandatory check, and the submodel does not perform mandatory check.

With this setting, the NOT NULL constraint is not set in the table definition.

"Use as a primary keyIf the setting is checked, mandatory check is automatically enabled and can not be changed.

  • This check is done in real time.(Check with JavaScript on browser.)
  • In the state of input error, you can not press the button such as "save".
  • The input item that caused an error has a background of red.This applies to text boxes or date/time list boxes.
  • "Required check" can not be specified for items for which viewing authority is set.

The repository key is model/modelitem/notnull.