Display and behavior of structural elements of one level/relation is controlled by the definition of the driving browser list. The following picture and the corresponding explanations show the possibilities you have.
The continent of the significant fields of the browser list place the text next to the element symbol. If the number of significant fields is bigger than 1, the contents are separated by "-" (minus). If significant fields are empty, separation is suppressed. The separation character cannot be customized.
*(Agile e6 only) In the tooltip at the data element the contents of additional fields can be displayed. For details information cf. browser configuration for Agile e6, tooltip fields.
Individual data elements are automatically hidden, if the corresponding record contains a #DIR in its first field (lowest position number). This allows you for instance to hide the top data element in order to display folders immediately on the first level.
The context menu at data elements is the Selection menu of browser lists. This menu contains all selections whose function call is different from iwf_lis_... . Selections with Userexit calls iwf_lis_... for calling additional browser lists are automatically hidden.
The context menu at folders of indirect relations is the NoSelect menu of the browser list. This menu contains all entered selections.
Any NoSelect Button areas installed at browser lists are not evaluated.
A relation is created by a selection with an iwf_lis_...-call in the Select menu of the browser list. The display and behavior of the relation are controlled by the selection text (indirect, direct and fix relation).
*(Agile e6 only) Following the selection text of folders of indirect relations, the number of contained data elements can be additionally displayed. For further information cf. -> Browser configuration for Agile e6, Variable SHOW-QUANTITY.
**(Agile e6 only) Every browser can contain an option (check box) for hiding the indirect relations. If this option is active, all the folders and their corresponding dependent elements are hidden with the exception of the relations defined as fix. This checkbox is only displayed if the Agile explorer default-entity EDB_EXP_DEF exists with a string value for the browser variable RELATIONS-TITLE which must not be empty. If no such entity exists or no value is assigned to the variable, the checkbox will not be displayed. For further information, cf. -> Browser configuration for Agile e6, Variable RELATIONS-TITLE.
The Select_Action userexit can evaluate click- or double-click actions on elements in the browser. Usually you want to open a form displaying data of elements. This (Dataview) standard behavior can be installed by calling cch_sel_dtv and passing a parameter string as it is required for the userexit iwf_frm_lis, e.g. cch_sel_dtv MED-ARTIKEL MED-ARTIKEL-SFR1. Then the specified form will open at click or double-click. After a click or double click on another element of the same level the data of the form will be exchanged. For special evaluations (for instance different actions after click or double-click) an individual userexit can be installed at the Select_Action trigger.
cch_nop_cop is recommended as Edit_Action userexit. It prevents copy and taste operations into the browser with drag-and-drop.
Please note that browser lists are opened virtually and the Pre_Mask trigger does not work (does not apply to Agile e6-configurations).
For all elements that can be displayed in the browser window an icon can be defined. The required icons must be created as bitmaps (.bmp) of the size x pixels and stored in a directory defined by the client environment variable DATAVIEW_CBRW. Other bitmap sizes are not allowed and will not be displayed. The color Grey (RGB value = 192,192,192) is automatically recognized as background color and switched to transparent mode. There are two ways to integrate icons:
In order to integrate similar icons for elements of one level (for instance all items with the same icon) you will have to create an icon with name ENTITYNAME.bmp.
Note! Entity-specific icons can also be used for mask titles. Then it is useful to store the icons in the .bmp or .ico directory of the client and not to set the path for DATAVIEW_CBRW.
In order to integrate different icons for elements of one level (for instance a special icon for each item) you will have to extend the master table by one field with the name TABLENAME.ICON and to display this field in the browser list. After that the element-specific icon names have to be entered in the field using the form name.bmp.
Note! It is also sufficient if the browser list contains a calculation field with the name ICON. This field can then be supplied with the icon names via software.
When elements are displayed, the browser first looks for element-specific icons in the field TABLENAME.ICON or ICON. If the entry there is empty or if the field is missing, the browser looks for an entity-specific icon. If there is none, the "green can" will be used as default icon. It cannot be customized.