Component Configuration
With the component configuration, you can control the behavior of each individual component within a Web Dynpro application or the user interface of individual views. For each component, several records of configuration data can be created. This kind of data record contains different types of attributes, Web Dynpro built-in attributes, component attributes, and administration data.
A component configuration consists of:
-
General administration data
-
Component-defined configuration data
The availability of a configuration controller in the component is a prerequisite.
On the left-hand side of the configuration editor is a hierarchical list of available context nodes with associated elements, whereby each element can have attributes. The number of elements and the attribute values can be changed. The number of elements can only be changed if the nodes were defined with 0..1, 0..n, or 1..n.
-
Web Dynpro built-in configuration data
On the left-hand side of the configuration editor is a hierarchical list of views and the UI elements located in them. Next to this list on the right-hand side are the changeable properties of each UI element selected on the left.
Note that a configuration is a TADIR object. This means that you need developer authorization to be able to work with this object.
Customers cannot simply change configurations delivered by SAP (regardless of whether the configuration is an application configuration or a component configuration).
Header Data
This general administration data includes the following:
-
Name of the configuration
-
Text description
-
Name of the associated component
-
Package assignment
-
Original language
-
User name of the creator and date created
-
Last changed by/on
Component-Defined Configuration Data
You can change the appearance and behavior of a Web Dynpro component. These changes can be implemented through additional attributes in the context of a special custom controller the configuration controller.
You can create any number of custom controllers for a Web Dynpro component. You can select only one of these custom controllers as the configuration controller. To do this select a controller in the object list, and from the context menu choose Set/Reset as Configuration Controller . In the same way, you can set the controller back to a simple custom controller.
Example of component-defined configuration:
Your system contains a package called SWDP_TEST with an example component called WDR_TEST_PERS_IMP_EXP. The last column of a simple flight table displays one of three note icons: A red circle, a yellow triangle, or a green square, depending on the occupancy level of the flight. The value defining the occupancy level at which the system should switch from one reference icon to the next can be configured by the application developer. For this purpose, the two attributes CONFIG_LOW and CONFIG_HIGH were created in the configuration controller context of this component. These two attributes set the limit values defining the occupancy for which the icon is low (green square) or high (red circle). If the occupancy level is between the values, a yellow triangle will appear in the table.
In contrast to Web Dynpro built-in configuration features, such attributes must be created explicitly in the configuration controller context. Therefore, the processing of attributes must also be explicitly programmed by the application developer in a controller method of the component. In the WDR_TEST_PERS_IMP_EXP example component, the logic for evaluating the attributes is entered in the WDDOINIT method of the component controller. Storing the attributes in the context of the configuration controller ensures that their values can be set or changed later with the help of the component configurator.
When you create a node in the configuration controller context, singleton nodes and recursion nodes are not allowed.
Web Dynpro Built-In Configuration Data
Each UI element has a set of properties defined by the framework. Their values are set when a view is designed. As a result, almost each UI element has a visible property. In the view designer of the ABAP Workbench, an application developer sets the value, for example, to visible . Within a special application of the component, precisely this UI element, however, should not be visible. The application developer then creates a configuration for the component in which the value for the property visible is set to none .
The value of the visible property is an example of a possible Web Dynpro built-in configuration type. This property is preset by the Web Dynpro framework and the value set by the application developer is processed automatically. There is no additional programming effort required by the component developer for Web Dynpro built-in configuration.
Many (not all) of the attributes of UI elements can be overridden with the help of configuration data.
Where-Used List
A where-used list of components in component configurations and of component configurations in component configurations is available.
You can display this in the Web Dynpro Explorer by selecting the relevant component configuration in the object list and choosing Where-Used List in the context menu. The corresponding uses are listed.
Functions of the New Configuration Editor for Component Configuration
More information: New Configuration Editor