Comfortable Browser Configuration for Agile e6

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.


The Browser Configuration Mask

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.


Attributes in the Header Form

Field name Explanation
Name Unique name of the browser configuration record
Id (user, group) Controls the group- or user-specific usage of the browser configuration
Title and description For start configuration: Sets the title in the tab and the top element, e.g. "Entryportal".
Icon* For start configuration: Sets the icon in the tab and for the top element, e.g. "entry.bmp". For subsequent configurations: Sets the icon for indirect relations.
Tooltip fields** For subsequent configurations: Comma-separated list of fields. The data in these fields appear in the tooltip at the data element.
Active For start configuration: Controls browser visibility.
NULL = Browser deactivated. The tab is invisible in the browser window.
ON = Browser active. The tab appears in the foreground after the browser window has been opened.
OFF = Browser is in the background and can be activated by the tab.
Details: You should set the active-flag for only one browser. If several or no browser at all are set active, the "ACTIVE-VIEW" will be applied. It is set in the browser default list.
Explorer Identifies the configuration as start configuration.
Close For start configuration: Activates or deactivate the Close button in the tab.

*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.


Attributes in the "General Data" Tab

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

Direct entry of field names and search criteria for preselecting data. Entered in the parameter field as comma-separated list of search criteria of the form "FIELDNAME1 = Value1, FIELDNAME2 = Value2, ...".
Possible operators are "=", "<", ">".
The macro @USER is supported.

With the pre-selection parameter you can add a search condition for data to be displayed.

Example:
If you choose "LGV" and use the standard LGV procedure for pre-selection "PrpExplorer/PreSelect" the the Pres.Parameter string is added to the mask join condition. Therefore, the parameter string must follow the mask join syntax.

See also userexit mas_set_joi_mas.

  • The string may not contain any spaces.
  • Several conditions can only be linked using AND combination ('&').
  • As comparison parameters, operators '<', '>', '!', '=' are allowed.
  • The value must be preceded by the datatype with a colon (I:, F:, S:, D:, L:, M:)

Example:

  • T_PRO_DAT.STEP_DESCR=S:ABC
  • T_PRO_DAT.AGG_FLAG=I:0
  • T_PRO_DAT.BOM_FLAG=T_PRO_DAT.AGG_FLAG
  • T_PRO_DAT.AGG_FLAG=I:0&T_PRO_DAT.BOM_FLAG=I:0
  • T_PRO_DAT.AGG_FLAG=I:0&T_PRO_DAT.STEP_DESCR=S:DER

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:

  • T_PRO_DAT.STEP_DESCR=ABC
  • T_PRO_DAT.AGG_FLAG=0
  • T_PRO_DAT.AGG_FLAG=0,T_PRO_DAT.BOM_FLAG=0
  • T_PRO_DAT.AGG_FLAG=0,T_PRO_DAT.STEP_DESCR=DER

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.


Attributes in the "Structure" Tab

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:

Field name Entry Explanation
Structural object type Defines the -> structural elements of the next level
D Data elements. Define a relation. The selection with iwf_lis_...-call is automatically added to the Select menu of the browser list. Dependent elements of displayed below the parent element.
H Folder. Defines a static structural element without data, for instance to classify or group other elements. In browser start configurations, several folders directly below the top element are often defined that way.
N NoSelect menu entry. The selection is automatically added to the NoSelect menu of the browser list. It is offered in the context menu at folders of indirect relations.
S Select menu entry. The selection is automatically added to the Select menu of the browser list. It is offered in the context menu of data elements.
Relations type Controls the-> display and behavior of relations
I Indirect relation, only useful for the structural object types D and H (in case of H, only because of the visibility control via the relation flag)
D Direct relation, only useful for structural object type D
F Fix relation, only useful for structural object types D and H, (in case of H, only because of the visibility control via the relation flag)
N No relation, required for structural object types N and S
Userexit and Parameter* iwf_lis_exp For data (D): Userexit iwf_lis_exp with parameter in the form userexit:parameter (e.g iwf_lis_ent ... or iwf_lis_ref ...) to call a subordinate browser list.
For folders (H): Userexit iwf_lis_exp with parameter @EXPLORER. In this case the next browser configuration is addressed.
Menu userexit For menus (N,S): function call for NoSelect- or Select menu of the browser list
Name** Configuration name For data and folders (D,H): Name of the next configuration record. The record can be displayed in a new configuration mask via hyperlink.
SELECT
NOSELECT
For menus (S,N): Dummy configuration names.

*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.


Browser Userexits and Variables (in Addition to the DTV Standard)

In addition to DTV standard, Agile e6 applications can use the following userexits:

Userexit Short description
brw_exp_cal_exp Calls all available browser views for the current user/group. The Active flag controls which view is currently active.
The name of a view can be optionally specified in the form brw_exp_cal_exp "VIEW=Name of view". If the view is already open, it will be shifted to the foreground.
iwf_lis_exp Calls the next browser configuration.
iwf_lis_uni Generic userexit to create relations in the Select menu of browser lists. The userexit invokes any other userexit.

In the browser default list of the Agile e6 application you can define the following browser properties globally or user-/group-specifically:

Variable Explanation Value
ACTIVE-VIEW Name of the default browser view. This view is automatically set active when the browser window is opened if the Active flag is set for no or several browser views. Browser name
EDB-DROP-FUNCTION,
EDB-DROP-TYPE
Sets a userexit (LGV/C) to control the drop behavior in all browser lists. The general drop function/type entered here could be overwritten by a configuration-specific drop function. Userexit name
RELATIONS-TITLE Sets the text next to the checkbox for hiding indirect relations, e.g. "relations". If no value is assigned to the variable, the checkbox will not be displayed. Text
SHOW-QUANTITY Activates or deactivates the display of the number of dependent elements at folders of indirect relations, e.g. "Projects [5]". So the users get an idea of the amount of dependent data even if the node is closed. y, n


Example Configuration

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".