Launchpad Content Management

A business wants one tile showing the live count of open orders, and another showing a rolling feed of internal announcements. Which tile type for each, and what breaks if you reach for a static tile on the order count?

A user logs in and sees no apps even though the right catalog exists and contains their tiles. Walking the FLP content chain, what is the most likely missing link?

When you create a standard catalog in the FLP designer, what two things actually live inside it - and what conspicuously does NOT?

A static App Launcher tile renders fine but clicking it goes nowhere. Its Navigation section has a valid semantic object + action. What do you check next?

A colleague wants to group all the apps of one sales-order scenario, and sets the intent's semantic object to . Why is that backwards, and what does actually do?

Your launchpad designer changes are stuck as local objects. Walk the steps to make them transportable - including the request type and the one designer setting people forget.

A custom tile referencing a brand-new semantic object you just typed in will not navigate. What prerequisite was skipped, and when does this NOT bite you?

Intent-based navigation is said to 'decouple' navigation from app addresses. What actually holds the app target - and what is the operational payoff?

A custom catalog exists. Walk how its tiles reach actual users through PFCG - and what must the user still do afterward that surprises people?

What does transaction LPD_CUST contribute when building custom catalogs - and what are the three things you set up in it?

A custom role's PFCG menu can carry a SAP Fiori Tile Catalog node and a SAP Fiori Tile Group node. What does each do, and what goes wrong if you include only the catalog?

A user on a phone cannot see a tile that works fine on desktop, and authorization is correct. Which target-mapping General setting explains it, and what does it actually control?

The launchpad designer can run with launch scope CUST or CONF. Which one captures catalog/tile changes into a Customizing request, and what is the practical default?

A standard catalog bundles Create and Change Sales Orders, but user A must be able to create only. Why is assigning the standard role the wrong move, and what do you build instead?