Customizing
Customizing
Breadcrumbs

Define Data Field Type

Information

  • In module customizing you can define for each data field how a data field is to behave in a user module or as what kind of field type it should act as, e.g. input field, checkbox, traffic light field, etc.

  • Some field types are only defined by a single customizing parameter, others, however, are defined by a combination of multiple parameters.

  • Below, you will find a list of the field types found in the application with specification of the necessary settings in module customizing so that a data field appears as the respective type on the interface.

  • Information on the use application of different field types, please refer to the Introduction and Program Operation help area.



Field type

Suitable DI type

Required parameter settings

Remarks

ID data field

Primary key data item

(data item with Column type = UUID)



Input data field


DF behavior = i


Output data field


DF behavior = o


Link Data Field


DF behavior = e2/e4/e5

Action ID = ID of a module, macro, menu item or a method name from the module subclass or a variable for the respective object

See also: Customize Link, Button, Context Menu, etc.

Listbox data field


DF behavior = le/li

LBMOD = ID of a listbox module

Input only via list box = (optional)

See also: Customize Listbox

Date listbox data field


DF behavior = cc

Data field configuration = paste one of the cc templates or write a definition

See also:

Customize Date Listboxes with Calendar Function

Checkbox data field

Data item with Column type = Yes/No

DF behavior = i2/o2


Mandatory data fields


DF behavior = i or li

Mandatory =

  • The Mandatory function can be used on all fields that do not accept an empty value or zero since blank spaces or zero are not considered as entry.

  • It is not reasonable to use this function for checkbox fields since here, a check is only performed when the checkbox is activated.

  • Ident data fields do not need to be set to Mandatory, these are automatically mandatory entries so that the data record is valid according to the database rules.

  • For date data fields, the mandatory function has no effect. Saving is also possible when there are empty data fields. However, it can be queried via another DI.

Traffic light data field


DF behavior = o

Traffic light DI = ID of a traffic light data item

See also:

Customize Traffic Light DI

Continuous text data fields

Data item with Column type = CLOB

DF behavior = i or mi/mo

Multiline = (optional)

The Multiline parameter determines whether line breaks are possible in the continuous text data fields.

Hyperlink data field

Data item with Column type =

HL: File in the DB or

HL: Local file or

HL: Linked file

DF behavior = h/ho

If the Output parameter is activated on the data area that contains the hyperlink or if the make_output() Python function is used, the hyperlink behaves as if it had ho DF behavior.

Browser control data field


DF behavior= we

For this data field, the 004336 button DI must be used.

Adaptive Card Designer data field


DF behavior= ad

For this data field, the 004336 button DI must be used.

Application Link data field


DF behavior= al

For this data field, the 004336 button DI must be used.