FIORI_SAPUI5intermediate
Launchpad Administration and Content
How apps reach users in the SAP Fiori launchpad: catalogs, target mappings, intents, spaces and pages, roles and troubleshooting missing tiles.
Overview
How apps reach users in the SAP Fiori launchpad: catalogs, target mappings, intents, spaces and pages, roles and troubleshooting missing tiles.
Lessons in this topic
- Fiori Launchpad Part 1: Catalogs, Tiles and Target MappingsUnderstand the launchpad content model: technical and business catalogs, tiles that users click, target mappings that resolve an intent to an app, and how semantic objects and actions make navigation work across apps.
- Fiori Launchpad Part 2: Spaces, Pages and Business RolesDesign what users see on the launchpad with spaces and pages, connect them to business roles and PFCG roles, and decide between SAP-delivered business roles, copies and custom roles.
- Fiori Launchpad Part 3: SAP Build Work Zone and Content FederationBring apps from several systems into one entry point: SAP Build Work Zone on BTP, content federation from S/4HANA and other providers, roles exposed from ABAP, and when a central launchpad beats system-local launchpads.
- Fiori Launchpad Part 4: Troubleshooting Missing Tiles and Apps That Don't StartDiagnose the classic launchpad tickets — tile not visible, 'could not open app', blank screen, wrong app version — by checking roles, catalogs, target mappings, app index, caches and back-end services in a fixed order.
Interview questions covered
- Explain how the Fiori launchpad decides which app to open when a user clicks a tile or a link.
- How do you design Fiori roles for an S/4HANA rollout?
- How would you provide one launchpad across S/4HANA, SuccessFactors and custom BTP apps?
- A user says their Fiori app doesn't work. How do you troubleshoot systematically?