Everything in UI5 / Fiori elements
Type: 2
Domain
Origin
Signals
Fiori elements: Answers in Fiori elements
More
Group by: Capability
Where it runs
Distributed through
Form
UI5 control library for file upload and download in front of CAP
UI5 component adding a spreadsheet upload dialog to Fiori apps
CAP Risks and Mitigations project with a Spreadsheet Upload button
Exercises building a Fiori elements app from Figma via MCP servers
TechEd 2025 workshop driving a Fiori elements app from Figma via MCP
UI5con tutorial on Fiori elements apps with AI assistants and MCP
Fiori Innovation Day exercises on Fiori elements with MCP servers
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Writer of flexible programming model elements into Fiori elements apps
wdi5 selectors for locating controls in Fiori Elements apps
Archived The declared repository is archived.
No license Neither the package manifest nor the repository tree declares a licence.
End-to-end testing for UI5 on WebdriverIO with UI5 control selectors
Where the login cannot be completed by configuration. Its authentication page states that multi-factor authentication is not supported, because a media break between browser and phone cannot be managed out of the box.
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop showing UI5 development with cds-plugin-ui5
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
Thirteen custom UI5 controls for abap2UI5 apps
Needs Standard ABAP 7.50 or higher, and an abap2UI5 whose frontend reserves the resourceRoot `z2ui5_cci`: a frontend predating that rename reserves `z2ui5ccc` and cannot resolve the controls. Frontend artefacts only one company needs, such as an in-house reuse library, a corporate icon font or company CSS, are what [abap2UI5-addons/custom-controls-customer](https://github.com/abap2UI5-addons/custom-controls-customer) is for, the same mechanism under the second reserved root `z2ui5_ccc`. ExportSpreadsheet needs SAPUI5: under OpenUI5 `sap.ui.export` is missing and the button renders disabled.
Template repository for own UI5 artefacts served to abap2UI5
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
TechEd 2022 workshop mixing SAPUI5 with Fiori elements building blocks
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Session building a travel dashboard with Fiori elements and SAPUI5
Fiori Innovation Day session building a travel dashboard
UI5con 2025 tutorial on SAPUI5 flexibility and key user adaptations
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
Three Fiori apps wired to one cross-app navigation intent
Neither the package manifest nor the repository tree declares a licence.
UI5 control library of sized sap.m controls and touch inputs
UI5 Demo Kit samples rebuilt as abap2UI5 apps
The 221 ports under `src/02` need a UI5 runtime newer than 1.71: they install and activate on any release, and on an older UI5 the newer control does not render. The `src/03` collection is hand-written for SAPUI5-only controls and needs a SAPUI5 bootstrap. There are no per-library branches, so pulling the whole repository is the one way in and the activation takes a few minutes.
Showcase for dev-approuter in front of two UI5 apps
Template and mock runtime for S/4HANA Variant Configuration UIs
Samples for the six extension types of SAP Digital Manufacturing
Nothing here runs on its own: a plugin sample needs a Digital Manufacturing tenant to be uploaded into, and the integration samples need a Cloud Integration tenant plus an ERP system, or a mock server as the outbound example uses, before they do anything.
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.
Todo app with CAP and SAPUI5 in TypeScript over OData V4
Neither the package manifest nor the repository tree declares a licence.