Important Classes and Interfaces for Page Builder

Features

Name

Description

Implementation/Examples

General Page Builder

IF_CHIP_API

Enables access to Page Builder services, for example,

  • Layout

  • Event handling

IF_CHIP_DEFINITION_MODIFIER

Used for changing CHIP parameters and custom parameters

Adapting the CHIP Catalog

Determining the Category for Sorting in the CHIP Catalog

Example:

  • Web Dynpro Component and CHIP of the same name: WDR_TEST_LS_DATA_CONTEXT with help class CL_WDR_TEST_LS_DATA_CONTEXT

  • Web Dynpro application: WDR_TEST_CHIP_CATALOG_ANALYSIS

CL_CHIP_API_UTIL

Enables access to IF_CHIP_API for embedded Web Dynpro components

Implementing CHIPs Dynamically

Side Panel

These classes are required in Web Dynpro applications

CL_WD_SIDE_PANEL_API

Enables access to the side panel embedded in the Web Dynpro application

Preparing the Web Dynpro Application

Example:

Web Dynpro application: WDR_TEST_HELP_SP

CL_CHIP_WD_CANVAS_MANAGER -> IF_CHIP_WD_CANVAS_MANAGER

Enables automatic data exchange for a Web Dynpro application in the content area of the NWBC using the NWBC context.

Enabling Tagging of a WD Application in the NWBC Content Area

CL_CHIP_WD_SIDE_PANEL_MANAGER -> IF_CHIP_WD_SIDE_PANEL_MANAGER

Enables automatic data exchange for a Web Dynpro application in the side panel of the NWBC using the NWBC context.

Same process as described in Tagging of a WD Application in the NWBC Content Area.

Tagging

IF_WD_TAG_PROVIDER

Enables the implementation of your own tag provider.

Implementing Tag Providers

Example

CL_WD_TAG_PROVIDER_SAMPLE

IF_WD_TAGGING_SERVICE

Enables tagging, which was programmed in the source code, at runtime. In this way context attributes can be provided with tags that are not visible on the user interface.

Setting Tags for a Web Dynpro Application