Pages

Page Configuration

The information about a page configuration is stored client-wide.

Information includes the names and positions of the CHIPs presented on a page, and also the CHIP catalog available to the user for adding CHIPs to the page content.

The page configuration is made of the following technical configurations:

• An application configuration of application WDR_CHIP_PAGE

• A component configuration of component WDR_CHIP_PAGE

• A component configuration of component WDR_CHIP_CATALOG

Configuration Layer

There are three different configuration layers based on the Web Dynpro ABAP configuration framework:

• Personalization

  Personalization is the top layer. Users can change the layout of the page, and add or remove CHIPs. Personalization options can be changed in customizing and in the configuration.

• Customizing and Configuration

  Customizing and configuration are the two layers below personalization. In these layers you can use all the Page Builder functions, and create pages in the runtime authoring environment of the Page Builder. You can adapt the page and the individual CHIPs to the requirements of your users. The differences between customizing and configuration lie more in the scope of the adaptations rather than in their functions. In customizing changes apply to a specific client whereas the changes an administrator makes in the configuration apply system-wide.

Delta Handling in the Page Builder

The effect changes have on the respective layers above differs between the Page Builder and Web Dynpro ABAP configuration framework. Delta handling in the Web Dynpro ABAP configuration framework is deactivated.

With Page Builder the following rules apply for delta handling of the configuration:

• If a specific layer is created for the first time, the lower layers inherit the data. This means, for example, that when a page is opened in personalization, and a customizing already exists for this page, it will be displayed.

• Not only are delta changes saved, each layer is saved separately too. This is why changes in the lower layers are not visible in existing configurations of higher layers.

• Delta handling of configurations in Page Builder result in:

  • Personalization that is no longer current is deleted if data has been changed in a lower layer (customizing/configuration).

  • If customizing is no longer current, the end user is notified but can continue working.