Support > Repository > Model item > Defining item rules (use as data dictionary)

Multiple settings can be grouped into rules. It can be used as data dictionary plus alpha. R7.10

"Data dictionary" is a summary of descriptive texts of data managed by the application to be developed.In general, we will organize information such as data type and number of significant digits for centralized management.It is said that it is still better if you can manage it including things such as input rules and auxiliary information for explanation.Wagby's design information (repository) is the data dictionary itself.

"Data dictionary" has related information between data.Therefore, for example, when trying to delete a model item, it can also be used to check the influence range referring to this item.

Figure 1 Confirmation dialog when deleting model items (related items can be confirmed)

What is item rule

Consider the case where several settings related to model items are set in the same way for multiple items. For example, the rule is as follows.

In Wagby, commonly available design information can be made into parts.We call this "item rule".
This section explains how to define and use it.

Definition method

Select the "Item rule" tab in Designer.

Figure 2 Item rule tab

In the initial state, there is no item rule.Select "New" from the upper left gear icon.

Figure 3 Creating a new item rule

The item rule setting dialog opens.

Figure 4 Item rule setting dialog

Prepare "setting name" and "overview".Setting name is a required item.

Figure 5 "Setting Name" and "Summary" are prepared

Prepare the repository.Click the "Add" button.

Figure 6 Preparing the repository

You can select the tab name of the model item detailed setting dialog as "category".First, specify this category.

Figure 7 Select a category

The list of repositories included in the selected category is displayed.Please select the repository you want to set.

Figure 8 Repository list
All repositories are "repository structure and team development> Repository listPlease refer to the.

Next, specify the "setting value".Depending on the repository, it can be selected formula or manual input.

Figure 9 Specify the setting value

Multiple repository settings can be included in one item rule.In this example, we are setting therapy for input format and output format.

Figure 10 Setting multiple repositories

Click the "Save" button and save this setting.

Figure 11 Save button

We created one item rule.With the same procedure, you can prepare multiple item rules.

Figure 12 Item rule created


When multiple item rules are prepared, the priority of application is higher in order from the top.If you included settings for the same repository key, the repository settings included in the higher field rule will be in effect.

In Figure 12 you can rearrange item rules by dragging and dropping.

Opens the "Item rule" tab of the model item detailed setting dialog.You can apply the prepared item rule.

Figure 13 Item Rule tab

You can apply it by checking the item rule name.

Figure 14 Select the item rule you want to apply
Multiple item rules can also be applied to one model item.

Please execute the build process after setting.The item rule is reflected.

In Fig. 12, you can display the model and model item list to which this item rule is applied by pressing "Browse" button on the item rule setting tab.This allows you to know which items have been applied.

Figure 15 Check item status

In Figure 12, you can add, change, or delete repository information by pressing the "Edit" button on the item rule setting tab.

Figure 16 Editing repository information

After editing, please execute the build process.All applicable items are changed all at once.

You can set "Item name" "Type" "Search (use for condition)" "List (for display)" to set in the list of model items.

Fig. 17 Setting field of basic category

Type setting

For type setting, you can enter the following values.

ClassificationConfigurable type
String "Character string", "zip code", "mail address", "URL", "file name"
Numerical value "Integer", "1 byte integer", "2 byte integer", "4 byte integer", "8 byte integer", "4 byte floating point", "8 byte floating point"
Date/Time "Date", "Date and Time", "Time"
Item reference of other models "Reference to another store model (combo box)", "reference to another store model (radio button)", "reference to another store model (check box)", "reference to another store model (search screen) "," Reference interlocking of other store models "
Repeat container "(Repeat item container)"
Repeating Container ID "(ID for repeated item container)"
When setting it actually, please exclude double quotes.

Notes on type setting

If you change the type in Designer, some settings will return to the initial state.However, in this item rule setting, even if you change the type, other settings will not be restored to the initial state and will be maintained.Therefore, developers themselves should carefully review related settings that are likely to be affected by changing types.

Specifically, we recommend that you check the following settings for all items that apply this item rule when you change the type.

  • Search range search screen.(Even when changing from numeric type or date type to character type, setting of range search still remains.)
  • Check the input.Includes allowable character types.
  • Implicit condition.
  • initial value.
  • Date, number format.
  • Input filter.
  • Primary key order setting.
  • Setting of narrowing down.
  • Input control.(Input possible/impossible expressions, required, prohibited characters, regular expressions, etc.)
  • a formula.
  • Unique constraint of the database.
  • The lock name.
  • Transaction configuration.
  • SQL expression.
In this way, since the influence due to change of type is large, designation of type in the item rule is used not for "possibility of change in the future" but for "to identify item list using this type" It is better to do.
  • The configuration information on the item rule is stored in the .userDefinedItem folder in the repository/trunk folder.
  • In the model item, it is a repository key named model/modelitem/userDefinedItem and contains information on which item rule to apply.When applying multiple, it is comma separated.
  • For the item rule, the repository key that can be specified in the model item detailed setting dialog is the target.You can not include things related to screens, layouts, authorities, menus, preferences, etc.