As Agile e6 customizer/programmer you can use a comfortable browser configuration component. It simplifies the configuration of browsers including structures. You can define abstract structural elements, data elements with their complete menus, preselections of data sets and the drag-and-drop behavior. An integrated access management allows group- and-user-specific access to the browser. The browser configuration mask and the browser default list are the tools for the browser configuration.
You open the configuration mask via Manager -> Menu -> Structure browser-> Browser configuration. It is used to define browsers within browser windows. Each browser must be defined separately.
A browser view is defined by first creating a configuration record, with its explorer flag set, in the header form. It defines the properties of the browser view, such as the text in the tab, any desired user-/group-specific usage, and the top element. The structure results when you define the sub-elements of the top element in the structure list and link it with subsequent configurations in the name field. You can open each subsequent configuration in its own configuration mask with the help of the hyperlink in the name field. There you can define additional specifications. As a rule, the explorer flag will not be set there any more, unless you want to use a subsequent configuration as starting configuration in another context, such as for another user.
*Details about the icon: In subsequent configurations only a folder symbol for indirect relations can be set here. Icons for data elements (direct relation) are only defined via the driving data object (record-independent icon ENTITYNAME.bmp or data-driven icons in column TABLENAME.ICON or calculation field ICON in the browser list).
**Details for tooltip fields: the contents of significant fields of the browser lists provide the text for the data element. Additionally, entries of further fields can be displayed in the tooltip. The tooltip field names must exist in the browser list. When virtual browser lists are created at runtime, for each tooltip field a "*" will be entered in the field Long description-M of the mask-specific field definition. Tooltip fields should only be specified in the browser configuration mask, and not by *-entries in the repository.
In the general data tab you can set functions for the current browser configuration if you want to influence the structure of virtual browser lists including their menus at runtime.
Field name | Type | Explanation |
Pre-selection, Parameter |
LGV, USX | Sets a Pre_Browser userexit (LGV/C). The userexit is executed after the Pre_Mask userexit of the current browser list. It is usually used to preselect data*. |
FLD |
With the pre-selection parameter you can add a search condition for data to be displayed. Example:
Example:
If you choose "FLD" you have only to fill in the Pres.Parameter string with syntax field_name><op><value>[,<field_name><op><value>[,...]]. Possible operators are '=', '<', '>'. The macro "@USER" is supported. The values are put into the query buffer of the fields. Example:
If you choose "USX" you can fill in a non-selection userexit name and provide the Pres.Parameter field with the expected value for the userexit. | |
Drop function |
LGV, USX | Sets a userexit (LGV/C) to control the drop-behavior of the current browser list. The drop function entered here overrides any general EDB-DROP-FUNCTION of the type EDB-DROP-TYPE set in the browser default list. |
Menu function |
LGV, USX | Sets a userexit (LGV/C) to modify menus of the current browser list. The user exit is invoked when the menu is created. You could, for instance, modify Select- or NoSelect function entries to check privileges. |
*As opposed to the DTV default browser call with iwf_brw_lise, the Pre_Mask userexit is supported if the Agile e6 browser configuration is used.
In the structure tab you define the structural elements and their properties. At runtime, the entries create the selections in the Select- and NoSelect menus of the browser list required for relations and context menus:
*Details for the attributes Userexit and Parameter (for D): To create virtual browser lists you can use your own userexits as well. However, iwf_lis_exp is explicitly recommended. It guarantees the use of the browser configuration for the next level and the required control when the structures refreshed.
**Details for the attribute Name: When a structure is created, the configuration records of subordinate structural elements have usually not been created yet. For this reason it is necessary to create the subsequent configuration record in the selection widget. It can be further specified in the browser configuration mask later.
**Details for the attribute Name: You must manually create the dummy configurations SELECT and NOSELECT. However, the predefined names are not obligatory.
In addition to DTV standard, Agile e6 applications can use the following userexits:
In the browser default list of the Agile e6 application you can define the following browser properties globally or user-/group-specifically:
The following example shows the configuration of the browser "My Data" with containing several levels.
The start configuration ENTRYPORTAL defines the browser tab, the top element "My Data" and two folders as elements of the next level.
The subsequent configuration MYPROJECTS defines its own context menu entry (at the folder "My Projekts"), the direct relation "Top Projects" (data only) and the indirect relation "Last Modified Projects" (folder with data).
The subsequent configuration TOPPROJECTS defines the context menu for the data elements of the direct relation "Top Projects".