Listbox Customizing

General

Listboxes

Customizing Information

• Listboxes are modules that can be opened via a data field with pull down menu.
• Listbox modules are customized like normal modules.
• The records for the listboxes can be
  • formed from existing data, e.g. the project data or
  • captured in the Listbox categories or
  • captured in an individual data table.

Parameters to be considered

• When customizing listbox modules
  • LB: value transfer
  • LB: part string search
  • Background symbol (for depositing a frame color)
• When embedding listbox modules:
  • LBMOD
  • DF behavior
  • Input only via list box

Customizing rules

• Listbox modules
  • can only contain one data window.
  • can contain visible as well as invisible data fields.
• In data areas, in which Never display is activated, no data field may have LB:value transfer or LB:part string search activated
• From a performance point of view, a listbox module may only contain the data fields it requires. These are data fields
  • are used for the sorting or filter criteria of the listbox.
  • are required for the correct output of the visible sorting or filter criteria.
• The listbox module may
  • only contain the visible traffic lights.
  • not contain any buttons.
  • not contain any listboxes; because in listboxes, no other listboxes can be output.

Notes

• In the status line, the following information is output upon opening a listbox: Number of hits in listbox: xxx of yyy. Here,
  • "yyy" is the total amount of hits: It is calculated from the records of data fields for which the LB: value transfer parameter is activated.
  • "xxx" the amount of displayed hits.
• The height (or width) of listboxes must not be adjusted manually but is calculated on the basis of the number of values (or width of the fields).
• There is a minimum and a maximum height or width.
• Within a listbox, structured data can be displayed as tree structure (like in a normal module).

Examples

Create Listboxes from Listbox Categories Manually

Objective

• To create a listbox module from listbox categories

Procedure

• Create new listbox categories in the Listbox Values module.
• Create a new module in the Modules module.
• Create a new data area with data fields from the DT454 Listbox values in the Data Areas module and enter the new listbox category for the Listbox category data field in the Filter by data field.
• Assign the data area to the module.

Adjust Listbox Values

Objective

• Adjust listbox values of a listbox category

Procedure

• Enter the required listbox category ID in the LBCAT field in the Listbox Values module.
  • In case no listbox values are displayed for the listbox category ID, enter the ID in the Listbox Values (Old) module.
• Edit the listbox values as required.
• Save.

Dependent Listboxes

Objective

• Output the listbox content in a different data field, dependent on the input.

Details

• The dependency is reached through a dynamic variable, which is used in the listbox module as filter criterion. Here, the last changed value of the data item is read and written into the filter criterion.

Example

• Task listboxes in the MOD003179 Report to Unplanned Tasks module.
• The tasks of the task listbox are to be output dependent on the project entered in the project data field.

Procedure

• Search or create a dynamic variable for the Project data item (DT472) (in this example: @D3).
• In the project data area of the listbox module, the project data field contains the @D3 filter criterion.

Listbox Functions

Incarnation Listboxes/Incarnation Fields in Listbox Modules

Information

• Incarnations can be used on the listbox data field as well as in the listbox module.
• The combinations and their effect are summarized in the table below.
• The table is to be read as follows: The top line in a field describes the listbox data field, the bottom line describes the field with "value transfer" set.

Value transfer/Listbox data field	Incarnation DI	"normal " DI
Incarnation DI	ID field value is compared to ID field value	displayed field value is compared to ID field value
"normal" DI	ID field value is compared to displayed field value	displayed field value is compared to displayed field value