!--a11y-->
Part 5: Setting Up Navigation 
Up to now, you have
designed the two views and have set up transporting the value of attribute
CARRID using the three relevant contexts. In the last step, you need to
create the
navigation between
the two views. It is part of the window
unit and is therefore
defined there. First of all, you have to create the plugs that are required
for navigation for the two views.
1. Switch to the view of the SEARCH view and create an outbound plug for the view on the corresponding tab page. Call this plug "SEARCH_out".
2. Return to the Layout tab page and select the Button layout element type.
3.
In the
corresponding properties table, create an
action
for the OnAction
event.
To do this, click on the Create
button on the right,
enter a name for the action ("Go_to_SEARCH_out") and then select the
SEARCH_OUT outbound plug you just created. Confirm the dialog box.
The method ONACTIONGO_TO_SEARCH_OUT was created and automatically implemented with the call of the outbound plug you selected.
4. Switch to the view of the DISPLAY view.
5. Create an inbound plug called "DISPLAY_in" and save the view.
6. Switch back to the view of the window of the component.
7. Now embed the DISPLAY view in the window structure (see Part 2).
8. Expand the hierarchy of all window elements and use the context menu of the outbound plug element of the SEARCH view to create a navigation link to the inbound plug of the DISPLAY view.
9. Save and activate all inactive parts of the component.
10. Test your application again.
This completes the simple Flight Info application. Entering an airline ID displays in a table all flights that were entered for this row in DDIC table SFLIGHT.
Of course, the sequence of the steps for
creating this example application is not binding. You can vary the sequence in
many places when you create your next application.