Support > Repository > Screen function > Button name and display condition
ja | en

You can change the names and display conditions of the buttons prepared for each screen. Expressions are also applicable.

Figures 1 and 2 show examples of applying expressions to button names.The button name will change depending on the logon account.

Figure 1 When the system administrator uses it, the button name becomes "administrator registration"
Figure 2 When the general use is used, the button name becomes "general registration"

Not only the fixed name but also the expression can be set for the "button name" of "button display" prepared for each screen.

Fig. 3 Button name setting

When specifying a fixed name

Specify the button name as it is.

Schedule registration

When using formula

Make sure the result type of the expression calculation result is of type string type.

IF (EXACT (USERNAME (), "admin"), "administrator registration", "general registration")

For details of the formula, see "a formulaPlease read.

When "button display condition" is set, the button will be displayed on the screen only when the condition is met.Figure 4 shows an example of specifying the condition "Date is after today".

DATE(${sdate})>=DATE(TODAY())

The return value of the expression should be a boolean value.trueOrfalseI will try to return.

Figure 4 Applied date condition

Control display/non-display of the button in conjunction with the value of the condition item

In the example of Figure 4, if you do not match the conditions when opening the new registration screen, the registration button will be hidden.After that, even if you enter a conditional date item, the button will remain hidden.

In the case of modifying this operation and controlling display/non-display of the button in conjunction with the value of the condition item, as shown in FIG. 5 (regarding the condition item) "When the value is changed, the screen is re-displayed Drawing "setting is effective.

When this setting is made, the value of the form will be retransmitted each time the value of the item is changed.Control of button display judgment is performed on the server side.

Figure 5 Redrawing screen when changing value

Example of description of conditional expression

When the value of the item item is 1, the registration button is displayed

${item}==1

When the value of the item item is "Tokyo", the registration button is displayed

EXACT ($ {item}, "Tokyo")

EXACTThe function compares strings.

For the model schedule, display a button when a user who has the authority "perm_button" operates it

HASMODELPERMISSION("perm_button", "schedule")

HASMODELPERMISSIONThe function returns whether it has the authority specified by the user.

Display a button when a user who has a principal "publicuser" operates it

HASPRINCIPAL("publicuser")

Administrator only Display buttons

HASPRINCIPAL("all")

All means administrator authority.

When you log on with administrator privileges,HASPRINCIPAL Function alwaystrue.Therefore, in the case of displaying only button of administrator authority, it means that any argument (principal name) given in parentheses is actually anything.However, to distinguish it from other principals, we recommend specifying all as above.

With foreign key relationships, you can list multiple child models on the screen of the parent model.
The button display control in this case is the following rule.

  • Items that can be included in conditional expressions areParent model.
  • However, the notation "child model _lp" can be used as a list display of children as seen from the parent.

Example: "Foreign key cooperation> Display condition"And the value of the item item 1 of the parent model is larger than 100, a new registration button of the child model is displayed.

${item1} > 100

Example: When the number of child models linked to this parent model is less than 3, display the registration button of the child model.

COUNT(${support_lp} < 3)

COUNTThe function returns the total number of child records.

Fig. 6 Button display control by external key cooperation

It also shows an example of controlling button names with expressions.Button name changes according to the number of child models.

IF (COUNT ($ {support_lp}) == 2, "one more", IF (COUNT ($ {support_lp} == 1, "two more", "three more"))

Restriction

This specification is not reflected on the "New" button on the child model list maintenance screen.
(The control of "New" button on the list update screen is currently unsupported.)