Specifying Dataflow 

The Web Dynpro technology provides model units for accessing an existing backend and controller units for data processing. Each application controller owns a context which is the active part of the unit. The layout unit view as well as all controller types are involved into the application’s dataflow and therefore need to be defined. The tool Controller Editor provides graphical support for value and attribute definition for all controllers.

Using Java classes From the Backend

For dataflow definitions, you would bind the controller contexts to the Web Dnypro Model. During model import, the model classes are generated which are then the source for data transfer to the controller context. Model binding therefore describes the main procedure when it comes to getting data for the application.

More Information: Binding Context to the Model

Data Binding

The properties of a user interface element contained in the view can be bound to attributes of the corresponding view context where multiple properties can be bound to one context element. This enables the context data to be displayed in the browser. Vice versa, any user changes to the view are stored in the view context.

More information: Binding data

Mapping Data Between Contexts

When data is transferred between the controller contexts this is called “mapping”. Data value copies are passed between the several controllers. The controller which is always involved into this dataflow process is the component controller; optionally, custom controllers can be additionally created and be used for dataflow purposes. Since passing data between the view and the controller is called “data binding”, the view context is not involved into the mapping scenarios.

More information: Context Mapping