Hi Manish,
The interface view is directly coupled to a Web Dynpro window and is automatically created when a Web Dynpro window is created. It represents the connection between both the Web Dynpro application that can be called by the user as well as a Web Dynpro window of a different component, if necessary. In this way, Web Dynpro windows can be used for cross-components.
In defining the start up plug for the application to decide which view should the application start at, we need to define the interface view of the window which holds the view. So, the hierarchy is like COMPONENT>WINDOW/its INTERFACE VIEW/VIEW. We can define the default view of the window by changing the default property of the view as true. But to decide the default window of the application, we nned to pick up the window's interface view in start up plug.
Also, I would like to state one important use of it. We can navigate from iView to another in a window using plugs in view. But, in order to navigate from one window to another, we need to use plugs in source view and those in the interface view of another window. Using interface views, we can even navigate between components within a DC.
Regards,
Tushar S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.