In Web Dynpro, you pass data between views using context mapping and component interfaces. The most common approach is to use the component controller's context as an intermediary: bind source view elements to the component controller's context, then bind the target view to the same context nodes. This automatically synchronizes data across views.
Alternatively, use view container outbound plugs with parameters. When navigating between views using a plug, you can pass data through typed plug parameters that flow into the target view's inbound plug. The receiving view accesses this data and populates its context accordingly.
For more complex scenarios, use component interfaces: expose context nodes or methods through the component's public interface, allowing other components to access and modify data. You can also use application context (if integrated into your system) to share data across multiple components and views.
Within a single component, the simplest pattern is context-based: create a context node in the component controller, map it to both views, and bind UI elements to these mapped contexts. Changes in one view automatically reflect in the other through the shared context.
For navigation, use the plugName() method on navigation links or buttons, passing parameters through the outbound/inbound plug mechanism. This creates a clean separation between view logic and data flow, making the code maintainable and testable across different view transitions.