If a user tries to access an invalid pattern that does not match any of the configured routes, they should be notified that something went wrong.
![](/service/media/topic/a6ce8cc2-9aa5-424b-8471-a1a32683fe88/UX400_23_Navigation_36.png)
To implement this feature, the bypassed
property is available in the routing configuration. Using this property, you specify the navigation target that is used whenever no navigation pattern is matched. If you use this setting, you also have to define a corresponding target in the targets
section.
![](/service/media/topic/a6ce8cc2-9aa5-424b-8471-a1a32683fe88/UX400_23_Navigation_37.png)
In the example shown, the routing configuration in the application descriptor has been extended by adding the bypassed
property. It tells the router to display the notFound
target in case no route matches the current hash.
The notFound
target is configured in the targets
section. It loads the XML view sap.training.exc.view.NotFound
without animation (show
transition) into the pages
aggregation of the UI control with the app
Id.
Note
To display routing related error messages on a view, you can use thesap.m.MessagePage
control.