Object Selector
You can use this pattern to search for and list aspect attributes of an object. The pattern is a complete user interface layout, which encompasses the component pattern Search Bar and the Object List configuration.
The Object Selector pattern uses the Search Bar to search for single objects from a list of items based on specific search criteria. You can use the Object List to list objects in either a tabular form or list layout. You can use the resulting UI layout to create new or edit existing objects.
Since the embedded components Search Bar and Object List always remain the same, the only thing that developers can do with the Object Selector is to configure it to their specific needs.
The Object Selector Pattern consists of two parts:
● Object Selector Configurator
This includes the Search Bar pattern and the Object List configuration.
● Object Selector UI layout
The Object Selector Configurator generates use of the Search Bar pattern in the application and launches the Object List configuration. To use the Object Selector, you must configure the Search Bar pattern and Object List and name the Object Selector configuration.
See the Search Bar pattern for more information about pattern configuration and use.
You can use the Object List configuration to structure the layout of objects in a list whereas you can define whether the row of data is displayed in a tabular form or in a list layout. The configuration screen can be divided into three parts: Object Configurator, List and Detail Views, and Application Launch Configurations.
At the top of the Object List Configurator, you can find that Service Module and Query Name entries influence the list of items available from pull-down menus for the Select Object Identifier for display and Tooltip for Object Identifier. The Service Module and Query Name definitions also reflect which aspect fields (Display Aspect Fields) are shown in the list and detail view tables.
By selecting items from a pull-down menu, you define how the displayed object should be identified (Select Object Identifier for display). Youcan also choose the quick info text when the cursor remains on a text or button for a short period of time (Tooltip for Object Identifier). You name the object list header (Header for ObjectList).
You can permit object deletion (Allow delete), define as default the view modus (Detail View as default), or decide if only the list view should be shown (Only List View). You can also select multiple objects for deletion (Allow Mass Deletion). When activated, this action must be named.
In the list and detail views, ESF entries in the columns Name and Description are defined based on the chosen Service Module. However, the detail view configuration limits the display of not more than two fields in the attribute list and not more than three as details in the list.
You can find configurations for launching an application when selecting an object below the Detail View. When activated, you can specify the following for the New and Edit modes of the application:
● Application Name
The application in which WebDynpro configurations are used.
● Development Component
This is the location of the user interface used for this particular component.
● Config name
This is the configuration’s name.
● Window width
This is to specify the width of an application window.
● Window height
This is to specify the height of an application window.
Although the New and Edit modes are essential to Object Selector use, they are separated from the pattern itself. You launch these applications from within the configurated selector interface.
It is possible to define the application based on URLs. Once again, New and Edit modes can be defined with one single configuration by activating Same URL for New and Edit mode. Otherwise specify:
● URL for New Mode
The combination of application name and development component to define a web address for use in the web application.
● URL for Edit Mode
A combination of application name and development component for use in navigating to the web application with the additional parameter1 necessary for identifying the object to be edited.

Based on entries made for the application name, development components, and configuration name, the corresponding URL is generated in the WebDynpro application with the appended parameters app.configName=<Configname> and app.parameter1=<guid> of the selected object instance for editing.
Certain parameters are not defined in the configurator; however, they are equally important in understanding how a application navigates. These parameters are transferred during activation of the New or Edit modes. These three parameters are:
● Parameter1
Contains values connected to the aspect field, which are gathered in the URL launch field of the configurator. This value is referred to as GUID (global unique identifier). The GUID can be retrieved from the context bound to the table.
● Parameter2
Contains the action for the editor “E”, which is the editing object; “N” is the parameter for creating a new one. The parameter will be evaluated by the object editor.
● ConfigName
Contains the value entered in the configuration file field. If no value is entered, then the URL does not contain this parameter.
In the generated screen layout, you see the configuration results of the Search Bar pattern at the top of the layout and below it the configured list display. By clicking Toggle to Detail View, you can see the object list in a more detailed layout, but with the limitations configured in the Object List.
By clicking New, you will be sent to the Submit Idea layout for new idea generation. By clicking Edit, you can then edit an idea.