Side panel applications can cause a significantly higher load on the back end because each stateful side panel application (for example, Web Dynpro) has a back-end session running.
Side Panel Defined in PFCG
If a user navigates to a different target that has a side panel application defined in transaction Role Maintenance ( PFCG), the side panel application is loaded and displayed in the right panel. Initially, only the first side panel application is loaded and displayed if more than one is defined for a navigation node. The other side panel applications are only loaded if the user explicitly selects them using a selector. In the following example, the first side panel application (EPM Map) is loaded and displayed initially. The concept explained above is shown in the following figure:
Once loaded, the side panel application, including its corresponding back-end session, remain started even if the side panel is not visible (not selected). The session of the previous side panel is still active in the background. After navigating from node 1 to node 2, all side panels of node 1 that are not side panels of node 2 are closed. The last used side panel of each navigation node is persisted and restored if the user returns to that node.
Example: Node 1 (for example with dynpro application) has the side panels A, B, C, and D defined. Node 2 (another dynpro application) has side panels A and D. Only the overlap of both side panels is available after the navigation process. In this case, only side panels A and D are present after navigating, while side panel applications B and C are terminated. The concept described above is illustrated in the following figure:
If the side panel is pinned, it is not closed after a navigation process. Its back-end session remains active. To pin a side panel, choose the pushbutton.
Local Side Panel
Local side panels are present at each navigation node and displayed at the end of the selection list. To configure local side panels, choose
.