Understanding and Developing Fiori Plugins with Extension API & TypeScript
Describes a launchpad plugin as a UI5 component without views that the shell loads for every app, SAPUI5 only, and compares extending the shell through the renderer with the Extension service from 1.120 and FrameBoundExtension from 1.124, down to the placement options each allows. It builds fiori-fullscreen-pluginfiori-fullscreen-pluginA SAP Fiori launchpad plugin in TypeScript that adds one header button, created through the Extension API, which toggles the browser's fullscreen mode; it needs SAPUI5 above 1.120.independent, ui5 as the sample, and ends with activation: globally through /UI2/FLP_CONF_DEF and /UI2/FLP_CUS_CONF or per role through a Shell-plugin target mapping on an ABAP launchpad, and as an HTML5 app assigned to a role in SAP Build Work Zone.
Where it sits
Who is behind it
In the atlas: maintains 8, contributes to 10, wrote 1@mariokernichauthor
Properties
About this work
For launchpad-plugins
Details
Graph
Source
History
- explains → applies_to on capability:launchpad-pluginsDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).
- Entered the atlasDiscovered via Added by hand.
For your agent
- Ref
content:understanding-and-developing-fiori-plugins-with-extension-api-typescript- JSON
- /content/understanding-and-developing-fiori-plugins-with-extension-api-typescript.json
- MCP
- Connecting an agent