Entering content frame

This graphic is explained in the accompanying text Window: Inbound and Outbound Plugs Locate the document in its SAP Library structure

Just like each view, each window has a number of inbound and outbound plugs. For basic information about the plugs in a window, see Structure linkWindow Plugs in the architecture manual.

Inbound Plugs

On the Inbound Plugs tab page you can create a number of inbound plugs for the window that is currently being edited. Enter a new name for this plug and add a description of it.

The properties of a window’s inbound plug differ from a view’s inbound plugs by the characteristics Interface and Start that can be maintained:

·        Interface

This checkbox determines whether the window’s inbound plug only is used for navigation within the component, or whether the inbound plug should also be visible externally as part of the Structure linkcomponent interface. If the Interface checkbox is selected, the inbound plug that is now externally visible is also displayed as part of the interface view belonging to the window in the object list node Component Interface. The inbound plug can only be changed in the window editor, however.

·        Start

This graphic is explained in the accompanying text The property Start is only relevant to inbound plugs of the interface view.

If the property Start is selected for such an inbound plug, this means that a Web Dynpro application can be started using this plug. When you create a Structure linkWeb Dynpro application, you can only select these interface view inbound plugs that are selected as a start plug. Such inbound plugs that do not have the Start property are available exclusively for navigation to an already-running application.

Unlike outbound plugs, inbound plugs can be equipped with an event handler. This Structure linkevent handler of an inbound plug is always called if the window is controlled using precisely this plug.

Outbound Plugs

Parallel to inbound plugs, a window can have outbound plugs. You can use an outbound plug to leave a window for a view of an embedding window. Outbound plugs can be called in two different ways:

·        Using the generated method WD_THIS®FIRE_<MY_OUTBOUND>_PLG.

·        Using the generic method FIRE_PLUG of API IF_WD_VIEW_CONTROLLER for the current controller.

Even the outbound plugs of a window have two additional checkboxes compared with a view’s plugs:

·        Interface

This checkbox determines whether the window’s outbound plug alone is used for navigation within the component, or whether the outbound plug should also be visible externally as part of the component interface. If the Interface checkbox is selected, the outbound plug that is now externally visible is also displayed as part of the interface view belonging to the window in the object list node Component Interface. The outbound plug can only be changed in the window editor, however.

·        Exit

This graphic is explained in the accompanying text The property Start is only relevant to outbound plugs of the interface view.

If an embedded window is left using a plug with the property Exit for a view of an embedding window, then the component that belongs to the inner window is also ended automatically. Calling an exit plug in the outermost component leads to the whole Web Dynpro application ending.

You can specify importing parameters for an outbound plug. These parameters are passed to the outbound plug when method WD_THIS®FIRE_<MY_OUTBOUND>_PLG is called. For more information about this, see WD_THIS and the Local Controller Interface in the programming manual.

 

 

Leaving content frame