Lesson 3 of 6
Related apps and navigation
7 min
Business processes cross objects: a supplier has purchase orders, purchase orders have goods receipts and invoices, invoices have journal entries. Fiori is built to let you follow those links without hunting for the next app. Knowing how navigation works also explains why a link sometimes does nothing for you while it works for a colleague.
Ways to move between objects
| Navigation element | Where you find it | What it does |
|---|---|---|
| Smart link | Underlined values such as a customer or document number in a table or object page | Opens a quick view with key facts and a list of apps you can jump to |
| Related Apps button | Object page header in many apps | Lists apps that work with the same object, opened in context |
| Process flow or related documents section | Object pages of documents | Shows predecessor and successor documents with links |
| Card or KPI drill-down | Overview pages and KPI tiles | Opens the app behind the figure with matching filters |
| Back and breadcrumbs | Shell bar and page header | Returns along your path with the previous state restored |
Intent-based navigation
Fiori links do not point to a specific app. They point to an intent: a semantic object (a business object such as SalesOrder, Supplier or AccountingDocument) plus an action (such as display or manage). The launchpad resolves the intent to a target app using target mappings in the catalogs assigned to your roles. You can sometimes see this in the browser address: the part after the hash sign looks like #SalesOrder-manage.
- You clickA smart link on sales order 1000457
- IntentThe app asks the launchpad for SalesOrder plus an action
- ResolutionThe launchpad looks for target mappings in your assigned catalogs
- ResultIf found, the target app opens with the order; if not, the link is hidden or navigation fails
Why links depend on your roles
Because resolution uses your catalogs, two users can see different navigation options on the same screen. If Maria's roles include the target app for an intent, the smart link offers it; if Dan's roles do not, the option is missing for him, or he gets an error that the app could not be opened. This is by design: you cannot navigate into an app you are not allowed to use. It also means that a broken link in testing is often a role problem, not an app defect.
- Does the link or Related Apps entry appear at all?No → the target is not in your catalogs; compare roles with a colleague · Yes → continue
- Does the target app open?No, error that it could not be opened → missing role, target mapping or service; raise with app ID and intent · Yes → continue
- Does it open with the right object and filters?No → parameter passing issue; capture the address and steps · Yes → navigation works
Keeping your place
Use the browser or shell Back button to return; Fiori restores the list with your filters. Opening a link in a new browser tab works for most apps and is handy for comparisons, but be aware that each tab may hold its own draft if you edit.
What would you do?
In Contoso UAT, Dan reports that the "Manage Supplier Line Items" entry is missing from Related Apps on the supplier object page, while Priya sees it. What is the most likely cause?
- Use smart links, Related Apps, process flows and card drill-downs to move between objects in context.
- Links target an intent (semantic object plus action), resolved through target mappings in your catalogs.
- Different roles mean different navigation options; a missing or failing link is often a role issue.
- Test cross-app navigation with production roles when the process depends on it.
Check your understanding · not graded
Lesson check
1. What is an intent in Fiori navigation?
2. Why might a colleague see a navigation option you do not?
3. What does a smart link typically open?
4. A link fails with an error that the app could not be opened. What should the ticket include?