Launchpad and site content
Getting apps, cards, pages and workspaces in front of users in an application launchpad or portal, including content providers, content packages and access roles. Serving the application’s files is app hostingApp hostingWhere a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.SAP only; extending the surrounding shell is launchpad pluginsLaunchpad pluginsExtending an application launchpad’s shell rather than an individual app: adding header buttons, user-menu entries, frame areas or background behaviour shared across the apps it hosts. A development sandbox for launching an app is a separate concern.SAP and community, unassessed.
Overview
On BTP the question is how content reaches a site: federated from a content provider, or installed from a content package, then assigned to roles. The site can be a launchpad or SAP Build Work Zone site, holding apps, cards, pages and workspaces.
SAP Build Work Zone creates an HTML5 Apps content provider on subscription, and every HTML5 app deployed to the subaccount appears in it, to be added to groups, catalogs and roles and assigned to a site. The advanced edition also installs content packages: ZIP files bundling UI Integration cards, workflows, workspace templates, home pages and workspaces.
Not covered: At the subaccount. An app has to be deployed to the same subaccount as the Work Zone subscription, and the content provider has to be updated in the Channel Manager after each deployment before a site shows the change.
The repositories answering this in the batch are SAP-samples templates and sample apps, which demonstrate rather than provide, so core-only reads what SAP Build Work Zone itself ships.
No community artifact is documented here.
In a UI5 app this is the part of the descriptor a launchpad reads: the intent that navigates to the app and the tile that stands for it.
The app's own manifest.json carries what a site needs to list it: a navigation intent of semantic object and action under sap.app/crossNavigation/inbounds, the tile's title, subtitle, info and icon, and a sap.cloud/service name that is unique per subaccount.
Not covered: At the descriptor. Which groups, catalogs, roles and sites show the app is assigned in the Work Zone content manager and site directory, not in the app.
Beyond the descriptor, SAP Cloud Portal ServiceSAP Cloud Portal ServiceSAP's BTP service for role-based portal sites: pages, apps and widgets behind single sign-on for employees, customers and partners, with content from SAP products and other providers.sap official, btp is the BTP service that builds role-based sites around UI5 apps, and launchpad-kpilaunchpad-kpiAn OData service and a one-method ABAP interface that put a number from an abap2UI5 app on a SAP Fiori launchpad tile.community org, abap from the abap2UI5 addons puts an abap2UI5abap2UI5One ABAP class implementing z2ui5_if_app is the whole app: the browser loads a generic UI5 shell once, and every interaction after that is an HTTP roundtrip back into ABAP.community org, abap app's number on a launchpad tile.
No community artifact is documented here.
Artifacts
Content
Seen working
Neither the package manifest nor the repository tree declares a licence.
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
Details
Coverage
For your agent
- Ref
capability:launchpad-content- JSON
- /capabilities/launchpad-content.json
- MCP
- Connecting an agent