A window defines the superset of all possible views that a Web Dynpro application could require whilst running a particular component. To arrange multiple views within a window, you can choose between two strategies:
● View Set
You choose between various basic layouts to position the views on the screen.
● ViewContainerUIElement
You create several ViewContainerUIElements and arrange them in the required order on the screen. Within each of these ViewContainerUIElements you can embed several views. Only one of these views within a ViewContainerUIElement however will be rendered at any one time. Which of those views is visible is determined by the navigation implementation
We recommend to use the ViewContainerUIElement, as views can be arranged in large variety of ways in order to achieve the desired layout on the screen.
More information: View Navigation Plugs and Navigation Links
The number of views visible at any one time, will typically be only a subset of the number of views embedded within the window. The subset of views rendered at any one time is known as the View Assembly, made up by one view within each of the ViewContainerUIElement. User interaction followed by subsequent navigation processing will frequently cause this subset of views to change with every server round-trip.
The view assembly represents those views seen by the user on their client device after the completion of a particular server round trip.
How does the Web Dynpro framework decide which particular views make up the current view assembly? There are two answers to this question:
● When an application is executed for the first time, only those views which have their default flag set to true will belong to the first view assembly.
● Thereafter, user navigation will occur and the view assembly will be composed of those views that have been newly instantiated and those views that persist from the previous view assembly.