Editing the Configuration in the Component Configurator

Procedure

The Web Dynpro built-in part of the configuration and the component-defined part of the configuration are modified together using the configuration editor.

Note

You can call the configuration editor in the following ways:

If the configuration exists already, you can display it in the Development Workbench. It is visible in the package display as a sub-item of the component or through the Repository Information System.
If the configuration does not exist yet, choose the component Display/Change Configuration in the context menu. See also Creating a Configuration in the Component Configurator .
Start the Web Dynpro application CONFIGURE_COMPONENT.

In the object list of the ABAP Workbench, choose the component configuration to be edited in a Web Dynpro component and select it by double-clicking.

The properties and administration data of the configuration are displayed.
Choose Start Configuration Editor .

The configuration editor is displayed in the Web browser. Component name and component configuration ID are already entered.

Ensure that the correct values are entered for the component name and the configuration ID.
Choose Change .

The properties are displayed, as is the component-defined configuration data and the Web Dynpro built-in configuration data.
Configure the settings as required.
- The configuration header data is shown in Properties . You can change the description text.
- If the component has a configuration context, the tab for the component-defined configuration is selected by default. Otherwise this tab is not active. For some components there is a special UI, otherwise data is modified using the standard UI of the component-defined configuration.
  
  Structure of the Context
  
  The instantiated objects of the configuration context are displayed in the table on the left. For nodes with a cardinality of 1..*, at least one element is displayed, for nodes with cardinality, no element is displayed initially. The names are generated from node names. For nodes of cardinality *..n, either the index or the unique value of the primary attribute is displayed additionally in brackets.
  
  The following actions are possible for this table in display and change mode:
  - Expanding and collapsing nodes
  - Selecting a node, either in the selection column or simply by clicking on the text.
    
    The attributes are then shown on the right-hand side.
  The following actions are possible for the table in change mode:
  - Adding identical items by choosing Add Identical Element in the context menu.
    
    This is possible for nodes of cardinality *..n.
  - Adding subelements by choosing Add <Name of Subnode> in the context menu.
    
    This is possible if the selected node has subnodes.
  - Deleting a node using Remove in the context menu.
    
    This can be carried out as long as the correct cardinality of the node is ensured.
  - Moving an element.
    
    If a node has multiple elements, they can be swapped with one another. The entries Move to the beginning / up / down / to the end are in the context menu for this, however not all of them are active.
    
    Moves can only ever take place within a parent element.
  Attributes of the current element
  
  On the right-hand side you can change the value of the current element.
  
  The header contains the name of the selected element (the same as that on the left-hand side). A row is displayed for each attribute. This consists of:
  - a Label, which was either taken from the ABAP Dictionary or was generated from the attribute names
  - an input field, a dropdown list box, or a checkbox, depending on the attribute type.
  - a final checkbox
    
    If you set an attribute to final , this attribute cannot be changed in Customizing or personalization. Primary attributes also may not be changed in Customizing or in personalization.
  You can rename a UI element by writing a normal text in the Short Description of the element, or by specifying an OTR alias in the form of $OTR:<package name>/<name>. Example: $OTR:SOTR_VOCABULARY_BASIC/PRINT_STANDARD_LIST
  
  If a primary attribute is defined, this is displayed in the first row and is a required field.
  
  You can then check your settings.
  
  The uniqueness of the primary attitude is tested in the check, as is the type-compatibility of the values. Further checks are not possible in the standard editor. The context hierarchy is also displayed again; the primary attribute value in particular is copied for multiple nodes.
- The tab for the Web Dynpro built-in configuration is active if the component has at least one view, which is usually the case. Here you can make the changes predefined by the framework on the UI. You can change, reset, or set the properties to final for the views and their UI elements.
  
  This tab is active if the component has at least one view (which is usually the case). Here you can make the changes predefined by the framework on the UI.
  
  You can then check your settings.
Note
You can check the consistency of configurations without having to save them. To do this, choose Check .
Save your entries and exit the configuration editor.

Note
The configuration editor determines whether a configuration has been changed. This means that the save pop-up only appears in the configuration editor when a change has been made.