In this series of blogs I will cover some of the new features in WDA available in Enhancement Pack 2.
Panels
In part 1 of the series I am going to talk about Panels. Panels are essentially the replacement for Tray and Group.
At this stage I assume that anyone reading this blog knows how to create a simple WDA. If not then might I suggest you check out Thomas Jung’s superb blogs which can be found here.
Creating the Panels
Swapping Root Element
Creating a panel in WDA is simple. The first step is the swap the root element in your view. This is achieved by right clicking on the ‘ROOTUIELEMENTCONTAINER’ the selection ‘Swap Root Element’.
This will act as the container for individual Panels.
Select the type ‘PanelStack’.
Although I created the PanelStack by swapping the ROOTUIELEMENTCONTAINER this PanelStack can be created anywhere in the view.
Root Element Properties
The elements in the table are generally set by default but it’s always worth double checking.
|
Property |
Value |
| CollapseMode | toHorizontalLine |
| stackDesign | tab |
Inserting Panels
Once the container is created we can add the individual panels. Each panel will represent a tab.
To insert the panel click on the new ROOTUIELEMENT and select ‘INSERT PANEL’.
Repeat this process as many times as necessary depending on the number of tabs required.
Panel Properties
|
Property |
Value |
| Layout | FlowLayout |
| contentDesign | Fill |
| Title | “Name of the Panel” |
Finished Product
OK, this is what the finished product will look like.
Features
OK, now that I have shown how to create a Panel I should explain some of the features of Panels.
CRM UI
The visual design of the PanelStack / Panel is the same as in CRM. This is to provide more consistency for the end user for these two UI frameworks.
Dynamic Titles
One of the key features of panel is that titles can be changed by the user.
Order of the Panels
Another key feature of panels is that the order of the panels can be changed by the user with the use of Drag’n’Drop.
This features give the user more freedom with the screen layout.
An example of this is is the OVP component of FPM.
Note: The OVP component is only available as of Netweaver 700 EHP 2.
